yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] kastg1:
So far I've been running the new 3/11 kernel for about 10 hours -- no failed wakes (with the orange LED) or SOD's - before this kernel I would get ~1-3 failed wakes per day. However, I have had two reboots (yay for gen.y dualboot!) -- the first happened while I was responding to a text message, and the second occurred while playing Robo Defense free a few minutes ago. I couldn't discern any noticeable pattern between these two events besides having used the phone for a longer period of time than usual (i.e., texting while sitting in a car for ~20 min, playing robo defense for ~20 min).

I also noticed (today at least) that getting from blinking green sleep to solid green sleep took noticeably longer longer on this kernel than the last -- on the 3/1 kernel I'd get full sleep in less than 5 seconds, while as on this kernel it's averaging about 30 seconds or more for full sleep, and sometimes never reaches full sleep unless I turn on and off the screen again.

Other than that, things look good -- keep up the good work!

I'm running FRX05 and the 3/1 rootfs from F22 on a Rhod400.
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
Ok, I have to admit it: this kernel boots FAST!

Also the problems of waking (screen on, back of, push again: on for a half second...) are gone.

But one thing on this kernel is very anoying: The time offset! Every minute the time get's about 1 second or more behind. This wasn't that bad on the FRX05 release...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Interesting, I don't think anyone has pointed out increased clock drift with this kernel.

I think most of us just use ClockSync and ignore the drift. Not sure what would cause it, but until we resolve the root cause of the clock drift I wouldn't worry about it TBH. That's another one of those very minor bugs, but is also very annoying - trust me, I know it's annoying. Just small in the scheme of things ;).
[Touch Pro2, Tilt 2 Android Development] QuentinX5:
Wouldn't a way to technically fix the drift from the clock be to, instead of updating the time, update the way in which the clock works? Like the way it counts or something (this coming from someone who does not understand how the clock in Linux runs)
[Touch Pro2, Tilt 2 Android Development] highlandsun:
For what it's worth, I see a lot of clock drift on all of my Linux machines, when there's no NTP service running. And even my G1 drifts noticeably over the course of several days uptime. Since we have access to highly accurate time (GPS) we probably ought to file a bug report with Google and change the framework to actually use GPS and NTP time to update the system clock.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
There are a wide variety of clock sources Linux can use. In many cases there is a system RTC that is independent of the CPU. In other cases, the system can use a timestamp counter within the CPU. TSC is almost always the wrong choice though, as it becomes unstable in CPUs that can scale clock frequency.

I don't know which clock source we use, I haven't had enough time to poke that deeply into it. I know we don't have a /dev/rtc of any sort.

Many systems are expected to drift, and Linux has provisions for "calibrating out" simple drift from the clock. However in our case, it seems usage-dependent - for example, hitting the menu button repeatedly can cause you to lose time pretty rapidly.

It looks like our default clocksource is "jiffies" - available ones are "gp_timer","dg_timer", and "jiffies" in this kernel. Not sure what these various time sources are.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
I got 2 reboots a couple off minutes ago.

Both after using the market to update apps.

