yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I would stick to the autobuild. (Could be my hatred for mirroring services coming out here... :p)

I thought F22 was going to stop building the kernels and modules and just let this thread serve as a discussion point for the new kernels...

Personally I would love to see that happen. I don't see any reason to have a separate kernel and modules download link, when the autobuild bundles it in one link, and is updated automatically...
[Touch Pro2, Tilt 2 Android Development] sad0felix:
LOL, I'll vote this as most useful comment of the year!

What made you guess that I don't use Firefox?

If you thought you had superpowers or telepathy, I am sorry to say, you were wrong.

In fact, it was Firefox 4 Beta 11 failing with that page, and I then downloaded it successfully with Interdet Exploder 8.

Hell, you can't imagine how much I hate brainless partisans.

Yup, I already visited the Glemsom's repo, and already downloaded his Feb 20th build, but given different file naming rules I wanted to be sure they were exactly the same thing!

Cheers.
[Touch Pro2, Tilt 2 Android Development] R^7Z:
Oh will you quit your excessive whining :p He obviously has more time to spare and wants to actually feel helpful! :D

I say go for it F22, build those kernels to your hearts content! :rolleyes:
[Touch Pro2, Tilt 2 Android Development] perern:
A lot of work has been done here since i sold my TD2 and bought Desire HD
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
....Yes? There has been...?
[Touch Pro2, Tilt 2 Android Development] F22:
Camera Not Yet Working

As you've already surmised, only some of the code needed to get the camera to work has been committed. On the bright side, this is the first of several commits that will occur in the near future as the camera code is merged back into the main tree.
[Touch Pro2, Tilt 2 Android Development] F22:
Glemsom's modules file is named the same as mine since that's the name under which the init script expects to find it. So even though he names his packages something different, you can discover the commit off which his packages are based just by looking at the modules file in the package. If you already have his zImage installed, you can go into settings, click on About, and scroll down and read what it says under Kernel version. This will also give you the name of the kernel release in the same format I used, not the format that he uses. The kernel he posted today (Feb. 22nd) would be 1262.
[Touch Pro2, Tilt 2 Android Development] electricalve:
crap.same thing with the 1263, my rhod 500 (in gsm mode) keeps saying no service when it comes back from sleep, im gonna try changing the pm_sleem to 0 and 2 to see what happens if someone have any ideas how to fix this let me know
[Touch Pro2, Tilt 2 Android Development] yaq15:
I have found a solution

1. download the latest zImage from 22.2. - extract and copy to the folder "andboot"

2. Rename the file modules* new -> old

3. Add the line "msmsdcc_1bit msmsdcc_fmax msmsdcc_nopwrsave = 14 million" to startup.txt

Android now works!
[Touch Pro2, Tilt 2 Android Development] Eodun:
What do you mean with this line? So you don't use new libs? That way you won't have wifi...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I think he's giving instructions on how to properly replace kernel/modules.

Also, you'll only lose wifi. "lots of other things..."? I'm not aware of anything else that you'll lose other than wifi. What else breaks?
[Touch Pro2, Tilt 2 Android Development] Eodun:
All modules are only for wifi??? I'll edit my message. I thought there were other modules inside, sorry.

Edit: Oh, btw, I never needed to rename modules file, as kernel grabs the correct ones automatically. Just deleted them after new kernel works.
[Touch Pro2, Tilt 2 Android Development] g3rm0:
I think there's also bcm4329.ko for Bluetooth and lots of stuff for IP networking (but that's not important when you don't have wifi ;)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Indeed, but if you want to revert to an older kernel/modules, it helps to rename the end of them so they make sense to you... I do this sometimes when I find a kernel/module combo that works well for me, but I also test a lot of stuff - I put something on the end of the file so Android doesn't try to use it, and I can still identify it if I want to revert.

Ah, didn't realize there was anything BT related in there. Considering the state of BT this point is probably moot as well, but good to know. Learn something new every day ;).
[Touch Pro2, Tilt 2 Android Development] electricalve:
I've tried both pm sleep modes. still no working. any ideas?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You should always be on pm.sleep_mode=1.

