yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] F22:
Kernel 1255 Fails To Compile/ 1253 Still The Latest

This morning's commits to the kernel tree introduced a pair of bugs into the kernel, one of which prevents the new kernel from compiling. This is why Glemsom's new kernel is just a broken link. It tried to put up a kernel it failed to build. It's just as well, the second bug causes the kernel to panic and reboot back into windows.
[Touch Pro2, Tilt 2 Android Development] F22:
you're most welcome. :)
[Touch Pro2, Tilt 2 Android Development] F22:
New Kernel (1258) - Feb. 14, 2011

Piping hot new kernel! Fixes the bugs in the early morning release. Also has WisTilt2's rhodium panel collapse and panel detect code plus VirusCrazy's amss clock implementation as well. See the first post for the download link and info.
[Touch Pro2, Tilt 2 Android Development] helicopter88:
Amss clock?

What's it?
[Touch Pro2, Tilt 2 Android Development] F22:
AMSS is basically firmware. Each HTC device supported by the kernel has a different amss version. Different hardware components run at different clock rates or speeds. Some components run at speeds that are multiples or divisors of other components.
[Touch Pro2, Tilt 2 Android Development] electriczbif:
Rhod100_uk, 1258 kernel, rest of the files from FRX04 from 01/21, testing for 2 hours:

1. Pressing volume up/down wakes up the phone for 1 second (led turns orange, screen black, blacklight off).

2. 1 out of 3...10 sleeps, the screen takes more than 10 seconds to wake up. The backlight is on, but the screen is black for 15-30 seconds. Tapping the screen has no effect. If I press volume up/down for 15-30 seconds, the screen finally comes up. If I don't press volume, the phone sleeps back after 10 seconds.

3. When the phone wakes up on ring, the screen brightness isn't restored to the value in settings but to a much lower one (about 20-30%).

4. I have called the phone 20-30 times, it wakes up ok on ring, no problems encountered yet (on wistilt's test kernel the phone was losing GSM network on a ring that doesn't wake up the screen).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
In reference to #3, are you doing autobl?
[Touch Pro2, Tilt 2 Android Development] electriczbif:
No autobl, brightness set to 100%.
[Touch Pro2, Tilt 2 Android Development] electricalve:
i dont know why this kernel (1258) isnt working on my rhod500, im using it on gsm network, but soon as the phone enter on sleep mode the antena turns off too, it says on the screen "Movistar no service" when the phone is on again it turn on the antenna again by itself, LOL please check out that bug..

im using stock frx04, im also formated the sd, to test the new kernel with the frx04 files and nothing same bug

pm sleep set to 1

no OC

2.35WV Verizon Radio
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That's probably the issue, I don't think manual brightness works correctly with autobl incorporated.

Never happens on my RHOD400, CDMA. Have you tried using the 500 as a CDMA device, does it do the same thing? I don't think "native" GSM devices do this (RHOD100, 300, etc).
[Touch Pro2, Tilt 2 Android Development] killerkhatiby009:
So anyone been trying this kernel out with tiad's froyo x?? Is it working well?
[Touch Pro2, Tilt 2 Android Development] JBS2:
------------
[Touch Pro2, Tilt 2 Android Development] AkumaX:
i had problems with it. but, i might try it w/ a new install
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
Camera?

I just installed the Feb 14 version, hoping to see the camera working... Its better (when I rotate the phone, the cameras rotate with it) but I get a message saying I need to install an SD card before using it. Am I missing something?

<just saw the comment at the top of this thread - I am editing my startup now and will get back...>

