yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] guevor:
I still have no clear what causes it, but I have noticed that when the dock battery has enough capacity did not happen, but when it is empty starts to happen.

Sometimes if I extract from the dock and return to insert does not happen more.

Anyway, I hope someday to find the cause or at least some remedy that really works.

I looked at the logs, and all messages are relative to when you suspend, so if the problem you mention was happening while the log there was no kernel message.

It could be that some process was accessing the disk much? To me it often happens that com.android.providers.media or /system/bin/sdcard is scanning all devices (memory, sdcard, microsd, etc. ..) in search of new/changed media, which slows the system, since access to devices (especially microsd or sd) is not too fast.

I've said some times, that for me this process is not working properly, because I have come to see how does the scan ends and begins again without I having done nothing new.

Anyway, if you want log, the only way to see what is making the system is with logcat (system log), because the kernel does what is asked to do and unless something goes wrong does not give error messages.
[Eee Pad Transformer Android Development] farsight73:
I'm on this V20.1 test2, using Droidwall(firewall) and it worked.

Anyway, what kind of optimization you add and remove here and what is it or do actually ?

Sent from Transformer TF101 (B60) via XDA Premium HD
[Eee Pad Transformer Android Development] guevor:
What nvidia has released is a new version of its proprietary and binary drivers for linux/X11. That means that if can be used for anything would be for modify a rom, and I have no means clear that nvidia make his binary libraries compatible with Linux/X11 and android. If so could attempt the use some of these binaries to update a rom, but as I say, I think it would be difficult to work properly.

In addition, if that could be used with android, would need to use a kernel with the drivers of that version (I think they use a kernel 3.1), because I'm pretty sure there are things changed and incompatible.

In short, I believe that to use it, could be a big effort kernel/rom and a very high probability that it did not serve at all.

A pity, because if the nvidia drivers were available as source code, certainly, all the current problems would not exist.

To receive notifications, emails etc. .. while suspended (as I use it) wifi must be configured to always on .

This does not mean that the processor never stops working to process what is received by the wireless or wifi itself is spending as if we were transfering.

Actually the hardware is designed to operate in that state, so it consumes very little, we could say (not accurate) that most of the time is off and turn on from time to time to check.

It could be what I've seen commented several times, that the configuration is wrong and must try toggling the setting.

Was a compiler optimization where the size of all structures and unions were rounded up to a multiple of 32.

I guess the problem would be with a structure that was turning out differently than expected in some of the system binaries (with a different compiler options).
[Eee Pad Transformer Android Development] gbil:
@guevor, as I wrote with v20 I don't get the sound stopping issue. I noticed that when this happened with other versions I got quite a few i2c errors in dmesg which I don't get now.

Have you changed anything specific in v20 regarding to i2c ? Because with v20 test1 etc I do get the sound stopping issue and same errors.
[Eee Pad Transformer Android Development] guevor:
Only change on test2 was the compiler optimization and in test1 a change in the pcie and some bus configuration but I have not sure it can affect to sound. It do not really ever happened to me so do not know where can be the source.