Are you overclocking? I'm assuming if you go back to 1258 it's fine? Did you try a fresh data.img?
[Touch Pro2, Tilt 2 Android Development] electricalve:
the bug began with the 1258, im stuck on the 1253 from the frx04, and yes ive tried new data img and still the same, no oc. i think that is something related with the slepping policy because soon as the phone sleeps turns off the radio, and when it wakes says (no service)|Movistar, if i wait for 15 seconds the network is back on
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Maybe it's something related to you running a GSM network on a CDMA device...

Did you run any of WisTilt2's test kernels? I've been trying to get everyone to run them so we can shake out any bugs before commit, and this bug never came up in testing...

Throw his latest on your device, let me know how it goes. Still getting the issue, get me some logs!
[Touch Pro2, Tilt 2 Android Development] electricalve:
ok. how do i get the logs? sorry but I have no idea how to get it
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
First you might want to try the test kernel... Shouldn't post anymore about that in here.
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
Problems with time drift

I haven't seen this anywhere, but I can't believe it is only happening to me (but then again, what else is new)

In the morning, my clock time may be as much as 30 minutes off. During the day it will eventually catch up (over a 4-6 hour period.)

I know that Unix in general does not like immediate time changes and supports time changes in this way, but for a phone (that I often glance at for the time) it is not a good idea. Is there a fix or is this something I have to live with?
[Touch Pro2, Tilt 2 Android Development] rcgators:
Common problem. Look up Clock Sync in the market.
[Touch Pro2, Tilt 2 Android Development] DopeyOne:
I can also confirm the same issue on my Rhod_100... I have always had problems with voice calls (will get stuck on hanging up or just not receive incoming calls), but never really had the problem where it just drops service.

I tried the test kernals and didnt notice the issue.... I am running FRX04 and FroyoX with autobuild from glemsom... both installs have the same issue..
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The only thing different between 1253 and 1258 is the panel collapse code...

So every time you unlock your screen the radio is disabled?
[Touch Pro2, Tilt 2 Android Development] sad0felix:
The last really working kernel is 1253 for me.

With 1258 I could just unlock upon start, then wouldn't wake up properly anymore (black display, cane feel the unlock vibration, so it was working well, underneath).

With 1262 I went on the whole day with no problems, then this evening it started doing the same thing.

Rebooted 3 or 4 times, no clue.

Went back to 1253.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Fresh data.img?

Did you have any issues with WisTilt2's test kernels? 1258 has his panel collapse commits, while 60 and 62 are all cam-related stuff.
[Touch Pro2, Tilt 2 Android Development] F22:
Differences: 1253 vs. 1258

Not true. In commits 1256 & 1257, Alex's clocks were replaced with VirusCrazy's clocks in the merge.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
re: ClockSync - that's a pretty primitive fix, considering that the Android framework has a built in NTP client, and also retrieves atomic-clock time from the cellphone network. The issue is either the phone is not polling the network often enough, or something is preventing the phone from polling the time when it tries.

I've found that toggling Airplane Mode on and off will force the phone to reconnect to the network and update its clock.

I'd guess that something is happening with the phone going to sleep that prevents the usual NTP updates. Since regular Android phones don't have this problem, I'm also guessing there's a trigger that normally runs when the phone wakes up that automatically updates the clock, and it's not running for us.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oops. I thought that was in 1260 & 62... last time I'll fire off of the hip on commits, I lose track too quickly :p.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
Can't unzip the zImage on 1260 Kernel

Did anyone had the same situation? I was able to unzip the modules but not the zImage.

Any idea?

THX
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Please visit the autobuild, 1260 is already old :p.
[Touch Pro2, Tilt 2 Android Development] rcgators:
Didn't call it a fix. ;) Until the clock issue makes it up the priority list ClockSync is what we have.

For those who don't want to be late for a hot date ... it's a good

workaround

. :D
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
I see, thank you
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
So what is what in there? I dont have a clue as to what is the latest?

Sorry! I'm a noobie to all this.

THX for all your help
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The lastest kernel is the one at the top. So if you want the latest, grab the one at the top...
[Touch Pro2, Tilt 2 Android Development] sb283:
changelog

I wonder if there is a way to know what has been changed in each particular build. Maybe I am dumb, but I could not find that on the auto-build website.
[Touch Pro2, Tilt 2 Android Development] F22:
http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm

This listing is useful because it shows you the commits in order of submission, and not in the order the patches were written. If there is more than one commit combined into a single submission to the tree, click on the word commits to see their descriptions.
[Touch Pro2, Tilt 2 Android Development] AkumaX:
http://glemsom.users.anapnea.net/android2/htc-msm-linux/

if you hover your mouse over each of the Build ID rows, a hover window pops up showing the latest commits :D
[Touch Pro2, Tilt 2 Android Development] sb283:
LOL. Thank you :)
[Touch Pro2, Tilt 2 Android Development] ivwonka:
running newest kernel 1262 from 2/22 for a few hours now on froyoX red 2/6. love it. it sleeps like a baby. love seeing that green led! seems fast and stable. no quadrant scores or battery data, but I didn't see much of that info posted here anyways. thank you to all devs and testers involved.
[Touch Pro2, Tilt 2 Android Development] yaq15:
the new "modules-2.6.27.46-01262-g4a804e5.tar.gz" rename to the old "modules-2.6.27.46-01253-gd53ddf6.tar.gz" name
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Never change the name of the modules, leave it alone.

Only change zImage....... to zImage
[Touch Pro2, Tilt 2 Android Development] sad0felix:
No fresh data.img yet, because it's my primary (I mean only :D) phone.

Which I work with.

To say it all, the data.img is there since early november ...

When I have some really spare time I will back it up and try again after wiping the old one.

BTW, WisTilt2's test kernel I tried was based on 1258, and gave me the very same results about forever dead display.

Pretty unusable, I would say, as both present the symptoms immediately after boot with no practical way of recovery (once or twice, after hundreds or attempts, it did miracolously wake the fsck up).

Sorry for being not too much of help.

EDIT:

BTW 2, during the 8-10 hours I had 1262 on it with non problems, the battery was drained just 40% (60% remaining, little bit more than 4k mV)), quite an achievement.
[Touch Pro2, Tilt 2 Android Development] CrazyCoder:
FYI: Android is using built-in NTP client only to get faster fix when working with GPS, it doesn't use it to adjust system time. NITZ (cellphone network time) is supported by a limited number of providers and sometimes sends incorrect results. There are countries with millions of users without NITZ coverage.
[Touch Pro2, Tilt 2 Android Development] Eodun:
Hm, from my ignorance... Then why I get correct time within WM and not in Android?
[Touch Pro2, Tilt 2 Android Development] rcgators:
As highlandsun pointed out...

So picking up the cell network time works at connection time, it's just not updating after the initial connection to the network. But more important, the clock is not keeping accurate time.

All known issues that will hopefully be addressed once the developers fix what the feel are more pressing issues.
[Touch Pro2, Tilt 2 Android Development] CrazyCoder:
Because with your current Android kernel time drift is so heavy that can't be corrected in a timely manner via NITZ. I had similar issue with some tweaked and custom kernels on my Google Nexus One, that's why I created ClockSync. The drift with the official Nexus kernel is much lower and can be corrected via NITZ (which doesn't work in Russia, therefore I still need ClockSync).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oo didn't realize you were the creator of ColckSync. Thanks for the great software!
[Touch Pro2, Tilt 2 Android Development] R^7Z:
+1

Very nice indeed! :)

Thread link
[Touch Pro2, Tilt 2 Android Development] Eodun:
Thanks to both, and another thanks to crazycoder: Clocksync is great! I've got it configured to sync with a spanish npt server, I love that I can do that.
[Touch Pro2, Tilt 2 Android Development] DopeyOne:
It isnt every time it sleeps, but it seems to be more consistent after long sleeps (ie 40mins+).

I will try 4a804e5 with a fresh data.img

PS. You guys are amazing, this project seems to be flying along :) Thank you!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Interesting, especially since it ought to be able to read the GPS clock already as well.

Hm, I remember when I was on AT&T Wireless many years ago, that they weren't broadcasting network time. Pathetic. I vaguely recall that when I was in Kazakhstan in 2008 that my G1 picked up network time just fine. I guess it's pretty unpredictable whether it will be available or not.
[Touch Pro2, Tilt 2 Android Development] AkumaX:
O SNAP do my eyes deceive me? does the latest official kernel @ http://glemsom.users.anapnea.net/android2/htc-msm-linux/ include the CAMERA commit?!

