yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I always do ;).

I'm not sure where he's at on it, but we probably will need some people with crappy service areas - or frequent SoD's to test. Hopefully we can get the femtocell/airave issue fixed at the same time!
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Well you know who to ask if you want frequent SODs!
[Touch Pro2, Tilt 2 Android Development] muziling:
1/3 kernel battery drain fast than before, seems only standby 12 hours, last kernels can standby 24 hours.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
That is the only time I get SODs, when I loose signal. other then that, tilt2 with droid is working perfectly. Love it!

I hope wistilt can figure out a way for us not to get SODs when we loose signal.
[Touch Pro2, Tilt 2 Android Development] jphaus:
I have to agree, battery life has been AMAZING for me in the 1276 version and FRX05. So happy.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Look around, you're one of the few complaining about battery life. Make sure the phone is sleeping correctly - I have the same device, RHOD400 - and battery life is fantastic.
[Touch Pro2, Tilt 2 Android Development] codedesignr:
What is the Airave issue? I ask because I have the Airave 2 from Airvana for Sprint (the newer one with 3G) and Android runs excellent.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
If you have a newer one, seems there isn't an issue. Others have SoD's like crazy when using their older airaves/femtocells. Same thing happens with poor service areas.
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
let me know if you need me to test anything. I can easily walk in and out of door to make me loose reception lol
[Touch Pro2, Tilt 2 Android Development] Atmosphere:
1 March Kernel, FRX05 - Froze up twice already today. Rhod100. Seems a bit worse than on FRX04.

Battery life seems amazing

doesn't seem to lose time while charging anymore - probably related to FRX05.

How do i find out what panel I have again... it's been a while since i looked. I did a DMESG on my phone and found the following. Is this normal for it to keep trying different panels till it finds "Panel 13"?

[ 1.592590] raphnavi_tp: Registering Raphael NaviPad driver

[ 1.592926] htcraphael_init_panel: Initializing panel

[ 1.592926] htcraphael_init_panel: disabling raphael panel

[ 1.592956] Disabling Diamond Panel

[ 1.592956] htcblackstone_init_panel: Initializing panel

[ 1.592987] htcblackstone_init_panel: panel does not apply to this

device, aborted

[ 1.592987] htckovsky_init_panel: Initializing panel

[ 1.593017] htckovsky_init_panel: disabling kovsky panel

[ 1.593017] htctopaz_init_panel: panel does not apply to this device,

aborted

[ 1.593048] Panel type detected: 13

[ 1.593048] htcrhod_init_panel: Initializing panel
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
13 is AUO-panel i thought
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, it's normal to go thru all those panels before finding the correct one. Christiaan91 is also correct, 13=AUO.
[Touch Pro2, Tilt 2 Android Development] shatred:
since today i am getting troubles with the 3-1 kernel.

been using it since 3-1 and until today it worked fine.

but, today i had 2 failed wake ups, but not an normal failed wake, no.

when i tried to wake it nothing, realy nothing happend. the light just stayed solid green, no matter what button i press it stays the same.

Even sliding open the keyboard doesnt work (i noticed that the keyboard light did not go on) so i am assuming that the phone just froze in deep sleep?

I am using this kernel with the latest GB (created an new data.img with this kernel so it was an complete clean instal)

any thoughts on how this suddenly happend today?

because it was working perfect 2 days long =]

very good battery life etc.

ps. i found an little bug, its about the music player. Some songs it freezes, and when a song does work the sounds freezes every 20-30 secs for 2-3 secs.

i know this is not an main concern but its just to let you guys know =]
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Classic SoD. Usually seems related to poor cell service areas, or transitioning between roaming and not roaming. Not sure the entire details, as it seems kinda vague - but that's what a true SoD is. No matter what, the phone will not wake.

You can try to pull logs from /data/system/dropbox, but WisTilt2 is pretty confident it's a RIL issue.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I'm pretty sure of that too. If I switch to Airplane mode, the phone will sleep for several hours and still wakes up instantly. If I leave the radios on, it will hang within an hour or two of sleeping; the LED will switch from green to orange and nothing will wake it up. (Even with this latest test kernel, FRX05 system, and latest F22 rootfs.)
[Touch Pro2, Tilt 2 Android Development] snowmaiden11:
Been having the same deep sleep issue as others - a few hours of working perfectly, and then can't be woken up at all. But I did notice something very strange yesterday - when I put it to sleep, it started BLINKING green instead of staying a solid green (looked like when you have an unread msg/missed call in WinMo). This is the first time I've seen anything like this in Android - and it didn't resolve after a few minutes, this lasted for hours until it went into the deep SOD. Otherwise, this has worked like a dream - instant sleep/wake, very responsive, great battery life

***EDIT: just double checked the first post and saw that the blinking is a new feature and I'm an idiot"
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Since I installed this version (both on FRX04 and 5) I see notices about not being able to find files at boot, it mentions:

