yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] prexzone:
can someone pls tell me y my phone keeps tripping off randomly n its like my battery is getting weaker. im using a sprint cdma rhod400
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
"Tripping off randomly"? You mean just dying out of nowhere...?

I'd say your battery is dying if that's the case, you give me very little to go off of tho...
[Touch Pro2, Tilt 2 Android Development] Starfox:
Not sure if this log helps, but there seems to be a problem in tty_ldisc.c. I see two null dereferences in my dmesg.

http://db.tt/DhCqj8L

Also about the apps "freezing", it seems that there's a lock somewhere that causes events to "queue up" until Android gets impatient and shows the FC/Wait dialog, at which point all the events gets passed to the process. Not sure how to diagnose that one.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] prexzone:
its not my battery. i use the frx06. for one my battery drains quickly and most times when im using my phone it just goes off for some reason idk. is this a bug problem or just my phone(sprint cdma rhod400 wit wistilt2 kernel) cos my phone is just 2months old
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Probably because it's not sleeping.

Do you see a solid green LED? If it's blinking or orange, the phone isn't sleeping and slaughtering your battery...
[Touch Pro2, Tilt 2 Android Development] reckert:
I was able to get a logcat going, and got some fragments of a log - it looks like its possible either the hardware, sdcard driver or the filesystem doesn't like 16gb cards. (I got a file000.chk file in my log directory that makes it appear it couldnt write to a block, then crashed). I've run some tests on the card on my laptop and am not getting any issues.

Once I moved everything to my 8gb card (After deleting some videos and music to make it fit), I have been running for a few days without issues.

In the logs I got :

<3>[ 86.637725] mmc1: Data timeout
<3>[ 86.637786] mmc1: DMA channel flushed (0x80000004)
<3>[ 86.637786] Flush data: 0000c003 242fe000 00000000 00400040 00070005 00008003
<3>[ 86.637878] mmcblk0: error -110 transferring data
<3>[ 86.900970] mmc1: Data timeout
<3>[ 86.901000] end_request: I/O error, dev mmcblk0, sector 10505150
<3>[ 86.901062] Buffer I/O error on device mmcblk0p1, logical block 10496958
<4>[ 86.901062] lost page write due to I/O error on mmcblk0p1
<3>[ 86.901092] end_request: I/O error, dev mmcblk0, sector 10505151
<3>[ 86.901123] Buffer I/O error on device mmcblk0p1, logical block 10496959
<4>[ 86.901123] lost page write due to I/O error on mmcblk0p1
<3>[ 86.901184] end_request: I/O error, dev mmcblk0, sector 10505152
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I saw errors like that all the time on my 16GB class10 card. Switched to a 32GB class 4 card and no more problems.
[Touch Pro2, Tilt 2 Android Development] shatred:
This latest kernel (15-4) together with the rootfs metioned in the first post is not working correctly on the Cherry pie V3 (the partition installation way)

The problem is: Everytime i try to enable wifi it just says: error (in the wifi "screen")

When i try this kernel + rootfs with the looped version (the xdandroid version) i have no problem at all, besides it being slow (that's why i was using the partition version)

When i use the kernel that came with the package (partition one) 1276 from 28/2 i have no wifi problems at all..

not sure if this information is any interesting, just wonderd if there is anything i can do to give you guys, so you can try and see where the problem lies.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Do a forum search for "wifi-nvram.txt" - think it might be in the FRX06 FAQ.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
SCBS aside, is this kernel still "more up-to-date" than the 5/9 kernel on glemsom?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm... I don't think so. I think autobuild has caught up, minus SCBS.
[Touch Pro2, Tilt 2 Android Development] husam666:
no more test kernels? :confused:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Is that what I said?

For the time being, there's nothing new to test. The focus is on getting every autobuild piece up to date with all the merge requests.

There might be another kernel test, but not for a while - and it probably won't be on .27, but I won't say much more on that, as it's based mostly on speculation on my part ;).
[Touch Pro2, Tilt 2 Android Development] husam666:
gotcha :)