If you give me a log when it happens to you, maybe give me a clue.
[Eee Pad Transformer Android Development] conizius:
In addition to what guvour said: you really dont want to use these drivers in android :) the drivers developed for android are way better (not to mention that it isn't compatible). I use those with ubuntu/linux and it is far from perfect...

Some pretty ugly bugs which lets a lot of gles applications crash. Tegra is ment for android and those linux/x11 drivers are just like a gimmic.
[Eee Pad Transformer Android Development] guevor:
I have downloaded and looked over (I had not looked at they before) and are obviously incompatible, because all the libraries are compiled for a linux standard structure (libc6 etc. ..) that we don't have in android.

What I've tried are the codecs (h264,jpeg,mp3,etc..), which should be more modern than we have today. What is not clear is whether they will work better, the same or give any problems.

Right now I'm using they and seems to work well on Revolver (not sure if other rom change the location of them "system/etc/firmware").

If someone wants to try it, I created a package that installs them (make a backup before if you do not want to reinstall the ROM in case of problem)
[Eee Pad Transformer Android Development] DammedKiller:
But do you notice any difference between that codecs and the standard ones?
[Eee Pad Transformer Android Development] ferparedes:
6HP39952LY2309450

Hell, I'm not using ICS anymore but I do recognize that you're doing an awesome work. If and when I do get back to ICS, your kernel is the one I'll most likely be using.

Thanks for everything dude, keep it up as long as you can (and for as long as it's fun for you)
[Eee Pad Transformer Android Development] gkillerx:
nstalled on arhd and its working. I didn't notice any though
[Eee Pad Transformer Android Development] sidneyk:
I just downloaded and flashed this codec package. I don't know if it's the codecs or the update of Netflix that happened earlier today, but now videos in Netflix are playing buttery smooth. Before, I was getting some weird scaling issues on scene changes, where you could see a flash of some other image from a different spot in the video and could see it try sometimes 2 or 3 different sizes to scale the video before it decided on one. Now, I'm not seeing any of that in Netflix. If it's the codecs, then thanks guevor, greatly needed. If it's Netflix work then I'll have to thank them. Anyway, after rebooting with these codecs installed, I did not see anything weird in dmesg.
[Eee Pad Transformer Android Development] wasdvd:
New codecs work terrific for me

TF101, ROM 4.0.3 RC3, kernel V20.1

With the new codecs:

Videos on the device play smoother than I ever remember, without OC, using 4 different players: Dice, BS, Mobi and MX. None of my videos are above 720P.

FlashTV also plays fine.

HD full screen YouTube also is perfectly smooth.

Seems to me you made a winner!
[Eee Pad Transformer Android Development] gbil:
Hi mate,

it was pretty easy to reproduce the problem with test2. I attach the dmesg after the sound was lost at which point also the whole tablet is acting a bit strange eg touch isn't always snappy, scrolling lags a bit and of course sound is lost.

Errors start at around line 1927. With the vanilla v20 I don't get these errors even hours after booting while with test2 I got them less than 30 minutes after boot.

thanks for the help
[Eee Pad Transformer Android Development] boonkui:
Thanks for the analysis. Given that I was viewing and annotating a large (6.6 MB) PDF file, I believe the slowness might be caused by disk access. The possibility of being out-of-memory is lower. Will take note of logcat.
[Eee Pad Transformer Android Development] guevor:
I looked at the log and for some reason it fails i2c communication. Initially the sound and later with the touch. The truth is that I do not ever happened to me (AFAIK) with any version, and I guess that most people neither, so it looks (which is becoming increasingly clear) to have a problem with the hardware and tolerances, which causes depending on how things are done the problem occurs faster.

It really is the only explanation I can find that there is such disparity between units of the tablet, from units that have no problem to other who have a lot of them, with a variety in between.

That said, all I can do is what I've been doing, looking for ways that these problems occur as little as possible. The downside is that lately, every changes I made, make it work better in some, but worse in others, which makes the job difficult and can go mad.

Anyway, I think the advantage of keep trying different ways is that if some version works good for someone, they can keep using that until there is something better.

On this particular issue, I will prepare a version in which I will remove one of the changes since V20 to see if you notice changes. Otherwise, I can remove another change and try again.
[Eee Pad Transformer Android Development] DroidRevenge:
This situation is interesting... also here with ARHD 3.4 and v20test2 my TF seams to loose touches, offten i have to touch 2 times to make it does what i want, and scrolling are very very jerky.

I am waiting for (another) test version... then i will report back result.

10x
[Eee Pad Transformer Android Development] guevor:
If it is the same problem, you could see in the kernel log if I2c errors appear related to maxTouch.

I prepared three incremental releases.

In the first I removed a small change.

in the second, another change removed plus the previous one.

In the third the same as the above but with new changes in i2c.

Please, try in order to be able to know what change affected (if any).
[Eee Pad Transformer Android Development] DroidRevenge:
Downloading, then testing...

---------- Post added at 12:03 PM ---------- Previous post was at 11:52 AM ----------

v20test3 = it seams ok, no more dead-touches or jerky scroll.

Guevor do you want i continue with other verions?

EDIT

Sorry but after some minutes, screen off, wifi on but doing nothing, issues are still here.

proceiding with other versions...

EDIT:

This i s odd!

i am trying to take dmesg for this issue and now all works well... can't say why!
[Eee Pad Transformer Android Development] guevor:
That's the downside to these things that are not deterministic and occur when they want.

If you think that having a cat /proc/kmsg working to capture the messages is affecting (although I see no reason for it), as this problem not produce hang, you can simply wait for it to happen and save later.
[Eee Pad Transformer Android Development] DroidRevenge:
not deterministic?

Doh! i need a duff! ;)

i am kidding, got it.

i will report you later.

10x
[Eee Pad Transformer Android Development] farsight73:
This v20.1 test2 having USB not function. Tried connect with my thumb-drive and Portable Harddisk but nothing on both USB ports.

Cold boot wouldn't help anything here. It seemed like the USB ports have no power at all.

Sent from Transformer TF101 (B60) via XDA Premium HD
[Eee Pad Transformer Android Development] guevor:
I'll try it now.

Edit:

There is a problem, I will try to track it.
[Eee Pad Transformer Android Development] DroidRevenge:
Maybe it is for that problem that i was not able to connect XBX360 joypad... don't you?
[Eee Pad Transformer Android Development] guevor:
I'm booting a new version to test if I have solved the problem, however, as a trick to make it work, leave it connected and suspended the tablet, when wakeup (if suspended really) should work.

When I verify that it works in different situations, I'll upload a new version.
[Eee Pad Transformer Android Development] devilpera64:
Guevor, for BT transfer? (device to TF101 works, not if TF101 to device)
[Eee Pad Transformer Android Development] guevor:
Have you read my post http://xdaforums.com/showpost.php?p=26423355&postcount=1459 ?

Edit:

Seems solved the problem with usb. It seems I had tried to save too much and stayed without power.

This version is identical to the test5 I have uploaded before but with the usb bus change.
[Eee Pad Transformer Android Development] farsight73:
Great.. thanks for looking into it right away.. I'm currently back with 16b since I'm away in such a rush and needed my work done on time.

Will test again your next kernel when it got rectified..

Sent from Transformer TF101 (B60) via XDA Premium HD
[Eee Pad Transformer Android Development] devilpera64:
Ihih i missed this passage :') i lost your response reading the others :) thx!
[Eee Pad Transformer Android Development] farsight73:
Quick report: Flashed and tested this kernel v20.1 test6 and USB back working again.. Thanks!

Sent from Transformer TF101 (B60) via XDA Premium HD
[Eee Pad Transformer Android Development] stcanard:
I've been seeing the I2C errors as well, I'll try through these and report results as well.
[Eee Pad Transformer Android Development] Penphoe:
Thank-you! For your kernels! Not only is my TF101 B70 no longer rebooting randomly, it seems to be much smoother! On top of that, my original XBOX controller which I've replaced the cable with an old USB cable works as a game controller again!

I was so disappointed when my OG Xbox controller no longer was supported in the Asus ICS kernel, but now I'm using yours and it works!

I too was running .test2 and when I tried my controller with this kernel, it wouldn't get recognized. When I did a dmesg in a shell, no messages showed up acknowledging the device. Now with this kernel, it works!

LaterZ!

Darren!!
[Eee Pad Transformer Android Development] gbil:
I'm using the first one since yesterday afternoon and don't have any i2c issues since.
[Eee Pad Transformer Android Development] devilpera64:
USB can't connect USB mass storage

Guevor i can't connect USB storage keys because TF won't mount them...it recognize them just a second and mount icon disappear... (i'm using V20_test6 - your last source). It won't recognize also USB host of my HD2 Android in the same mode..

thanks for your attenction :-)
[Eee Pad Transformer Android Development] guevor:
A kernel log would help.
[Eee Pad Transformer Android Development] devilpera64:
How i can do it? ^_^
[Eee Pad Transformer Android Development] guevor:
For collecting a kernel log after you experienced the problem, can use a program like os monitor that allow to save the kernel log, or in a terminal can write:

dmesg > /sdcard/kernel.log

After that, on the sdcard you can find a file kernel log that can attach here.
[Eee Pad Transformer Android Development] AstroTrain:
Hello guevor,

I am having some recent problems with 2 of your kernels 17c and 20.1.

I am running Ricardo's CM9 Megatron rom version 1.1.6, got multiple SODs/RRs with 17c and now 20.1 after ROM upgrade. I have attached kernel log file as well as logcat for the most recent SOD for 20.1.

Before with an earlier version of his Rom and using 17C I never had any of the above issues but I was using your kernel straight from this thread, now we are advised to use the kernels in Megatron Parts which I assumed are modified.

Can you take a look?

Thanks
[Eee Pad Transformer Android Development] jtrosky:
@guevor - I would love to try your kernels, but when I tried 17c and V20, I found that IPSec Xauth PSK VPN's don't work work with your kernel (which works fine in stock).

Any idea why this wouldn't work or how to fix it?

I had to revert to stock until I can get this issue addressed as I absolutely need VPN access to work...

Thanks for any input you may have!
[Eee Pad Transformer Android Development] guevor:
I have reviewed the log and the last things I can see is that tablet woke up (was not really on deep sleep because was charging), then performed the face unlock and three minutes later the log ends.

My questions are:

How was it exactly?

Did you try to wake him and did not turn on the screen, waiting for three minutes and finally pressing the power button 10 seconds to reboot?

In this log do not see anything like the failures I've seen so far, because it seems the log of normal operation, was not suspended and the screen appear to be on.

I can not test the VPN, so I can not see that error occurs, if it shows any, so would be useful if you could save the logs in the process.

It would be logs from kernel and the system just after having tried to connect to vpn, to see if there are something that can give hints.

For privacy would be better that at least the logcat were send me by PM, because I'm not sure if will show some private information about your VPN.

Perhaps only with the kernel log has enough, although it would be rare.
[Eee Pad Transformer Android Development] AstroTrain:
Thanks for the quick response Guevor,

The tablet was not on charger overnight, the batt was at 33% yesterday then this morning tried to wake the tablet as I normally do by opening the cover on my tablet case). I have a magnet on case that automatically wakes the tablet when the case is open. So that failed to wake the tablet so I used the power button, no response after several tries, then had to hold down power button 10 secs then it powered up and the batt was down to 13%. So to me it looked like a SOD.