Logs are empty in the dropbox :(
[Touch Pro2, Tilt 2 Android Development] rodrilobo02:
Hi all,

Where can I get the newest kernel built??? I read some new updates about bluetooth and want to test.

I tried to get it from http://glemsom.users.anapnea.net/ but seems like it stoped build kernels since february...
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Latest official kernels

Haven't heard about a BT test kernel yet, so i don't know.

EDIT:

Realized that's the same website.

There are probably no new kernels.

Be patient.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, our RIL is setup to only handle so many data streams - this causes reboots when you have too many running simultaneously.

RIL is being rewritten, and dropbox kmsg logs are going to be missing for a while... Sorry!
[Touch Pro2, Tilt 2 Android Development] viruscrazy:
Well, BT tests might comes directly into the build. I've submitted the patches for bluetooth to work on rhodium. Next step is the audio rework I'm finishing, si that bluetooth headset can work (I've made it work, now it's just some cleanup, testing, ...).

Jerome
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
Where will this be posted or will it be under a new post?
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Got more issues with this new 3/11 kernel. Last night I went to check something on my phone and I had just a blinking green led, but it was also a SOD. I had to reboot. I rebooted and stuck it on the charger since I was going to bed. I put up the clock dimmed with my alarms set. This morning I took it off the charger after the alarm rang. It was running smooth and fast.

The only thing I have done today is email is checking every 15 minutes, a few phone calls, a few text messages and that is it. All of a sudden about 3:00pm EDT or so I realized that clocksync wasn't updating the time anymore unless I manually did it myself. It was also sluggish and too multiple taps of the screen before it would acknowledge key presses. The end button would not go to home most times nor would it end phone calls. Other times it would work fine, but even after syncing the time with clocksync it still got out of sync and didn't fix itself again.

Also the phone will now not go into sleep mode anymore. I have no app running other than email, clocksync, voice search, and all the normal google processes. I have never had a problem like this before having that stuff running.

I had this sluggishness issue yesterday also and had to reboot mid-day. This was not happening with the previous test kernel. The previous one was the best one so far. I am going to revert back to that one for the time being because it is stable and the autobuild kernel is not stable for me either due to excessive SOD's.

I am running a Rhod400, and all places I am normally have 4-5 bars, so I am having no signal issues. Here is my dmesg dump while it has been acting up. I am about to reboot.

I had to break the file down into three files due to the stupid forum rules of not exceeding 87.9kb. They are in order from A-C. Sorry to post so much, but since I am unsure if I can even recreate the problem since it has been happening with no pattern or reason I am not sure rebooting and trying to recreate it is going to work. It looks to only start happening after running at least 5 hours or more usually.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Since there's really nothing to test, jb is just going to release it - as he stated, the kernel code is done, just need to fix the userland side. The cam code had a lot of variables and needed to be tested on each device - BT is hopefully going to be device-agnostic (relatively speaking) so there's really no need to put up any public tests, as it should "just work".

Thanks for your hard work viruscrazy, really do appreciate all you've done for this project!

I had something similar yesterday - no rhyme or reason, phone was just DOG slow. I plugged in ADB and looked at top, load averages were in the 15's... not good, but the other weird thing is there was no process that was hogging all of the cycles. So I really have no idea what was causing the slowness. Reboot, fixed...

I wonder if the battery code is doing more than we think, I've had a lot of weird reports on this new kernel.

Feel free to revert to an older kernel, just please don't post it here. I want to test stuff going forward, I don't want everyone grabbing older kernels - thanks!

Just saw an update to your post - the 87k limit seems kinda dumb too, but if you zipped it would've been no prob ;).
[Touch Pro2, Tilt 2 Android Development] xanathar:
I have another issue with the latest test kernel (3/11). Alarms do not set off if the phone is in full sleep (solid green). As soon as I wake up the phone, the alarm sets off. This was never an issue on the older test kernels, I was using it since months. A reboot also did not help.

Rhod100 (AUO) here.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
That is good to know if I ever decide not to charge the phone and have an alarm set! ;)I usually always have it charging thus no deep sleep. Glad you posted that though, because I don't want to not wake up or miss something, as I am finally comfortable trusting xdandroid to be my alarm clock as it has been rock solid previous to this kernel! ;)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, I've noticed this partially - what I mean by that is some alarms have gone off for me, while others haven't until I wake it.

I'll do some more testing on this and get back to you, thanks.
[Touch Pro2, Tilt 2 Android Development] xanathar:
Thanks arrrghhh. Here is a dmesg log from my phone after I made some tests with the alarm. (s/hxxp/http)

hxxp://dl.dropbox.com/u/5179008/dmesg_1503.txt
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Heh, you'll be able to post links with 5 posts IIRC ;). I'll take a look, see what I can dig up. Thanks for the log!