thx
[Touch Pro2, Tilt 2 Android Development] shatred:
yeah i tried that, but it does not work, it still keeps saying "no mac adress availible"
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Has your wifi ever worked? If so, wifi-nvram is probably not the issue... At least I wouldn't think it would be the issue.

Triage it - does it work on autobuild kernels? Have you ensured the modules match the kernel? For troubleshooting purposes, have you renamed your data.img to try "fresh"?
[Touch Pro2, Tilt 2 Android Development] Starfox:
Tried to start WiFi tethering with latest autobuild, got an error. I also see an OOPS with some smd stuff about 3/4 of the way through.

http://db.tt/lfI4TtA

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm... this thread is for feedback on WisTilt2's test kernel, not autobuild, thanks.

Plus, wifi tethering is buggy at best.
[Touch Pro2, Tilt 2 Android Development] shatred:
just to be clear we are talking about the same cherry pie V3, i mean the one where it uses an ext2 partition on ure sd, so there is no data.img.

also, wifi works fine with latest autobuild kernel + latest rootfs

i also tried reinstal it, makes no difference
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't support that build.

If wifi works fine with the autobuild, use it. This test kernel has nothing to do with wifi, and if it breaks wifi, oh well - it's a test kernel....
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Okay iv tested this kernal with a plethora of unsupported builds and on cherrypie the kernal won't work probly unless you DON'T use modules! Rename them to just modules.tar.gz so dey are not opened. You will lose wifi but you will have all the other benufits of this kernal minus the strange side effects.

But if you try froyoB or cherryginger you can use the modules/zimage as is and wifi should work 100% also :)
[Touch Pro2, Tilt 2 Android Development] shatred:
But the only problem i have is that wifi does not,

i actualy do have scbs with this kernel, and all the other things.

ah well, i started using frx06 again even tough its getting slow on mah device lol
[Touch Pro2, Tilt 2 Android Development] manekineko:
Just a headsup, but autobuild still doesn't have the decreased amount of text on bootup still that enables calibration.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I don't think it ever will either, because that patch also killed the ramconsole and prevented us from collecting LAST_KMSG on crash/reboot.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea... I think the part that cuts down on the junk would be useful, just don't move the framebuffer's location, is that not possible?
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Is it possible to merge in the screen wake fixes?

On autobuild I get a few SODs a day and almost every time I wake the device I get a failed wake. (touching where unlock symbol is wakes the screen)

This kernel is 100% fine.

I have heard these changes are unmergable.

Is this true? If so can't it be ported?
[Touch Pro2, Tilt 2 Android Development] ryannathans:
It should be as simple as changing a few cout's.

Although I might be wrong, it has been a while since I have done much C or C++ (if that is what it is written in?)
[Touch Pro2, Tilt 2 Android Development] highlandsun:
cout? Are you nuts?

The kernel is written in C and assembly, not C++.
[Touch Pro2, Tilt 2 Android Development] Starfox:
One way to "fix" the clutter would be to address the known issues, such as the unbalanced IRQ dump, rpcrouter messages, mdp present, and any of the "this shouln't be used" type messages that have been long present in both auto and test kernel. Right now dmesg is filled with chaffs that make it difficult to pinpoint any issue. And the kernel should not need to report how the brightness is set every x second, that was useful when debugging the autobl stuff, the code is (or should be) stable.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This stuff takes time. Anything can be ported, it's just whether or not it's acceptable. WisTilt2 has had to change some of the ways he has implemented these fixes, in order to be acceptable by all for merging upstream to the mainline kernel.

The changes as they exist in this kernel are probably unmergable - please, be patient.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
New update. There are some reports of SOD's on the newest autobuild kernel, this is a kernel that is very close to the newest autobuild, just with some changes. See the first post!
[Touch Pro2, Tilt 2 Android Development] pdawg17:
I'm assuming this kernel will not work with the new audio/BT stuff from the other thread?
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Only been using newest kernal on rhod400 for a little bit so can't really help with SoD yet but the phone goes to sleep and wakes very fast.
[Touch Pro2, Tilt 2 Android Development] sportfisio:
Installed on spanish Rhod100,and get faster wake and sleep,and no SOD from now... This is getting closing perfection! Thanks for the job!