:D

omfg it worrrrrrrrrrrrrrrks!!!!!!!
[Touch Pro2, Tilt 2 Android Development] jphaus:
Just downloaded it and booted two different times to test camera. It's not working for me. :( Once trying camera, orange light stays on forever and phone does not go to sleep.
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Same here. There appears to be an issue with sleeping correctly and camera does not work. Dang, got my hopes up man
[Touch Pro2, Tilt 2 Android Development] F22:
I haven't tried it yet myself, but it's my understanding that the latest kernel contains all the kernel mods needed to work with the camera. (bzo submitted 14 commits today, most of them on VirusCrazy's behalf!) Nevertheless the corresponding userland libraries are not yet in XDAndroid. So as of this moment, you still have to follow the instructions in VC's thread for everything except the kernel.
[Touch Pro2, Tilt 2 Android Development] manekineko:
I'm seeing the same thing. FRX04, tried both Camera and Vignette from the Market, both just hang trying to start the camera.

Edit: Replied at the same time as F22, didn't realize that userland libraries were not present. So it's no surprise mine didn't work.
[Touch Pro2, Tilt 2 Android Development] AkumaX:
Right now I'm on tiad8's FroyoX 2.2.1 Blazin. In his TitaniumBackup file, there was FXCamera, so I installed that and that's how it's working right now - I guess that means I could assume that tiad8 put in the userland stuff.
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
Can you point us towards VC's thread please (I did some googling, but did not immediately find it.)

thanks :-)
[Touch Pro2, Tilt 2 Android Development] nickleby:
Camera works fine with the latest kernel and Froyo X RED :D

But when you're going to take the picture, the image is too dark! Even when there's a bright light :confused:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Here you go
[Touch Pro2, Tilt 2 Android Development] billerbong:
Thanks a million all of you developers. I was able to use the Kernel from glemsom website and the mods for the camera working. Also great job on the sleep issue as well. My Rhod500 cdma would fall into a deep sleep after about 8 to 10 hours and now I have had my phone running for about 48 hours before the camera mods that I just put in a few minutes ago. Sometimes the screen comes up blank but if I hit the screen every thing shows. AWESOME job and thank you a ton for all your hard work.
[Touch Pro2, Tilt 2 Android Development] billerbong:
Hey I did find that when I am in a call or voicemail sometimes not to often the speaker phone will be active but the speaker phone is not to loud. The speaker seems to be on real low. Let me know if there is something I can do to help.
[Touch Pro2, Tilt 2 Android Development] rcgators:
If it happens after you press a key, then it's a known issue. Just disable keytones and it will bypass the issue. Keytone turns on the back speaker but does not return sound to the earpiece after the tone.
[Touch Pro2, Tilt 2 Android Development] randomblame:
Now we need an frx04 update to include some camera support
[Touch Pro2, Tilt 2 Android Development] AkumaX:
shouldn't everyone just move on to FRX05?
[Touch Pro2, Tilt 2 Android Development] Eodun:
?

There's a FRX05 with cam update.
[Touch Pro2, Tilt 2 Android Development] rcgators:
The following combination work well....

ext2: http://files.xdandroid.com/system-FRX05.ext2.zip

Kernel from testing thread: [TESTING] Updated 3/1/11 New Kernel ...
[Touch Pro2, Tilt 2 Android Development] AkumaX:
I'm using:

- the FRX04 Reference Zip

--- updated w/ FRX05 system.ext2

- kernel from arrgh's 3/1/11 testing thread

- rootfs from F22's 3/1/11 testing thread

and it's been a DREAM working with it!! most stable build ever, haven't restarted in days!
[Touch Pro2, Tilt 2 Android Development] sad0felix:
EDIT:

Ok, I apologize. It seems that I was just too unpatient to wait the 5/10+ secs necessary for the display to wake up correctly.

Sorry everyone for the inconvenience and noobiness.

I leave the message below so you know what I am talking about.

I keep having the same troubles: any kernel newer than 1253, after booting correctly, after going to sleep correctly, will cause my display to not wake up anymore: I can feel that it unlocks correctly, I can reply phone calls and such, but it stays just black.

When I say any, I mean: 1258, 1262, 1276 (FRX05 stock), 1258 based Wistilt2