Update - got home, ran a test - alarm went off just fine. Phone was in deep sleep, solid green LED - I guess it's possible there's something different about lengthier sleeps... I experienced the same issue yesterday morning. This morning I experienced something entirely different - a dead phone! Not sure what happened there, but suffice to say I haven't had an alarm work correctly once so far this week :p.

At any rate, I can't really make heads or tails of your logs - nothing is jumping out at me. But I'm far from an expert on analyzing logs. Hopefully I run into WisTilt2 tonight, if not I might just shoot him an email... Ugh, I hate intermittent bugs that aren't easily reproducible! But if they were all like that, this would be easy :).
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
Is it possible that due to ClockSync correcting my clock every 15 minutes the phone forgets to ring his alarm?

Example: The alarm is set tot 8h00

The clock is at 7h59 and than Clocksynck kicks in and corrects the clock to 8h01.

Is it possible that when this happens the alarm doesn't go off?

(I was wondering this because I needed to get up this morning at 8h00, but I woke up at 10h30... I don't think my boss likes that ;-) )
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, yea I can't imagine my boss would appreciate that either ;).

15mins is pretty frequent as well, I have mine set to every hour - phone woke me up no problem.

Since Android isn't perfect yet, might want to set your clock to alarm as well - did that this morning myself as I had to get up extra early and I was never going to wake up on time if my phone failed me. Worked fine this morning, so I am very confused by this bug.
[Touch Pro2, Tilt 2 Android Development] dcmedic:
question?

Are the RIL updates being talked about, going to address the SOD issues with limited service areas?

Sent from my MSM using the XDA mobile application powered by Tapatalk
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, among many other things RIL related. Mostly benefits CDMA to be honest, but that's because most of the code for GSM was already in the RIL - CDMA had the most to gain :p.

That's probably one of the reasons why it's taking so long - lots of code to flesh out for CDMA.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
I don't think anyone knows the answer to this with 100% certainty. There is speculation now that the SoDs have more to do with the processor, clocks, battery voltage, and other things that are way over my head. The low signal may just be a stresser (the radio, and therefore the battery, works harder when you are in a low signal area) that pulls juice from the processor long enough to throw off the clocks. Again all way over my head, but that is the theory being floated around. So that may not be the RIL at all, but the SoDs are being investigated.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This is a good point ^^.

My theory is there's multiple reasons for the SoD, but if it does all go back to clocks... that's not out of the question either and perhaps poor service does just exacerbate the issue.
[Touch Pro2, Tilt 2 Android Development] dswaggz:
@arrrrghhh any news on gsm support for nand an watz up with the miui rom how bout some nand love on that
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What does this have to do with kernel testing?
[Touch Pro2, Tilt 2 Android Development] dswaggz:
Sorry jus askin if there was gsm support you would have a lot more testers
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This kernel works great for GSM.

Please, read the first post of the thread - perhaps that will help you understand the purpose of this thread?
[Touch Pro2, Tilt 2 Android Development] dcmedic:
The theory of a stressor sounds very feasible. I have noticed that when i go to an area with no signal whatsoever, I have no problems.

Tilt 2 Tapatalk
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Um, this kernel and the builds out there work just fine for GSM.

It's my "daily OS" for the phone now.

If you're referring to NAND - this is not a NAND testing thread. NAND is nice on paper, but IMO we have too many other blockers to focus on before making a significant move to NAND.

1) Stability and power management - it's a lot harder to update kernels and test new ones when running from NAND

2) Fixes in userland libs - Similar, it's a lot easier to test fixes to a library when running from SD than from NAND

3) Stuff that is simply not supported in Android yet, like XTRA (QuickGPS) for the GPS - No one who expects to use the GPS of their phone should go NAND at this point. People who expect to use GPS may never be able to go NAND due to the lack of documentation on the XTRA interface - some people are looking at it, but it's a fairly complex beast and the little documentation we have on it makes people's heads hurt.
[Touch Pro2, Tilt 2 Android Development] xanathar:
GSM also has its problems: I cannot get data to connect on boot, I have to force 2G in the network settings when the phone boots. Deactivating that option (Use only 2G networks) gives me 3G/UMTS/HSDPA, but then I experience userland hangs (amber light) in poor reception areas (probably occurring while switching 2G/3G).

