yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Android Development] krystianp:
You have to tweak only board-pinmux file. Compare one from ICS branch with cm10.1 branch to get changes that might affect it.
[Atrix 4G Android Development] rhcohen:
Do you know for sure that you do not have the voice typing problem on CM9? As I mentioned, it can take quite a long time -- certainly more than 10 seconds -- for me to get the first failure. After that it is just a few seconds for a recurrence.

But as no one else seems to be reporting a problem maybe it is a quirk of my phone. (Or maybe no one uses this feature.)
[Atrix 4G Android Development] krystianp:
I used voice typing couple of times, longest was 6 minutes. It didn't failed but it might be modem related, as I was loosing connection couple of times. You can go back to your working kernel and check pinmux config by going into /d folder. You will find there tegra_pinmux_something afair. There's whole list of pinmuxes. Check differences and work with it, maybe you'll get something.
[Atrix 4G Android Development] rhcohen:
Thanks for the pointer -- now for the detective work! Yes it seems it could be modem related, as when the failure occurs I get messages about not being able to communicate with Google.
[Atrix 4G Android Development] ahmetcan44:
I wish we had nothing but a working KitKat. I really wish that.
[Atrix 4G Android Development] Feche:
First is first, kernel!
[Atrix 4G Android Development] palmbeach05:
I fully agree with [MENTION=4882205]Feche[/MENTION] on this one. Even though it is probably possible to get KK up and running, b/c AHD is running Epinter's CM11 with a 3.0.1 kernel.

Idk if anyone wants to step up and give it a shot, but I can say this. KK is more like a glorified 4.3. Same thing, few changes here and there, and the addition of ART. The keyboard is messed up (by Google) because they removed the enter button and replaced it with a smilies button.
[Atrix 4G Android Development] rhcohen:
kernel diffs?

I am starting my detective work (to try to figure out how to get a kernel with CM10.1 on which Google Voice Typing doesn't die, but otherwise works as well as the Feb 5 kernel). So I have two questions:

(1) I have determined that google voice typing worked for me on the Jan 18 kernel, but was broken on kernel-2014-01-31_cm10_1_clk2usb. I gather these differ only in pinmux's and amount of diagnostic info provided. I would like to retry some intermediate kernels to see if I can pinpoint when the problem set in and so hopefully narrow down and pinpoint the change that produced it. The kernel from 01_28 would be a good place to start -- it was pretty stable for me -- but I deleted it and the link no longer seems to be alive (I get a "can't find the page you're looking for" error). Do you still have it, and if so can you post it somewhere where I can re-download it?

(2) The other thing I would like to try twiddling is the flash intensity. Is that a kernel issue or ROM? Flash works with stock camera app but flash pictures are often over-exposed.

By the way the Feb 5 kernel continues to be remarkably stable, at least for me. Great work, [MENTION=4641721]krystianp[/MENTION]! (Now if only I could get Google Voice Typing...).
[Atrix 4G Android Development] stuntmanmike82:
There is a new Kernel available in the Dropbox from today.

Installing...

So far everything is working like before.

What are the changes?

Gesendet von meinem MB860 mit Tapatalk
[Atrix 4G Android Development] rhcohen:
[MENTION=4641721]krystianp[/MENTION], I just (re-) tried the kernel 2014_02_03_19_21_CM10.1, and found that it has (for me) the problem with google voice typing, which I don't have with straight epinter Dec 11 CM 10.1. But your description of the 02_03 kernel indicates that all pinmuxes were set to their defaults. So should there be any differences between the 02_03 kernel and Dec 11 CM 10.1? (I am trying to figure out what kind of experimentation to do with kernels I might compile). Or is it perhaps the case that the default settings for pinmuxes are those from early December CM9 and that those differ from early December CM10.1?

By the way I have verified that I can go back and forth between (seemingly any of) the recent kernels and that from Jan 18, with Google voice typing working on the latter and not working on the former.
[Atrix 4G Android Development] krystianp:
i really don't remember if pinmuxes are the same or not but if you compare those tables you should see any differences. Second reason might be defconfig changes, kernel always keeps it's config in /process/config.gz . Try comparing those also.

I did some spi config changes, went back to deferred resume, reverted small changes in dvfs and couple more minor tweaks. On modem drop (data) please provide kernel log.
[Atrix 4G Android Development] rhcohen:
Sorry to have to ask, but where do I find "those tables"? I would presume in the repository for the status as of the Dec. 11 CM 10.1, but where for the 02_03 kernel?

By the way I still have the problem with the newest kernel.

And again, I would llke to retry the kernel from 01_28 but link is broken. Is there a way I can get it?
[Atrix 4G Android Development] krystianp:
/d/tegra_pinmux

as for kernel it might be deleted by now:/
[Atrix 4G Android Development] saiftheboss7:
The last kernel gave me no reboots till now. Definitely better than previous. Had too many random reboots. Modem drop still occurs though. Had 1 drops in 4 hours.
[Atrix 4G Android Development] krystianp:
Take kernel log please, I've added some stuff there, maybe it will be helpful
[Atrix 4G Android Development] saiftheboss7:
I know it'll will sound stupid.. But how do I do it? Will I have to connect to adb or is there an app for that?

Thanks in advance.

New Bug:

1) Call Waiting Beeping sound doesn't work.