When the tablet woke I went in to retrieve both the logcat and the dmesg files. After that I reflashed the 20.1 kernel from megatron parts.

Before I upgraded to new Rom version never had a problem with 17C, was rock solid. If another Sod or RR occurs will try to get the kernel log again.

Thoughts?
[Eee Pad Transformer Android Development] guevor:
Ok, so the log was from the next boot, when it was working ok?.

So the facts that were recorded are those of the next boot and so what I saw, it was a normal state.

What I need to try to find out what happens is the log of when it occurs, so the only method to get it is leaving a process to save the log continuously.

For this you need to use a terminal, become root (by typing su) and then put:

cat /proc/kmsg > /Removable/MicroSD/kernel.log &

That will keep all kernel messages to the file kernel.log on the microsd (need to use a microsd to not cut the recording when sleep)

Thus if at some point is hang, the next boot the file with the last recorded message (not the last, because unfortunately when failure comes, can't save, but at least the immediately preceding).

Sorry for the delay, but when I was writing the answer, I had to leave, since a small fire on a lower floor of a neighbor and although it was controlled, the smoke was entering.
[Eee Pad Transformer Android Development] AstroTrain:
No need to apologize, hope all is well. :)

Yes, the logs were after the next boot. I will try your suggestion and hopefully the logs will show the event that took place for it to shutdown like that. There is one other person that reported getting SODs after the ROM upgrade to 1.1.1 plus in the Megatron ICS thread using kernel 17c.
[Eee Pad Transformer Android Development] atomic339:
What the min CPU frequency is 312 MHz? Is it related with random reboot?
[Eee Pad Transformer Android Development] devilpera64:
Are you ok Guevor? :-/
[Eee Pad Transformer Android Development] guevor:
Yes, all right, thanks. The only problem is the smell that is left, but all is ok.
[Eee Pad Transformer Android Development] Thing O Doom:
Hope it was all resolved well!