Enviado desde mi Touch Pro 2 usando Tapatalk!
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Will test but I'm not sure if I will much help because I havnt been using the latest autobuild also with your pre-scbs kernal+highlandsuns ril iv been gettn transition to full sleep in LESS than 1second (no blinking led even) 90% of the time. This kernal is damn near perfect ^-^

-will download and try new kernal
[Touch Pro2, Tilt 2 Android Development] randomblame:
was this merged? Looking at the commits today I see this:

anyone try it out yet?
[Touch Pro2, Tilt 2 Android Development] sportfisio:
I'm also interested on this... Any chances to make them work together?

Enviado desde mi Touch Pro 2 usando Tapatalk!
[Touch Pro2, Tilt 2 Android Development] Starfox:
I think I'll sit the newest autobuild out. Assuming the test kernel changes is what was used, I had back-to-back sleep of amber death, had to pull battery botth times.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] tovarish:
The 5/14 kernel seems to be quite stable on my rhod100. I cant wait to have all the latest developments (highlandsun's ril, f22's keymaps, scbs, better audio and bluetooth) in one package soon.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Been testing it for two hour or so. While I had about 3 (orange) SODs with the autobuild kernel, I just had a true Sod with this latest kernel. What happened:

Phone was in deep sleep, pressed EndCall (LED turned orange), then the menu/windows button to wake the phone (this sequence normally works). However, pressing the menu button turned on hardw button lights, and LED turned green, and everything froze (screen still off). Button lights did not turn off, and opening keyboard did not turn on keyboard lights.

Is latest-kmesg still unavailable?

Rhod100/AUO
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Yes. You've got to manually start logging kmesg when you boot the phone to get kernel log dumps. I forget the exact command for this.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No, the dropbox logs have been restored. As I said in the first post, this is a temp test kernel with changes minimal from autobuild.

I've been getting resets to WinMo after an incoming call - sometimes I can answer the call, sometimes it resets while ringing... I'll try to get some logs to WisTilt2.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
If you're running the audio/bt changes still that is why, I had to go back to 1324 from the audio/bt thread to fix it.
[Touch Pro2, Tilt 2 Android Development] reckert:
With the 5/14 kernel, I my phone had the SOD this morning (booted last night, put on charger and went to bed), here is the dmsg logs.

My other logs seem to be empty.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, I didn't even think about all those audio changes... they probably are heavily kernel dependent, crap. Thanks for pointing this out before I sent a bunch of logs off :p.
[Touch Pro2, Tilt 2 Android Development] reckert:
I got some more logs - things were running really slowly, and the screen was unresponsive, almost like the touch screen driver wasn't waking up.

For now I'm going back to the 4/15 kernel.
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
I Have Been Running the CyanogenMod 6.1 Touchwiz build with this kernel & never had a slowdown or one single SOD leading to a restart after a call. Im guessing its build related
[Touch Pro2, Tilt 2 Android Development] Starfox:
I was looking proc_comm_wince.c and noticed two things:

1) msm_proc_comm_wince() calls udelay(1) up to 10 million(!) times every time it's called. n/u/mdelay are busy waiting and from what I googled up should be only used when there are no alternatives.

2) msm_proc_comm_wince_exit_sleep() clobbers msm_proc_comm_wince_pending_ints if DEX_INT_VBUS was set. And from what I'm reading of the last patch that is not the behavior you want (perhaps you want to &= ~DEX_INT_VBUS instead?).

-- Starfox
[Touch Pro2, Tilt 2 Android Development] tovarish:
Does this latest test kernel also have the scbs stuff in it?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nah, and was only a temp test anyways. Seems the patch is already on the autobuild, I'll probably just pull it down.