insmod: can't read 'lib/modules/lzo_compress.ko'

insmod: can't read 'lib/modules/lzo_decompress.ko'

insmod: can't read 'lib/modules/xvmalloc.ko'

insmod: can't read 'lib/modules/ramzswap.ko'

I had it first in FRX04 (just copied the 3/1 kernel as I normally do)

then I tried downloading the libs from viruscrazy thread

then I tried everything with FRX05 (on fresh install)

Sleep is also terrible, I takes minutes to get a solid green, if it goes solid at all. Which would indicate something wrong with my install I think?

--EDIT: I'm leaving the camera alone btw.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I pulled the libhtc_ril_wrapper.so from the HD2 git repo and installed it on my TP2. I also installed the libhtc_ril.so from my G1. This combination gets no in-call audio, unfortunately. Also, it suffers from frequent random lockups, so not sure this is really a viable path.

What does work: sending/receiving SMS worked fine. 3G data connection worked. Calling and answering "works" (but you can't hear anything or say anything). Sending DTMF tones from the keypad works. The phone is transmitting something, it just seems like some audio mux is not connected properly, because on the other end I can hear static on the call, and the static turns to silence when I hit the TP2's mute button.

Kind of a shame.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Been trying the 3/1 kernel the past day or two. Battery life is great, however:

Shortly after arriving at my desk, the phone indicated a wake from sleep (orange LED) and stayed that way. Attempting to turn the phone on or do anything resulted in nothing. (Sounds like the above description of a classic SoD, except the phone transitioned from sleep to not-sleep as indicated by the LED before dying).

Next reboot, I tried to put the phone into airplane mode, it hung.

The next reboot it started in airplane mode.

At my desk, I have very weak signal, frequent transitions from 3G to EDGE, and often simply no service at all. So yeah - the issue definitely seems related to weak signal.

Edit: Just had a spontaneous reboot. Device was not in sleep, was actually running a filesystem search. Hope it doesn't hose the data partition by corrupting my call log file like it did before.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Can we be sure that the problem is within the RIL itself and not how the kernel supports the RIL?

I've been reading through ril-htcgeneric.c and brushing up on my AT commands (been a while... Did a bit working with Iridium modems a year and a half ago but that's it...)

Most of the problems do indeed seem radio-related, but there is a more common theme here - Nearly all failure situations seem to occur when the phone is sleeping and there is an unsolicited response coming from the radio. The RIL turns many of these off when sleeping (see requestScreenState), but not all (and it can't - some stuff HAS to be handled):

1) Issues in weak signal areas - The RIL doesn't fully turn off unsolicited CREG responses. So a change in network registration (transitioning from a femto to the "real world", transitioning from UMTS to EDGE, transitioning from EDGE to no signal) is going to cause a CREG to come in even if we're sleeping.

2) Issues with incoming calls - this is also going to cause an unsolicited event from the radio

So we could be getting hosed in kernel space when the radio tries to wake the main CPU to handle an unsolicited response, or we're getting hosed in the RIL by an unsolicited response we don't handle properly.

I wonder if there is a way to log unsolicited responses (onUnsolicited() in htcgeneric-ril.c) to see if we're getting hosed before or after that code section, and what the unsolicited response is? I'm assuming the normal Android LOGx() macros won't work since I don't think ADB logs get written to a file?