Thanks for the latest 20.1, my Xbox gamepad finally works native again without any hacky fixes!
[Eee Pad Transformer Android Development] akyboy:
20.1 on megatron is sooooo smooth,..... runing it for 1h now,...
[Eee Pad Transformer Android Development] Nebucatnetzer:
That's a dev. Even working when there's a fire and just leaves if he can't stand it anymore. I take my hat off to you.

;)
[Eee Pad Transformer Android Development] devilpera64:
Here there is my kernel.log...i hope to have done right :-)

https://rapidshare.com/files/3205488141/kernel.log
[Eee Pad Transformer Android Development] carlvk:
I have always imagined Android dev's having to achieve something like this

http://www.youtube.com/watch?v=LtFImsMIl1U&feature=related

when things are normal , never mind during a fire :cool:

all is good still with my b50, dock, all the cards, running v20 test 6 Thanks for giving me my tablet back
[Eee Pad Transformer Android Development] guevor:
I can not say that neither yes nor no. As it is something that happens quite randomly any change in timings can affect, but can assure you that it not solve the problem.

Other than that, the consumption does not suffer too much and have better response.

Well, I was a bit stupid, because when I left, the respiration was bad, not because there was a lot of smoke, but because it were from plastic burning and the smoke is worse.

I analyzed the log and I saw a strange behavior. I will try to locate the source, and then fix it.

Sometimes I've felt that way, or even with more dishes, you know that some will fall, but you keep trying.
[Eee Pad Transformer Android Development] guevor:
@devilpera64, I have reviewed the code and according to the log, did not execute some part of the disk initialization, but I have not touched anything of that code in a while, so I do not understand what could have happened.

I added some debugging to try to extract some more information about what happens.

If you can test this version and repeat the same steps to generate another log, I will continue investigating that case.

This version also includes some other minor changes after which if there was no trouble, will release as V21.
[Eee Pad Transformer Android Development] devilpera64:
Wow this update solved error mounting removable drivers! Thx! do you want log?
[Eee Pad Transformer Android Development] guevor:
No, log was only for when not working, to see where it failed, so unless it occur again, it is not necessary.
[Eee Pad Transformer Android Development] sagar_tiru2006:
I dont get it ... I have V20 and games like GTA and others crash after a 5-10minz of gameplay !!!

Is there something wrong wid my ROM or is it the Kernel ... ??

Using Revolver RC3 with latest ASUS Base ROM
[Eee Pad Transformer Android Development] guevor:
I have no GTA, but I've tried lots of games and have had no problems.

It could be a problem of voltage/overclocking, or perhaps something else.

The kernel log, after going off the game, may indicate whether a problem with the ram or anything else related to the kernel. I also use RevolverRC3.

EDIT:

I uploaded the V21.

It is the same as V20.1test7, but without the added debug.
[Eee Pad Transformer Android Development] revjwb32:
i have added the kernel, What program are you using to overclock? Voltage Control? and if i dont use any is it just the normal stock 1ghz?
[Eee Pad Transformer Android Development] bsoplinger:
What exactly would one see in the logs when there is a problem with voltage/overclocking? Can I debug when I put the voltage too low or speed too fast without needing to bother you?

Sent from my Sprint Evo View 4G (PG41200) using Xparent Purple Tapatalk 2
[Eee Pad Transformer Android Development] sandman7793:
Set Cpu works good for overclock just make sure if u check mark the set on boot save the recovery zip to sd card (Under settings inside set cpu) so you can get out of boot loop if you overclock to high!!!!

Also thanks Guevor for all you do!!!