Edit: Do the CDMA changes also apply to the EU 3G band (WCDMA)? If so, these problems might also be solved.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Just with this kernel...? WisTilt2 is GSM himself, and certainly does not have this problem - I'm not aware of anyone else with this issue either... Perhaps it's your provider? Under what circumstances does it work correctly?
[Touch Pro2, Tilt 2 Android Development] xanathar:
No it was like this from the day 1, maybe since a year or so. I'm on o2 germany, and had many different kernels and data images since then. I also remember me helping another person on o2 germany who had the same problem.

On a fresh boot, Settings -> About Phone -> Status shows Mobile Network Type as Unknown, and refuses to establish a data connection. After forcing 2G (the option is disabled, just going into the APN submenu and then back enables it :) ), it says EDGE, and I get a data connection. If I uncheck it, it says UMTS. That force 2G option is not persisted, so I have to do this on every boot.

I can post radio logs from my phone if you think it can help.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Interesting... Well, logs would probably help - I probably won't be able to decipher the problem, but I can pass on this info on to WisTilt2, but it sounds like something funky with that carrier.

I don't know why your fix would work either - but hopefully it'll help us narrow down the issue. Thanks!
[Touch Pro2, Tilt 2 Android Development] DopeyOne:
Left my phone on overnight and woke up to no radio service.. only way to fix it was a rebot.. logs show an AT< +ME ERROR:30

radio log attached.. frx05 11/3 kernel

@arrrghhh sorry to hear peeps are giving you such a hard time, don't let it get to you.. you and the devs are doing an awesome job! Love your work! I'll stop wasting thread space now..lol..
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, I just ignore those people. Mods cleaned it up, for the most part from what I can tell.

At any rate, I'll see what WisTilt2 thinks - he is the wizard here - but he is also in the process of rewriting the RIL.
[Touch Pro2, Tilt 2 Android Development] besho2222:
Sorry it's my first feedback on a testing build ever, so I may sound like a noob, correct me please, I want to help really:

Device: RHOD210

FRX05

* it's the best kernel I've ever tried

1. much faster, really, best performance till now.

2. 3D performance is gorgeous.

3. camera works smoothly, didn't try the video.

4. BT doesn't work.

5. WiFi is perfect, so fast too (using WPA2-PSK)

6. fast sleep and wakeup

7. faster boot time ? (or it's just me being impressed by the kernel :D)

8. calls are great.

That's for now
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
BT doesn't work on any build (yet). Fixes are in the works for that.

Everything else you've listed is what's been put in - boot is faster for sure, and sleep should be MUCH faster. You're on GSM so you probably won't suffer from the slow sleep bug after calls too ;).
[Touch Pro2, Tilt 2 Android Development] muziling:
11/3 kernel, Alarm clock not alarm me at 7:00am

Back to 1/3 kernel, alarm clock works for me.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm... I experienced this, but only once. Not sure what causes it at the moment, but I have to assume the new battery code.
[Touch Pro2, Tilt 2 Android Development] besho2222:
Gr8, I just want the video performance (playback) to be perfect, and I'll NAND it ASAP, keep up good work guys :D
[Touch Pro2, Tilt 2 Android Development] bvone21:
I'm experiencing two bugs, but I can't seem to find comments from others having the same issues, is there not a "search this thread" option anymore? Having a tough time searching and I hate to double post...

Anyways...my issues are:

1) When I receive a call I cannot hear the caller on the other end. (When I "make" calls, everything is fine)

2) Most of the time I keep my phone on vibrate, I'm not getting any vibrates when receiving Texts. Incoming calls vibrate fine.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm not experiencing either of these issues.

Delete your data.img and try again - also, check your settings for vibrate, there's several.