All the code in the 'old' 4/15 kernel should also be on the autobuild - but I think there's still a piece here or there missing, so I'm leaving it up for the time being.
[Touch Pro2, Tilt 2 Android Development] xanathar:
I also think that the autobuild does not have all the WisTilt2 patches, I get failed wakes every second time with the audio routing kernel (based on autobuild, both 1323 and 1324), whereas the latest WisTilt2 test kernels were working perfectly. RHOD100/AUO here.
[Touch Pro2, Tilt 2 Android Development] tovarish:
The latest test kernel also works quite well in my rhod100. The only thing lacking for my regular usage is accurate battery level information.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm, the audio routing kernels are unique... Please test on the actual autobuild kernels before you say things like this.
[Touch Pro2, Tilt 2 Android Development] Luky522:
Hi, I've got a problem with this kernel. Everything is working fine, but android cant see my SD Card. When I go to Music there is a picture of SD Card and sign saing that there is no SD Card. It was working on older kernels, but on this no. I also have FAT32 partition and I've tried the thing with renaming the data.img. It let me go to the music, but the camera and the other things are saying that there's no SD Card. I have RHOD100
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Issue is not the kernel. Do a full format of the card using the HP Tool, FAT32. You can backup all the data on the card and restore, or start over. Doesn't matter.
[Touch Pro2, Tilt 2 Android Development] Luky522:
Will be ever possible to play games like NOVA, Gangstar and Modern Combat on booted android ?
[Touch Pro2, Tilt 2 Android Development] helicopter88:
I don't know why you posted in this thread

This is for Wistilt2's kernel tests not about android problems.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Weird, he also posted in the FRX06 thread. Seems he really wants to play those games lol.

I answered your question in the FRX06 thread, please don't cross post Luky522...
[Touch Pro2, Tilt 2 Android Development] muziling:
ACL NAND is updated and tested now, but his kernel is fail and hard to wake up, can compile an kernel which can be used for NAND version.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I know you've been told this before but...

You cannot use haret kernels on NAND. The code is significantly different, and the kernels are not interchangeable!!!

Hopefully that was clear enough...
[Touch Pro2, Tilt 2 Android Development] dsramesh:
I have using the latest build from the autobuild site and have noticed in the last few versions, the Market App crashes upon selecting <Downloads> and returns back the home page of the Market.

Any idea how to fix it or is it known issue?

This is on Rhod500 (Verizon TP2)

Thanks!

..Ramesh
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What do autobuild kernels have to do with this thread...?

At any rate, I seriously doubt it's a kernel issue. Sounds like a Market issue, try clearing the cache, and perhaps try a new data.img - but please, let's try to keep this thread on-topic.
[Touch Pro2, Tilt 2 Android Development] dsramesh:
I had the similar problem with the build posted here and thus moved to autobuild to try it out.

I will try again with a new data.image file

..Ramesh
[Touch Pro2, Tilt 2 Android Development] 44R48:
Density

Hi guys,

Nice kernel, is working great!!!

However there's one thing, when i wake up again the light density is on lowest level...is fixable?

I have a Rhod100_NL

Thanks guys
[Touch Pro2, Tilt 2 Android Development] baikal2:
Hello ,

I am a newbie and started fiddling with xdaandroid a few days ago.

I have some feedback .

I am running the FRX06 build on a RHOD400 with witstilt2`s kernel and RIL2 and F22`s rootfs .

Have been running with this setup for 2 days and have not encountered the SOD( amber Light ) so far. However I have noticed that if I miss a call the phone shows as searching for service. Even though the phone shows as searching for service , I am able to recive calls and can take the calls. There is no data though. I cannot make calls (the phone is searching for service).

I get over this by going going in and out of airplane mode. That gets the phone back into the regular(working data and and am able to make phone calls) mode.

I would like to submit logs (if useful) and wondering if there was a readme or any sort of documentation on how to submit the logs.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
http://xdaforums.com/showthread.php?t=1123129
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Is autobacklight on (under Display settings)? I think this was fixed in newer kernels.

I doubt you'll need logs, I'm pretty sure I know what's going on.

You said you're using a CDMA device (RHOD400) - is your carrier that you're using the phone with GSM? As in, your carrier is GSM but your have a CDMA phone?

See bug 120 for more (technical) information. This is a known-bug.
[Touch Pro2, Tilt 2 Android Development] baikal2:
I am on Sprint (CDMA).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You can receive calls... but it says searching for service? That makes no sense.

Unfortunately your configuration seems highly custom, and probably has something incorrect. Please go back to clean FRX06. If it still occurs on FRX06 (with no changes) then we can look at logs. Otherwise, wait for 07. I'm not going to support all of this testing stuff, it's impossible to pinpoint if it's user-error or not.