Edit: Somewhat unrelated question, will values of pm.sleep_mode other than 1 completely break, or just not provide battery life as good as sleep_mode=1? (not considering 0 here, assuming it is totally broken, but wondering if 2 and 3 are a valid compromise for when I'm not in a debugging mood.)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Definitely not an expert on this subject, you seem to know much more than I do in fact ;).

Patches are always welcome! WisTilt2's radio programmer is going to rewrite our RIL from the sounds of it - only good things can come from that! He said to hopefully have something to test next week.

As for your last question, WisTilt2 said that he now enforces pm.sleep_mode=1. So as I understand it, no matter what you put in (even if you have nothing) 1 is forced.
[Touch Pro2, Tilt 2 Android Development] Eodun:
Not an expert, but it sounds as a corrupted modules file. Try re-downloading it, and of course don't uncompress modules tar or rename it :rolleyes:
[Touch Pro2, Tilt 2 Android Development] toadlife:
IN the HD2 you have to run a file called "CLRCAD.exe" file before booting and it reportedly "enables sound". Perhaps this is related to the ril wrapper?

Just a wild guess.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Happens to everyone. I don't believe they are included in the kernel and they don't seem to have any effect as far as I can tell.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Thanks for the hint. I tried running that but it just crashed device.exe; I guess it is too specific to the HD2. Can't find the source code for it anywhere to see what it does, all the google hits are only for clrcad.exe.

Beginning to suspect that this really is a kernel issue. The libril stuff only takes requests from the system and spits them out as a series of modem AT commands, and reads response messages from the modem. I can't believe such a simple userland function can cause a system lockup.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
One small "bug" in these latest kernels - the /init script always looks for /data/modules/wlan.ko to extract its build version string, to compare it with the currently booted kernel and see if it needs to extract a new modules.tar file. But in these latest kernels, there is no wlan.ko file in the modules.tar file, so it always extracts it on every boot, even when it doesn't need to.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Another hint on the crashes - I turned off mobile data, and now I'm not getting any more SoDs.
[Touch Pro2, Tilt 2 Android Development] codedesignr:
Probably explains the Femtocell/Airave issue. Phones connected to the original Airave without data are getting a lot of SOD's. However, phones connected to the new Airave, which has 3G data, are working excellent.

Edit- The original Airave does do data, just at 1x instead of 3g. People in poor service areas most likely would be using 1x as well. People who are roaming on Sprint use 1x with analog roaming. All 3 of these conditions are common examples where people received frequent SOD's. Maybe it has to do with the phone switching data modes.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
These can be completely ignored, those modules are now built statically in the kernel instead of as separately loaded modules. The only bug here is that /bin/userinit.sh in the rootfs is out of date and ought to have these two lines removed.

These last two are because they're using a very old release of compcache code and its Makefile doesn't actually work with the version of the Linux kernel it's built against. So these two modules fail to be built. Dunno why nobody has bothered to fix it so far, it's a simple fix which I've attached here. These modules provide a compressed in-memory "swap" partition; it's a way to get a little bit more space for apps when you have multiple apps active, without needing to swap to a swap partition on your SD card (and wearing it out prematurely). I guess no one here has really missed it, but it's a very handy feature on the G1. Also it's part of the mainline Linux kernel now (2.6.35) so it definitely works well.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Iv been hit with my first kernal-network problems today and boy did dey hit hard. . . .. .about 5times in an hour while in a shoddy coverage area and each time it resulted in a hard-reboot in the end (switching into/out of airplane mode froze up) and everytime I tried to search for networks I got a full freeze up which I had to reboot to solve.

But I know ye are aware and working on this and am sure ye will find the problem :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What does this have to do with testing WisTilt2's kernel?!?
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Seems unrelated to me... Would be nice if the poster above had linked to more than just a twitter feeds (such as maybe a specific post and why they were linking it)?

Don't have time to search through that entire feed for something relevant to this thread...

I spent most of this evening upgrading to FRX05 (well, not quite - I built from the git repos), going to submit my GPS patch in the next few days then move to something else - like maybe helping to debug this. Since I'll be in an area where issues are common due to weak signal, some advice on how to print debugging info from the RIL and have it saved would be useful. (printf() goes nowhere, LOGD/LOGE/etc go to ADB logs that don't seem to be persistent through a crash. Something that gets saved to dropbox would be useful.)
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Here's how I believe the dropbox to work based on the conversation and evidence I have seen:

All logging output gets stored in memory and can normally be accessed by dmesg