OK - that was a bust. I don't get the message any longer, but the camera screen is still black and the buttons don't work. If I click a soft button, the application crashes :-(

thanks...
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Camera working with 1258? It doesn't, hasn't been committed yet
[Touch Pro2, Tilt 2 Android Development] großa:
Almost the same thing here, but i can't get it out of sleep when I press buttons. Only with a call I'm able to get it out of sleep. Didn't test autobacklight, but you are right. The phone brightness isn't restored.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
WisTilt2 is going to whip up a RHOD100 AUO panel only test kernel tonight. I'll post it in the usual testing thread.
[Touch Pro2, Tilt 2 Android Development] killerkhatiby009:
alright i've been using the new 1258 kernel with froyo x and i've noticed that many times when i wake up from sleep the screen turns on but nothing shows up, similar to what people have mentioned. Sometimes if a wait a few seconds the actual screen will show and other times it will just go back to sleep. What I do notice though is that to get around this I just have to press the screen after turning it on in the location where the usual android unlock button would be and the screen always comes up. It works but it would be nice if wake up worked every time as well, I seemed to have less wakeup issues with the 1253 kernel.

Also as others have noted the volume button does cause the green light to change to red/orange quickly and then back.

lastly, I had plugged my device running android into the charger over night and the led always stays orange (is this normal?) but when I woke up and tried to turn on my phone it had gone into an SOD and my phone was extremely hot. I used to be able to leave it all night plugged in on 1253 just fine, ill try it again tonight and see.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What phone? Your sig and avatar are probably outdated...

RHOD100? AUO panel as well? While my phone also goes to orange when I hit the volume buttons, I don't have any screen wake issues (well, 99.9% of the time I don't).

Also good to note, there are a lot - if not all - reported SoD's occurring when charging. We've definitely narrowed it down to that, and the battery code needs some serious reworking so hopefully they stumble onto a fix while doing that.

FYI, it's perfectly normal for the LED to be orange when charging - the phone is always "awake" when charging, it can never sleep while charging.
[Touch Pro2, Tilt 2 Android Development] husam666:
No SODs so far, but yesterday I had a couple of freezes, both after turning off flight mode.
[Touch Pro2, Tilt 2 Android Development] sb283:
I am also experiencing exactly this same wake up issue on rhod400 (Sprint)
[Touch Pro2, Tilt 2 Android Development] electriczbif:
Rhod100_uk, 1258 kernel on FRX04 from 01/21:

I'm still having issues answering the calls, as with FRX04 and FRX03. 20-30% when I answer a call, I can't hear anything and mic doesn't work, until I switch speakerphone on and off. After that, everything is ok. I have tried to install on a fresh formated SD card, with or without data activated, with 01/21, 02/05 or 02/10 rootfs but there is no difference regarding this issue. To get around this, I've used Tasker to switch speaker automatically on and off when I answer the calls and works somewhat ok, but still takes about 2-3 seconds to answer a call that way.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
(deleted...)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
If you touch the screen, does it wake? I guess I'm confused as to which wake issue, as you quoted me talking about how I don't have wake issues on my RHOD400....

I know this bug has been squashed... I don't get why the 100's would still experience it, unless the patch only applied to 210, 300, 400 and 500... Doubtful.
[Touch Pro2, Tilt 2 Android Development] killerkhatiby009:
yea my sig is way outdated lol, Its a sprint TP2 so rhod400 i think? And alright then ill stick to charging in windows mobile in that case until that gets fix. Thanks alot for the help.

And as for the wake up, it wakes up every single time (as opposed to before where it would need a couple of presses sometimes), I just seem to need to press on the blank screen where the unlock button would be for it to actually display something.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
1258 zimage download is bad downloaded it twice 2 different sd cards and sd formater every time failed to load file zimage
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hey, responded to you in the "FroyoX" thread...
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
no off the f22 thread here. I will try the other
[Touch Pro2, Tilt 2 Android Development] jmstumme:
I have had the same issues waking on a rhod500, alarm goes off in the morning and panel doesnt wake, i hit the power button and then the buzzer just goes solid for 10 seconds and then goes back to normal operation but panel is still off, took 2 min this morning to turn my alarm off :-\ also when it does come on there is the dot to drag to to unlock still on the screen
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Gotta ask, what sleep_mode are you configured for?
[Touch Pro2, Tilt 2 Android Development] jmstumme:
Mode is 1
[Touch Pro2, Tilt 2 Android Development] bluenote73:
I think this probably still contains bug 80? The Diam500 cDMA screen alignment bug? Can anyone comment?
[Touch Pro2, Tilt 2 Android Development] F22:
Diam 500 CDMA Screen Alignment Bug

It's possible that it doesn't since the code suspected of being responsible for that bug has been temporarily removed. Somebody with that handset should check.
[Touch Pro2, Tilt 2 Android Development] sb283:
Yes, it does. I did not know that before I read one of the previous posts. Good to know.
[Touch Pro2, Tilt 2 Android Development] xtremetactics:
First load of the 1258 Kernel was running great using FRX04 reference, rebooted to play with the gingerbread build and since then I have had 2 SoD's while phone was sleeping (green light) reverted back to wistilt 2/9 kernel and phone is running good. I am not positive which logs are from before it so I am adding the last three I have. Hope it helps. I have Rhod400
[Touch Pro2, Tilt 2 Android Development] bluenote73:
[talking about the screen alignment issue on CDMA diam500 and other devices]