However, audio routing for me is flawless. I assume you're on the newest March 11 kernel?

Some have said that flipping the speakerphone on/off fixes audio routing issues, but again I do not experience any audio routing issues with this kernel, and neither do any other 210 owners AFAIK.

Does this happen on the autobuild kernels...?
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Id like to second the vibrate issue, it vibrates for calls but never for txts even thoughvibrate is on in settings and is set to vibrate 'all the time' so even when not in silent mode it should vibrate for notifications but doesn't.

But note iv always had this problem with all the kernals and builds iv tried. Always presumed it was just an issue with our android builds which hadn't been ironed out yet? . . . .I txt a lot so its a little bit inconvieniant but its definatly not a serious problem :)

Also I'm using a 210 and I don't have audio routing issues with 'this kernal' AFAIK(don't use calls much) But iv had them alot before but as arrrghh said switching speakerfone on and off has always fixed it for me anyway.
[Touch Pro2, Tilt 2 Android Development] skimike02:
Using this kernel and FRX05, I sometimes can't hear the other caller on incoming calls. Rhod 210. Also, with this newest kernel, it seems to not wake more (with an orange light on). I have even had it happen in good coverage areas a few times. Other than that, working great.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Someone else reported that same audio routing issue, but above another 210 user refuted it.

I don't know, all I know is I don't have any audio routing problems. Need logs if I'm even going to think about asking WisTilt2 what the issue could be.
[Touch Pro2, Tilt 2 Android Development] bijan588:
This kernel is great

Pros-

- fast

-deep sleep blink

- cam

Cons

-sometimes won't deepsleep

- key can get stuck

- a little unstable
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What do you mean key can get stuck? If you mean that repeat key bug, I thought that existed on the autobuild kernels - does it not? That would be really interesting if it doesn't, because I always assumed that bug did exist on the autobuild kernels...

Sometimes won't deep sleep... Have you checked all the usual things that cause this issue? GPS, apps, etc.

As for a little unstable, more unstable than autobuild? Again, what do you mean by this? FC's, reboots to WinMo, SoD's...? Thanks!
[Touch Pro2, Tilt 2 Android Development] kastg1:
In addition to the vibrate settings in Settings>Sound, there are additional vibrate settings for text messages in the messaging app by hitting (when in the messaging app) menu>settings. Perhaps vibrate is not turned on there?
[Touch Pro2, Tilt 2 Android Development] bijan588:
Not the stuck key bug, its a bit diffrent. I ment sometimes fn gets stuck.

And the instability is not present when I use auto builds. I get a lot of sods from nowhere.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Lmao XD kudos to you my friend! Been awhile since iv felt lik a total noob XP never really looked through my sms settings cause I presumed it was enabled by default lik on most phones.

Sound out! Its working now and I'm presuming anyone else with sms vibration troubles have the same problem. Thanks again :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm... I guess stick to autobuild kernels then... I'm certainly not experiencing either of those issues.

Not even sure if logs will help - obviously on SoD it will, but if it's a true SoD you won't be able to pull logs.

No clue on the stuck FN key, you're definitely the first to my knowledge to report that bug...
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
I don't know if this is already reported, but I can't choose my ringtone anymore... :confused:

Settings > Sound > Phone ringtone

I can only pick "Silent". There are no other ringtones anymore. On the first boot I could set one, but now they're all gone? Although the ringtone I picked first still works...

(FRX05 with latest kernel from this thread)

Edit... Rebooting the phone solved the problem... Weird
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I typically recommend a format of the SD card using the HP Tool when people have this issue. This is a userland issue either way, not a kernel issue. Thanks.
[Touch Pro2, Tilt 2 Android Development] shatred:
that repeat key bug is still existing for me in these builds, also in the latest.

for example when i am typing an text message, sometimes randomly an letter gets "stuck" if i press the letter a (or any other letter) this will happen: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa (until i press the power button to let the phone sleep, then unlock it again and it stopped)

its not realy a big bug but i can be a little anoying somtimes..