This memory is persistent through reboots (aside from power loss I'd assume) for the most part but upon booting into windows is potentially mangled by other writes to that section of the memory.

Upon booting into android again, the log is attempted to be written to the dropbox folder before it is overwritten.

I'd guess this method makes more sense than directly writing to SD because of the negative effects (speed, reliability) of writing directly to the SD.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Using something like GenY Dualboot helps, because it causes HaRET to run earlier before a lot of Windows startup processes have had a chance to overwrite memory.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
I'll have to look into that - Sense takes forever to load on my EnergyROM install, and at this point I think I'll only need WinMo for QuickGPS.

Does the dropbox catch Android LOGD/LOGE messages (e.g. stuff that appears in logcat) or just dmesg stuff? I sort of recall seeing more than kernel messages in the logs, but no Android logs (e.g. logcat logs) - I'm thinking of adding some debug logging to the RIL, but I'm not sure exactly how to do so. dmesg is usually for kernel space messages, I might be able to output stuff to the ADB logs, but a hung phone won't be able to view those logs.
[Touch Pro2, Tilt 2 Android Development] rcgators:
Since this is easily reproduced, writing to the SD for a test kernel wouldn't be a bad idea. We won't need to run it for long before getting some good logs.

I was also looking at the source the other day but I don't have a build environment and figure someone else will get to it before I can dig up all the parts to make my own builds.
[Touch Pro2, Tilt 2 Android Development] accountabc:
I tested the latest (march 1st) kernel on my blackstone with FRX05. My findings:

-Boot OK

-Camera OK

-Camcorder + sound OK

-Wifi: it says "Error" when trying to enable

-3,5mm: working

-Audio playback: stuttering every couple of seconds
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
3/1 test results

So after testing the 3/1 kernel for 4 days on FRX05 (format and clean install) I noticed the following things.

- As for insta-sleep; results were quite poor on my device; takes up to 1 or to minutes to go to full sleep

- Wake was more or less OK, maybe 1 failed wake every 20 wakes

- One or two freezes every day (not in sleep, either with screen on, or off but with orange LED)

And then since noon today, it seems The Timebomb went off again :D freezes and random reboots of Android, or into Winmo everywhere, at least 8 or so in the last 3 hours.

So for my device (100 / AUO) the 26/2 kernel is still the most stable, and that one really had insta-sleep! But I have only ran that one for 1.5-2 days so I'm not sure about the timebomb with that one. I'll go back to it anyway, and let you know if anything strange happens there after a few days.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Just to explain something I think was misunderstood if dats ok ^-^ 26/2 and the latest kernal both have insta sleep. . . .but in the 26/2 full green led meant arm processor sleep, not microp, so not 'full sleep' (untill about a minute or so, but you couldn't tell ). While in the latest kernal its changed for debugging porposes, when you press sleep you don't see orange rit? Dat means you still have insta-sleep ^-^ but not full sleep . . . But I don't tink we ever had 'full' insta sleep :) because when charging or gps is on for example it never transitions into full sleep.
[Touch Pro2, Tilt 2 Android Development] shatred:
i think with full sleep he means deep sleep. like arrgghh said, blinking green is half sleep and its trying to go into deep sleep, you know when this happend as soon as the led is solid green.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks for the feedback, but did you not read the first post?

Indeed. WisTilt2 quickly realized how that could be deceiving, and added that additional debugging ability.

Now when you say 1 to two minutes, are you serious? Longest I've ever had is maybe 30s, and that is related to the RIL - which is hopefully being rewritten and we'll get to test soon! :D
[Touch Pro2, Tilt 2 Android Development] shatred:
mine takes 6 secs and then its solid green =] and sometimes even 3 secs :p

BTW how do i know if i have an eid panel or aoe or something like that? cause i think that the cam only works on rhod100's with an eid panel. so far the only people with an rhod100 and camera working said they have an eid panel.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
to get any confusion out of the way, on my device both kernels (26/2 and 1/3) go from orange through blinking green (trying to go to full sleep) to solid green (full sleep) when pressing power.

With 26/2 it takes .000001 sec (really insta-sleep) up to 5 sec max, depending on the app that I have open at that time. Batt life 31h max.

With 1/3 it takes at least 5 sec, with a max of 1.5 minutes. Batt life max 14h.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
I have an AUO panel rhod 100, and the default camera app at most shows me an initial image, then doesn't update after that. The buttons still respond though. With some of the apps off the market, it behaves a little better, though I'm still yet to take an image :(

However, we're not debugging the camera in this thread, so pretend you didn't read any of that.

Oops!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You battery life is that significantly different between those two kernels...? Battery life should be if anything better on the newer kernel, short of maybe some wakelocks from the cam code (which does need to be cleaned up it seems)...
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Well thats what I thought too, however the daily results show otherwise. But I have noticed it from 28/2 onwards. The weird thing is that I seem to be the only one here with that problem, but perhaps other AUOs can comment?

EDIT: btw, I haven't touched the cam on purpose, to not disturb testing the rest
[Touch Pro2, Tilt 2 Android Development] shatred:
its EXACT the same story for me, probably i have an AUO panel then >.< dammit i want eid lol
[Touch Pro2, Tilt 2 Android Development] shatred:
i can confirm this, the 26/2 kernel had longer battery life then the newest 1/3
[Touch Pro2, Tilt 2 Android Development] Atmosphere:
I unplugged my phone from the charger at 6am this morning - at 16h00 this afternoon I plugged it back into the charger... i would have probably gotten another 1 or 2 hours... but the battery life is not as good as FRX04 I think.

Random SOD about 3 times per day

Random Reboots
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm... We're not comparing system images, we're comparing kernels...

Also, assuming you're comparing the main GIT kernel to this one, this kernel you should see significantly lower drain - assuming it's actually going into deep sleep correctly.

Seems the AUO panel folk saw a drop in battery life from the Feb.26 kernel, which is baffling. I'll ask WisTilt2, I'll probably need some logs - just not sure which kind.

Random reboots can be all sorts of random problems. SoD is caused from spotty service - when I'm in good service areas, I never get SoD's.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The TI wlan Wifi driver is missing from this kernel build. Dunno if WisTilt2 omitted it intentionally or not, but it causes other problems too (e.g., on bootup the init script always extracts the modules tar file even though it doesn't need to).
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
I'd be glad to provide logs, but I heard they were somewhat disabled?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well if the phone is running, no problem. It's the historical logs from a reboot situation that are not working (and I believe are still not working, not sure why TBH...)