This happens always. No exceptions.

I tried also renaming data file, to make it build up a new one.
The only result I got was complete freeze before I could even set things up.
Everytime.
Same both cards. FRX05.

I tried searching around, I saw that someone else is having the stoned-display issue, but it appears to be random and not that common to them.

Does anyone have any hint on this?

Rootfs - latest (Feb 24th)
cmdline:
lcd.density=240 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 force_cdma=0 pm.sleep_mode=1 physkeyboard=rhod100_it

Bye
[Touch Pro2, Tilt 2 Android Development] majkeljj:
I have also problem with new kernels starting from 1233 to 1276 when I use it on fresh install. My screen freezes after about 2-3 minutes after boot. no matter what I do and no matter which android I use FRX, FRG, etc. This happer every restart. To overround this I make fresh install with kernel from 24.11.2010 and then go to the newest in the next boot. Then everything works fine. Any solutions?

RAPH100
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
I have the same problem with all new kernels. If I touch the home or power key or wait until standby, the display is dark and the phone is dead. (rhod100_de)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What sleep_mode are you using? Build? What is the exact kernel this stopped working on?
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
pm.sleep_mode=1

f.i. Kernel: 2.6.27.46-01276-g6a6a1c1-dirty

not sure, when it stopped working

(I will try sleep modes 2 and 0.)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm. I need you to do some legwork and go thru each kernel, one-by-one backwards from 1276 and tell us when it stopped working.

Otherwise we have no clue what broke it. Earlier reports could've prevented this as well - if you have a new problem with a new kernel, we need to know immediately. Otherwise we have to get someone who is experiencing the issue to go thru and figure out what, specifically, breaks your device.

Also, you didn't mention what build you're on? Have you tried different builds and have any different experiences using the same kernel?
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
FRX5, sleepmode=2 is the same.

(The phone is not dead, if i press power, the led is changing from orange to green. The phone is ringing, I can answer, just the display is black.)

I will try all kernels an report.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks, this will allow us to narrow down which commit broke the panel waking.

Odd that everything else works. Just curious, does the backlight come on and the panel stay off, or does nothing change except the LED?
[Touch Pro2, Tilt 2 Android Development] snalbansed:
I have exactly the same issue and solution on my rhod100_uk with AUO panel.
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
I have installed FRX5 with 2.6.27.46-01276-g6a6a1c1 (included) and then changed to:

2.6.27.46-01253-gd53ddf6

No Problem with the panel backlight. This is the last known good kernel for my phone.

2.6.27.46-01258-gf9e4956

The first kernel with a black screen after standby.

I have a dark screen, can not see any thing, but the green led after 5 seconds.

(I have tried to power on a few times and the the screen was on only one time.)

2.6.27.46-01260-g11945d1

Not possible to download the modules from mediafire.

(My rootfs is from here: http://xdaforums.com/showthread.php?t=935710 )
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Please get kernels from the autobuild service...

Although there's probably a gap where you have to download from F22's thread. Bleh.

1258 was the first commit from WisTilt2 on the panel collapse stuff.

Have you tried his latest test kernel?
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
Not so easy for me to find all the kernels.

Do you mean http://glemsom.users.anapnea.net/android2/htc-msm-linux/ ? Or with the startup utility?

htc-msm-linux-20110228_193144-package.tar is not booting.

Startup utility is downloading a kernel from Jan. 23.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Don't use the startup utility, that's just for updating to the most recent kernel - it doesn't let you choose which kernel to download (although it would make this testing infinitely easier :p).

There's a gap between kernels 1231 and 1253 on that site you listed above, which is the autobuild service.

If you want to test any kernels between 1231 and 1253, you'll have to reference F22's thread. Any other kernel should be available on the autobuild server.
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
I have tested now:

2.6.27.46-01253-gd53ddf6 1580 kb (good)

from http://xdaforums.com/showpost.php?p=9757042&postcount=1

2.6.27.46-01253-gd53ddf6 1614 kb (good, but problem with b4home-Key)

htc-msm-linux-20110210_213850-package

---

1258 (bad)

1260 (bad)

1262 (bad)

1276 (bad)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ok, so that was the panel collapse kernel IIRC (1258).

Have you tried WisTilt2's newest kernel in my kernel testing thread?