(bug 80)

I'll put it on my todo list to check this out. I just got back from having surgery though so it probably won't happen immediately. If anyone else with a CDMA device runs into this please comment here!
[Touch Pro2, Tilt 2 Android Development] majkeljj:
My raph100 with fresh install Huawei U8150 ROM and 12658 kernel have wake up problem every time when I send it to sleep.
[Touch Pro2, Tilt 2 Android Development] muziling:
when charge with USB, screen almost can not be wake up, but system works, can listen sound when I hint volume up/down.

my device: touch pro2 rhod400

my kernel: 1258

my rom: Froyo B V4
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Great, I'll be waiting eagerly!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm about to leave for work, but I do have the kernel. I'll post it in my testing thread soon...

F22 - just wanted to say about the calibration issue. I've had other RAPHs report issues with it. Still haven't heard back from any CDMA RAPH/DIAMs on the screen alignment issue...

Reading the dev list and seeing you say 'temporary' make me think that those clocks that seemingly broke a lot of things and improved nothing are going to be recommitted... Kinda makes me scratch my head, but I do understand getting this setup properly for a good base. However, I also understand that sometimes theory and reality don't always see eye-to-eye...
[Touch Pro2, Tilt 2 Android Development] F22:
I went back through the old kernels and confirmed that the .35 fb commit was responsible for the ts calibration issue, not the clock commit. We just didn't notice until the clock commit because nobody had posted a complaint until then. 1258 does fix it for Rhod, but not for Raph. I'm not surprised that it doesn't fix it for Diam. Top, Black & Kov are question marks.

Yup.
[Touch Pro2, Tilt 2 Android Development] R^7Z:
Was that (.35 fb commit) prior to or after the 12-4 kernel package from glemsoms autobuild site?

More specifically: htc-msm-linux @ 20101204_005141

I can produce a ts-calib file with that kernel package with my Fuze (RAPH110). I have not tried it with the latest (1258/htc-msm-linux @ 20110214_200559), should I and report? Is there anything I can produce that will help narrow this issue?
[Touch Pro2, Tilt 2 Android Development] F22:
After. 20101204_005141 is the first of two kernels Glemsom built on 12/4/2010. Glemsom's second 12/4 kernel, his last before he went on hiatus, is 1231. The .35 fb commit was 1233.

Not at this point I think. We know it's commit 1233 that broke touch screen calibration for all the handsets. What we don't yet know is why it suddenly started working for rhod but not raph in 1258. Nobody tried to fix it. The fact that it's now working again for rhod is purely a beneficial side-effect of one of the other changes that have been made.
[Touch Pro2, Tilt 2 Android Development] sad0felix:
About the screen remaining black.

On a rhod100 (ita), FRX04.

I had kernel 01253

I had latest (AFAIK) F22 rootfs, 20110202-d8f73aa

I replaced the kernel with 01258

I replaced the rootfs with latest official (from xdandroid.com) 20110210-2cb7ec0

Xdandroid starts but no screen.

Touch works, can "feel" the screen unlocking, can talk if called, but no way to wake up the display.

Before reverting to previous kernel, I tried reverting rootfs to stock FRX04 (20110123-5cafe3f, I am not sure, I left it renamed in the andboot folder), and now I have display.

So I guess the rootfs might be as guilty as the kernel.

Cheers.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Howdy.

Not to steal this thread's thunder (it is the thread to discuss issues with the newest GIT kernels) but WisTilt2 has a potential fix I'd like you to try...

WisTilt2's commits on the panel collapse is probably the reason your panel is not waking. Can you do me a favor and try the latest test kernel? Thread is here. Please post any responses related to that kernel in that testing thread. Assuming it does work for you great! Keep it for the time being, if it does go well hopefully the code can get committed soon. Thanks again!
[Touch Pro2, Tilt 2 Android Development] sad0felix:
I guess you mean with latest rootfs, right?

Thanks for the hint, I'll try ASAP, this evening, when I'll be back home.

Now the phone needs to be up and running ... :P

Cheers

UPDATE:

No, it's definitely not the rootfs ...

Same problem again, I have to test that now :D

UPDATE 2

Pretty the same result with wistilt2 kernel: phone responsive but black.
[Touch Pro2, Tilt 2 Android Development] bluenote73:
I installed 1258 on my cdma diam500 and so far, (fingers crossed) I haven't been able to re-create the screen alignment issue where the sides of the screen migrate slowly across the physical screen. I'll continue to try and re-create and post back if I manage to do so.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Rhod110

FN LED not working (key works beautifully)

before 1258 i was using 1255

with 1258 im getting this 'freezing' issue randomly sometimes after i unlock the phone via pattern (havnt tried anything else). also getting the freezing in sleep issue, not sure if i can get a connection, i will try and reproduce at home.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
Rhodium 400 FRx04

Seems to run smoother than 1253 no issues after 1 day of operation. HQ runs on utube did not on 1253 and skyfire resolution seems better. Still have to make phone call or run maps on initial startup to reset server but once that is done it operates fine. Not as fast as the newer builds but definatly a lot more stable. Also usb headset seems to switch better and more stable. Microphone still does not work with headset in phone call.

On red build posted results there using this kernel.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Are you playing HQ YouTube thru skyfire...? HQ still doesn't work for me, in the YouTube app or in the Browser...
[Touch Pro2, Tilt 2 Android Development] Qmaster11:
Camera

In froyo x is a kernel with camera!
[Touch Pro2, Tilt 2 Android Development] meenjedatnou:
Same here on Diamond2 T5353 ... Deep sleeps to which I cannot get the phone to wake up unless resetting. I am now back at 1253.

Where can I find the cmaera kernel ?
[Touch Pro2, Tilt 2 Android Development] rcgators:
Try the camera testing thread. New updates posted today.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
No through utube and moviephone
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Is "utube" an app? I have the "YouTube" app...
[Touch Pro2, Tilt 2 Android Development] AkumaX:
think this will fit on a 512mb card?
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Including all the android files and ext2 file (or extension2 partition)? . . . No I don't tink so. But feel free to correct me if I'm wrong :)

Edit: well I checkd my sd and all the files are relativly small, but you wouldn't want to have too much else on the card. Also using etx2 partiction(or ext2 file but I can't recall the default size of that rit now ) you wouldn't be able to install loads of apps.
[Touch Pro2, Tilt 2 Android Development] R^7Z:
Off topic post

Wrong place to discuss this but I have a 512MB microSD and it fits just fine.
[Touch Pro2, Tilt 2 Android Development] AkumaX:
cool :) i'm only asking cuz i found out my 512mb card is ridiculously fast (20mb/read, 15mb/write)
[Touch Pro2, Tilt 2 Android Development] R^7Z:
Keep in mind, it's going to be a slim to no chance for anything else being installed to it. It's best to have at the least a 2 or 4GB class 4 or higher microSD, not required but it would make things a little more enjoyable! :)
[Touch Pro2, Tilt 2 Android Development] AkumaX:
Here's some interesting results for you guys ;) obviously, all cards vary, but these are the ones i get to deal with (values are rounded)

512mb generic = 20mb/read, 15mb/write
1gb sandisk = 11mb/read, 5mb/write
2gb generic = 14mb/read, 9mb/write
2gb kingston = 19mb/read, 6mb/write
4gb kingston C4 = 17mb/read, 5mb/write
8gb adata C4 = 19mb/read, 11mb/write
16gb patriot C4 = 15mb/read, 9mb/write
32gb sandisk C2 = 14mb/read, 6mb/write
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
Yes it is YouTube thanks for making me type more letters.
[Touch Pro2, Tilt 2 Android Development] husam666:
can you at least be nice to people who are getting android to run on ur phone
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
I got a SoD today so here's my kmsg log.

Just to be sure, i'm using the gingerbread test build.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
I had the same SOD issue for the first time after going to 1258 also arrrghhh. Overall that build runs a lot smoother with less "system server bug" issues, but this is the first time I have ever gotten a SOD in any build I can remember. Also for some reason when turning on my GPS to use an app like foursquare or maps or anything else, I will then go to turn it off to get the phone to be able to go back to sleep mode which always worked on past builds. Now sometimes it will not sleep despite turning GPS back off. The GeoLocation is already off and I never touch that, but definitely something has changed between 1253 and 1258 that made this happen I would have to believe.

Oh yeah I am running a Sprint Rhod400
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
Cell Service

So usually im at school and this weekend i went home.

At school i have very low reception and i usually loose it from goin in and out of rooms.I couldn't handle 1258 because it would constantly freeze up and not wake. I didnt understand how other's were saying how well it worked.

At home i have pretty good constant cell reception and omg! this new kernel has been amazing for me. I do get 5-10sec wakeups but otherwise its been great. No Sod or any error's.

So far i can diffidently say that my SOD's are coming from reception loss.

now to get better reception at school! or have this fixed =)
[Touch Pro2, Tilt 2 Android Development] Jandyman:
I used have the same problem cause I go to school in an old school with 2 foot thick walls . . .but have you tried wistilt2's latest?(don't tink commits are in git yet) its on the thread arrghh linked and also in my sig, iv had almost every wake work within 2secs and no SODs caused by the kernal.
[Touch Pro2, Tilt 2 Android Development] bluenote73:
Just wanted to confirm, I've been running 1258 on my DIAM500 and I haven't seen hide nor hair of the screen-edge-migration issue where the borders of the screen slowly migrate horizontally.

I also discovered something about the "screen doesn't turn on on unlock" issue. I could "feel" it unlocking via the vibrate, but the screen didn't turn on. I unlocked and was able to navigate to a brightness shortcut that I have on one of my homescreens, and a tap or two? to that DID turn on my screen.

Hope that might help somebody, I dunno maybe its obvious that changing the brightness inits something.

While I'm here, can somebody explain how to update to FRX04? I've done a moderate amount of searching and I can't seem to find instructions. I think its just the system2.img file? so can I just drop in a new one and replace the old one?

thanks
[Touch Pro2, Tilt 2 Android Development] R^7Z:
The easy way is to just replace the system.ext2 ( plug n play! :eek: )

Supposedly the update method "works" but I have yet to see it work on my Fuze. Seems I get some issues but experience none of the others, go figure :D So, I couldn't suggest something I don't use... :)
[Touch Pro2, Tilt 2 Android Development] randomblame:
just installed 1260 on my good old rhod 300- I was hoping it included all the camera code but aparently it doesn't because camera is not working. Sad cheese - back to playing with my inspire :D
[Touch Pro2, Tilt 2 Android Development] R^7Z:
If I'm not mistaken, I believe camera is still in testing, unfortunately :enter sad face of choice here:
[Touch Pro2, Tilt 2 Android Development] yaq15:
i have the "unabel to mount sd card" Problem on a rodh100_de with a 2 GB SanDisk SD Card.

the line "msmsdcc_1bit msmsdcc_fmax=14000000" hase not work.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Format your sdcard again, with HP format tool. Don't forget to do a long FAT32 format.
[Touch Pro2, Tilt 2 Android Development] meenjedatnou:
Tested on Topaz T5353 Diamond2, but unfortunately call-dropping is still a kernel bug. Furtermore I am using it together with a Gingerbread system.ext2 which in my opinion has pretty nice battery time..
[Touch Pro2, Tilt 2 Android Development] yaq15:
From Christiaan91: Format your sdcard again, with HP format tool. Don't forget to do a long FAT32 format.

many thanks, but it did not work - same error "unable to mount ..."
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I have a feeling the "SD card bug" is back... Looks like you already tried the fix on the first post, sorry about that..

Silly question, but are you putting those two lines in the right section of the startup.txt? That trick always used to fix people that had issues with this clocks-related bug.

I bet CDMA RAPH/DIAM's have the drifting screen bug back...

I would honestly recommend anyone experiencing these above issues, stick to 1258 for the time being.
[Touch Pro2, Tilt 2 Android Development] sad0felix:
I am the only unlucky one that can't download 01260 modules?

I can successfully download the zImage only.

Mediafire page just reloads upon download link clicking.
[Touch Pro2, Tilt 2 Android Development] R^7Z:
Can you download from Glemsoms autobuild? Or are you just sticking with one kernel provider :D ;) :p
[Touch Pro2, Tilt 2 Android Development] djcrosstunez:
Try to download with firefox;) works for me!