In other words - people, if you're going to use anything that is labeled "testing", you are on your own for fixing issues... Unless of course you feel you can pinpoint what is going wrong (as in, there's a bug), either don't use the testing stuff or sort it out yourself.
[Touch Pro2, Tilt 2 Android Development] baikal2:
arrrghhh,

I dont think I am using anything custom beyond what is already being used in the forums. I am assuming you missed my configuration in my earlier post. I am using FRX06 with F22`s rootfs and the new RIL2. The kernel is from the current thread from 5/14.

The FRX06 as it stands gives me a lot of SOD(the one with the amber light). I was trying to give feedback to help out wistilt2. If you are already convinced that the kernel is as complete as it can get, then I suppose I can wait for FRX07.

The beginning of the thread seemed to welcome feedback . I wasnt aware that testing was complete.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Testing is clearly not complete as this is a test kernel, but you're making reference to an issue that is possibly related to you tweaking the build beyond "stock" with the new RIL and due to you having non-stock things in the build, how can you be sure the issue is with the test kernel? Try a true "stock" FRX06 build with this kernel and see what happens, then maybe something can be done for it. You may have found a real bug that needs to be reported, but unless it can be narrowed down, nothing can be done. Just set up a new build on the card, doesn't take much time or space.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I read your setup, and it's not stock what is included in FRX06. I can't tell if the rootfs is causing the issue, the RIL, the kernel...

I also have no clue if you implemented them correctly. I'm going to assume you didn't, and ask you to triage it yourself - mainly because I have the same service, same device, and it does not exhibit this issue.

However, this kernel is getting a little long in the tooth - and you're not using the kernel I would recommend either. I usually tell people to grab the 4/15 kernel, if only to partially resolve the slow wake issue.
[Touch Pro2, Tilt 2 Android Development] 44R48:
no even when set it on autobacklight it is still on minimum, and there is another bug...freezes after a call...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Try autobacklight OFF - see if it makes a difference.

I don't have the 'freezes after a call' issue at all. Need logs.
[Touch Pro2, Tilt 2 Android Development] F22:
Rhod100 Panels

WisTilt2 rewrote his autobl code not to use microp, and it appears that rhod100 panels are no longer having issues. I wouldn't celebrate just yet however. This may actually be due to a bug. The panel wouldn't have an issue waking up if it never was fully turned off...
[Touch Pro2, Tilt 2 Android Development] gnnash:
I have experienced a very erratic data connection with all kernels, but never experienced this issue until this kernel.

I try to fix it by toggling airplane mode, but the phone won't let me exit airplane mode once I enter it when this is happening.
[Touch Pro2, Tilt 2 Android Development] kwoodyusa:
I dont know why I have this problem with the the key tones. I tried several of the older kernels and still have the problem. To add more info it also happend when recieving a call on call waiting. My phone is an att tilt 2. I also moved the SD card to another tilt 2 and had the same problem.

What phone do you have? Could it be something different in the model?

I agree with the buzz, also the volume is low compaired to the music on spk.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I doubt it's the phone model... I have a RHOD400, but the guy who is developing these kernels has a RHOD300 (aka 'Tilt2'... as in WisTilt2...?) himself :p

At any rate, is this problem only with receiving a call on call waiting? Perhaps that's the issue, I'm not sure I've ever taken a second call in Android... let alone with the speakerphone since that basically just started working.

Either way, I guess I'd just like to ensure you're running all of the newest (and clean version!) of the FRX03 system image, tried a new data.img, all that jazz.

If you can reproduce the problem consistently tho, that's definitely something to look into. I'll try creating a call waiting scenario.
[Touch Pro2, Tilt 2 Android Development] ksper6986:
best

this has been by far one of the best kernals ever , i dont really have any problems beside the usual glitch great work WisTilt2 and whomever else is involved and thank you arrrghhh for posting this and taking your time to answer questions
[Touch Pro2, Tilt 2 Android Development] Raul^:
I will do what I can to try and troubleshot the problem. I tried to install Droid Explorer too, but still no joy. I'm not sure if in the drivers files there is something about touch pro 2.