2) Sound goes totally mute after a call. Doesn't work any type of sound including music or video or ringer until a reboot.
[Atrix 4G Android Development] krystianp:
You can either take it on the phone in terminal emulator or via adb. I find sometimes adb more convenient because I can watch kernel log being streamed. This way it's easier to spot problematic parts. I'm not sure what call waiting beeping means and haven't experienced your second bug also. But kernel log should help here. Taking logs was explained couple of times in recent posts, just search for "dmesg".
[Atrix 4G Android Development] tonglebeak:
Drop during speed test download. 10640 in the log is whereiI think it takes a crap.
[Atrix 4G Android Development] saiftheboss7:
Not on PC. So now doing it from mob.

Here's the log Log Link
[Atrix 4G Android Development] todobarato:
Hello Krystianp,

With the last kernel 01_49 on CM9 I get data drops by do the speed test and music stops to play, but in cm10 work perfect, extrange.. Do you need the logs?

Sent from my MB860
[Atrix 4G Android Development] Feche:
Data and signal drops, logs here.
[Atrix 4G Android Development] jisse44:
I had many modem drops yesterday with kernel-2014_02_10_01_49 but can't take klog because I was hurry, so I returned to 2014-02-05 version.

I re flashed 2014_02_10_01_49 this morning, I did many speedtest at home, and no data drop by now.
[Atrix 4G Android Development] krystianp:
Music stops with local played music or streamed music. Do you play it over phone's speaker, headphones, bt headset? And yes, log would be nice.
[Atrix 4G Android Development] vicfuze:
Looks like krystianp checked in a lot of updates in the branch today.

Are all these commits in the latest dropbox kernels from yesterday or should we compile these for testing?

Thanks!

Feb 11<= commits
[Atrix 4G Android Development] todobarato:
Yes, it was playing on local player, files on SD-card, over headphones.

the following logs are OK:

dmesg>/sdcard/kernel.log

And for radio log do:

logcat -b radio >/sdcard/radio.log

or something else?

Best regards.
[Atrix 4G Android Development] krystianp:
Those are older commits that I had and that where not uploaded. Current changes are not published yet, since I don't know what works and what doesn't. I published those commits

so [MENTION=5268654]rhcohen[/MENTION] can find out why Google voice doesn't work.

Where these logs taken after your bugs occurred?
[Atrix 4G Android Development] vicfuze:
I use Google voice on ICS, and just used voice to compose a message fine with latest dropbox kernel (kernel-2014_02_10_01_49_atrics.zip)

Might be a CM10.1 ROM problem. I also see stability issues if you do not wipe davi/cache between kernels.
[Atrix 4G Android Development] krystianp:
One more thing that might cause problems on cm10.1 is ramdisk.
[Atrix 4G Android Development] rhcohen:
RE Google voice typing problem

Hey [MENTION=1955369]vicfuze[/MENTION], just FYI -- krystianp had also suggested voice typing might be a CM10.1 problem. But I have verified that for any kernel prior to Jan 26 I have no problem with it, and for any kernel from Jan 26 on I do have the problem. I can switch back and forth repeatedly and toggle the problem off/on. Doesn't matter if I wipe dalvik/cache or not between kernels. So maybe it is a problem with how the kernel interacts with CM10.1, or possibly just how the kernel interacts with some particular hardware combination (as seemingly has been the case for modem drops and other problems with some of the recent kernels -- e.g. I'm running the 02_10 kernel with no modem drops, restarts or freezes so far, after more than a day, but other people have been having problems.) I am planning to compile the kernel now in the repo with the changes between Jan 26 and the one before it turned on/off one at a time and hopefully isolate the voice typing problem. (actually, I'm planning to do a full wipe/reinstall of CM10.1 and the Feb. 10 kernel to verify I still have the problem before proceeding).

BTW vicfuze I see you are in SF; I am also in the bay area (east bay).

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

What is the difference bewteen ramdisk treatment on CM10.1 and ICS/CM9, and how would that be related to my voice typing problem coming/going with different kernels?
[Atrix 4G Android Development] todobarato:
Yes, but the music bug was not possible to reproduce, I will try today.
[Atrix 4G Android Development] todobarato:
Hello again,

I have make log again and the drop only occurs if the music is playing??? Very estrange....
[Atrix 4G Android Development] Voldemort:
I was on the 0202 01.15 kernel for several days (no time to test the new ones until today) and the voice recognition bug did not affect my phone with 10.1, so I guess it's something more device-specific than simply rom-kernel interaction...

The only issue I had with this kernel was some kind of delay with apps and the obvious prompt "trebuchet/phone/whatever is not responding. Wait or kill the process?"

Testing the latest one now, anything I should be testing first?
[Atrix 4G Android Development] rhcohen:
problems cloning kernel

I've been trying to get a local copy of the kernel repo (so I can compile and try to sort out google voice recognition issues on CM10.1). But every time I try to do a "git clone" it hangs at around 30% downloaded, and then quits. I get error messages like:

Cloning into 'android_kernel_motorola_olympus'...

remote: Reusing existing pack: 2194104, done.

error: RPC failed; result=56, HTTP code = 200.71 MiB | 212 KiB/s

fatal: The remote end hung up unexpectedly

fatal: early EOF

fatal: index-pack failed

Can someone suggest a more fault-tolerant way to proceed? (I am running "git clone" from a terminal window on my computer.)
[Atrix 4G Android Development] andresrivas:
Try to sync to a new folder

Enviado desde mi MB860 usando Tapatalk 2
[Atrix 4G Android Development] Voldemort:
On the 10/02 kernel Google voice recognition worked fine although I couldn't hear anyone during phone calls nor anyone could hear me.

Reverted back to 0202, will test another one tomorrow.

Should I fill the spreadsheet?
[Atrix 4G Android Development] rhcohen:
I never tried the 0202 kernels, tried older and newer ones. I had troubles with kernels from 01_26, 01_28, 01_31, 02_01, 02_05 and 02_10. I will try the 0202 one to see if by any chance the voice recognition problem goes away for me. By the way I can see the problem with, seemingly, any app that uses Google voice recognition: google voice typing on email, google search, google translate.

But generating a dmesg log just after reboot would be helpful to see what is the same and different between your phone and mine. There is at least one additional person having the voice recognition problem, [MENTION=1567750]txtsd[/MENTION], posting on the CM10.1 forum. txtsd and I have same radio (37P); you have 38P. But I doubt that is the difference since I have the problem whether on cell data or wifi.

---------- Post added at 04:02 PM ---------- Previous post was at 04:00 PM ----------

Sorry, by "sync to a new folder" do you mean clone a different git repo (which I can do successfully) or try to clone into a different folder on my computer (hard to see how that could matter, I am cloning now into an empty folder.)?

Update: I updated git, seems to have solved the problem.
[Atrix 4G Android Development] rhcohen:
38P radio

Since I'm wondering if the radio version could possibly make a difference to the voice recognition issue (I would have thought not) -- are you on 38P because it came with a phone company phone upgrade, or did you upgrade that yourself? If so, why, what difference did it make, and where did you find the upgrade file?
[Atrix 4G Android Development] Feche:
Tired of reboots when unlocking the phone/deep sleep bug with 1_49 & 15_39 kernels, I installed 19_21 kernel an this is my report:

- 49 hours uptime WITH NO PROBLEMS!

- No data drops

- Good signal

- No reboots when unlocking/deep sleep

- Very stable ROM and very fluid!

- Good battery with light usage

The only problem I noticed is that battery percentage is displayed wrong sometimes (?) I think K released a fix for that but it's on newer kernels.
[Atrix 4G Android Development] rhcohen:
Further update: I tried flashing the kernel that worked for you (0202_01_15) and (not surprising to me) google voice recognition (typing, search, etc) was not working properly. Since your ( [MENTION=462587]Voldemort[/MENTION] ) phone has google voice recognition working on that kernel I expect it will as well on the latest ones. All the more reason to have you post the info about your phone hardware (from dmesg log and "about phone" to the spreadsheet) and/or post here. It would be nice to understand what makes your phone different from mine and that of [MENTION=1567750]txtsd[/MENTION]. It is apparently not ROM (the same for all), probably not memory (txtsd and I have different ones but the same google voice recognition problem), and not radio (txtsd has same radio as you).

By the way, maybe you said this before, but how for how long did you try voice recognition? First time around on a ROM, after cache/dalvik wipes, it seems to take a while -- maybe 15-20 sec -- of continuous use to get a failure. After the first failure additional ones are much quicker (a few sec).
[Atrix 4G Android Development] Voldemort:
I used voice recognition for about 20-30 seconds on the 10/02 kernel (probably that's border line for an accurate test).

I suspected 02/02 wouldn't work on your device as well, but I was hoping the best for you :)

I will test another kernel this afternoon and will fill the spreadsheet then.
[Atrix 4G Android Development] jisse44:
New network drop with kernel-2014_02_10_01_49_atrics.

After first wifi on/off, phone ask for SIM PIN code, unfortunately I wasn't logging at this time.

I started logcat and kmsg after the drop, and turn on/off wifi, airplane mode and data. I had to reboot to retrieve data signal.
[Atrix 4G Android Development] rhcohen:
Good! I have also a set of data from [MENTION=1567750]txtsd[/MENTION] (he posted a dmesg log) and will (after asking his permission) add that to the spreadsheet or see if he will do so.

And yes, 20-30 sec is borderline. The time it takes for first failure for me is quite variable. And by the way, once I have a failure, if I don't wipe cache/dalvik, installing a different kernel displays either success or failure of voice typing quite quickly. So maybe the problem has something to do with the way different kernels use cache and/or dalvik. (But why would that be hardware-specific?)

I am also about to start looking to see what pinmux or config settings changed between Jan 18 and Jan 26 and that were still in effect in the February kernels, to see if I can narrow down what changes might be responsible for the voice recognition failure.
[Atrix 4G Android Development] jcrahul:
even i am using this kernel "moved to this when i read your post" this is pretty stable... but still i can't comment about battery drain
[Atrix 4G Android Development] Voldemort:
I just updated the spreadsheet with my test results.

I had to revert back to 2014/02/05 kernel because the 2014/02/10 made the phone unusable (could not hear during phone calls nor others could hear me)
[Atrix 4G Android Development] rhcohen:
I looked at your spreadsheet results. When you say "Google voice works only for 5-10 sec (not crashing though)" -- do you mean by that that after it stops working you can press the microphone and talk for another several seconds before it stops typing again? That is what I observed and described by "Google voice typing crashes" -- it crashes after several sec. Pressing the microphone and trying again is, I think, starting up another google voice session, it runs until it crashes. Anyway if you're answer to the above question is "yes" it seems we are observing the same problem. So that makes at least 3 of us.

Very hard to distinguish from the spreadsheet answers any correlation (among people on 10.1) between those reporting the problem (versus those who don't) and the hardware combinations. Although maybe those who haven't reported the problem are just not using GV recognition, or not using it for sufficiently long times that they observe the problem.

You should probably note your problem with 2014/02/10 under "other bugs" on the spreadsheet.
[Atrix 4G Android Development] vicfuze:
New dropbox test kernels posted today...
[Atrix 4G Android Development] Voldemort:
The answer to your first question is yes, we do have the same issue. I did not remember your exact explanation here on the forum and I thought that you had a real crash and not that it simply paused the service and then it started again.

Fix it as you wish, IMHO a crash is something different and worse than a service that works for X seconds, let's just find a clear way to explain it :)

The "other bugs" section only has CM9 roms so I did not touch it.
[Atrix 4G Android Development] palmbeach05:
new kernels are up
[Atrix 4G Android Development] rhcohen:
I wasn't referring to the "other bugs" section, but rather the "other bugs" row of the "modem drops" sheet. There is such a row for each of the recent kernels, right underneath "deep sleep reboot/sleep of death" -- the same row where you entered your remark about Google Voice.

RE the use of the term "crash", I guess I think that when a particular application or service dies, it has crashed. If I understand you correctly, what you experienced is not a pause in the service -- if you had to push that microphone button to resume, you were restarting the service. But then, the term we use to describe it isn't what's important here.
[Atrix 4G Android Development] krystianp:
All who experience problems with audio (skype, calls, etc) please provide kernel log (IMPORTANT: take it as soon as you notice the problem). I've posted new kernel as you noticed, please compare this and previous carefully. Changes are very small but might be important.
[Atrix 4G Android Development] tonglebeak:
Modem drop with new kernel
[Atrix 4G Android Development] krystianp:
From the logs I'm receiving final error is this:

<3>[ 2174.602454] spi_slave_tegra spi_slave_tegra.0: transfer timeout
<3>[ 2175.602447] spi_slave_tegra spi_slave_tegra.0: Error in Dma Rx transfer
<3>[ 2175.602463] spi_slave_tegra spi_slave_tegra.0: spi_tegra_handle_transfer_completion ERROR bit set 0x40a00000
<4>[ 2175.602475] ------------[ cut here ]------------
<4>[ 2175.602483] WARNING: at drivers/spi/spi_slave_tegra.c:1096 0xc03158c8()
<4>[ 2175.602489] Modules linked in: zram(C) lzo_decompress lzo_compress
<4>[ 2175.602511] Function entered at [<c0014880>] from [<c0050a08>]
<4>[ 2175.602520] Function entered at [<c0050a08>] from [<c0050a3c>]
<4>[ 2175.602527] Function entered at [<c0050a3c>] from [<c03158c8>]
<4>[ 2175.602536] Function entered at [<c03158c8>] from [<c0064758>]
<4>[ 2175.602544] Function entered at [<c0064758>] from [<c0064d7c>]
<4>[ 2175.602551] Function entered at [<c0064d7c>] from [<c006ade0>]
<4>[ 2175.602558] Function entered at [<c006ade0>] from [<c000f080>]
<4>[ 2175.602567] ---[ end trace d3c6bb984ccfe132 ]---
<1>[ 2175.602575] spi:tegra:address m=c07ef504 m->complete=c0312218

Now I'm trying to figure out what is the cause of that. For now please test it if it's better or worse than last kernel. I'm in the middle of preparing new kernel with more info that will help to solve this issue.
[Atrix 4G Android Development] saldirai:
fingers crossed.
[Atrix 4G Android Development] Zeljko1234:
Everything is prepared. We have JTAG pin-out (thx lehjr), test Atrix (I don't know who donated), steady hand (thx mmontuori), remarkable kernel team (I think everyone knows krystianp and mmontuori)... So I believe in power of community :)
[Atrix 4G Android Development] quetzalcoatl2435:
Fingers crossed...
[Atrix 4G Android Development] Pixelguy:
everyones counting on you :D lets hope this works! and if not so what your team gave it a good shot :fingers-crossed:
[Atrix 4G Android Development] ranjithkumar1201:
Best of luck to all of u guys working on this

Partyyyyy the day it works
[Atrix 4G Android Development] krystianp:
That atrix is mmountuori's. He is devoting his backup atrix to this project. We are also testing all kernel changes on it. So all the thanks goes to him:)
[Atrix 4G Android Development] ekennes:
View attachment 1544082
[Atrix 4G Android Development] Zeljko1234:
He surprise me everyday. I follow your activity and you also deserve a lot of thanks :good:
[Atrix 4G Android Development] petersonldp:
guys, the topic of the rom epinter was posted a link that directs to download the kernel source of our atrix, but I realized that seeing the documentation is 2.6.xx, will have some benefit to colleagues?
[Atrix 4G Android Development] Lexord:
Good luck guys :) BTW who's testing this, mmontuori or krystianp?

Sent desde mi MB860
[Atrix 4G Android Development] saldirai:
View attachment 1544114
[Atrix 4G Android Development] Zeljko1234:
I tested many version of the kernel for UART. Unfortunately non of them work. That's why we're going for JTAG...
[Atrix 4G Android Development] attrixnor:
thanks for this team : developpers, atrix donater and hard work !!

good luck :cowboy:
[Atrix 4G Android Development] wildchild048:
I have a spare atrix if you need something tested.
[Atrix 4G Android Development] Zeljko1234:
Are you good at soldering?
[Atrix 4G Android Development] ticiano_arraes:
Good luck guys.
[Atrix 4G Android Development] krook6023:
@ALL

Keep this thread on topic, asking for ETA's is not productive.

krook6023 (mod team)
[Atrix 4G Android Development] Ilkinansr92:
http://www.phonearena.com/news/Bett...es-for-the-LG-Optimus-2X-at-long-last_id37426
[Atrix 4G Android Development] HMZX:
Great news! The Optimus 2X has finally got ICS, and that is a sign - It will all get better ;)

Seriously though, hope the devs are able to make use of that release.

Massive thumbs up to all of your work so far, you are awesome people! :good:
[Atrix 4G Android Development] canerpense:
Back to topic please, we are very eager to see something new after such a long time. Since Motofail left us alone, we are all counting on the devs and the community.

I wish I could help with my poor coding skills...:eek: