yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] Jandyman:
I second that, for me it types almost 200 of the letter most times so it is fierce annoying. Also get random keyboard freezes where the keyboard becomes unresponnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnsive until the backlight turns off, then it works again . . . . .but as you can see button stick is more of an issue :/ (btw I decided not to edit this time to give an exact example)

But afaik wistilt2 isn't planning on fixing this as he is currently editing RIL, to improve what this kernal is testing: panel init/deinit without any adverse effects.

Also these keyboard errors seem to coincide with keyboard backlight commit, so I'm presuming that's where the bad code which causes it cmes from. Don't know what kernal dev is working on this though, maybe it should be reported to whoever pushed the keyboard backlight commit?

But I as much as anyone hope that someone will work on a fix :)
[Touch Pro2, Tilt 2 Android Development] dswaggz:
Wasn't it f22
[Touch Pro2, Tilt 2 Android Development] jphaus:
Oh wow, and here I thought it was just me. I have had this problem for quite some time now and was just assuming that it was my physical keyboard going bad rather than an Android bug. In fact, I was thinking about trying to get warranty work done (SquareTrade), so you just saved me a big embarassment and some time away from my phone. And here I thought I was pretty smart working with Android on my TP2. Thanks for pointing out, I hadn't seen this mentioned before, but I hadn't searched either. :o
[Touch Pro2, Tilt 2 Android Development] afrizal_chen:
My RHOD100 has been running 4 days without a single SOD.

I turned 3G off on WM (thus running GPRS), execute Haret.exe, after doing this, there's no way I can get 3G on XDAndroid. So with only GPRS for data, I have no SoD, even on places where i have no reception.

I more thing, yesterday I took the RHOD out at 8am, it last until 11pm wihtout a single charge, (usage: made some calls, did a lot of watsapp and messaging, google readers).

Good works!

RHOD100 - FRX05 - WisTils 3/11/11 Kernell - F22 1 March Roofs
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yup, that's the theory - switching between 2g/3g is causing the SoD issue. WisTilt2 is working hard on the new RIL, problem is the CDMA code is very scant and needs some serious fleshing out. Hopefully soon we'll have something public to test!
[Touch Pro2, Tilt 2 Android Development] toadlife:
There is no 3g within 30 miles of where I live and I get the occasional sod, so I'm not so sure about it being a 2g/3g transition issue. That said many of my sod have happened in an area where my phone freqently switches between gprs and edge.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I guess I don't get how GPRS and EDGE are different from 2g/3g - either way the radio is switching modes and it fails.

Of course, there is no GPRS or EDGE on CDMA, from my perspective all we have are 1xRTT and EVDO.
[Touch Pro2, Tilt 2 Android Development] khabibul35:
My Rhod 400 Review:

Pros:

1) SoD was pretty much non-issue. It always came came eventually. Although, quite frequently I would power on, get the wake LED but a black screen. Once I hit power again it would sleep, and then once I hit power the third time it would wake with the screen.

2) Very snappy. By far the fastest response I've gotten from any ROM/kernel combo

3) Camera works very well, but sometimes froze after the first picture if I pushed back to take a second pic.

4) Backlight worked flawlessly.

Cons:

1) Frequent resets. At least 4-5 times a day the phone would reset. Mostly while texting.

2) Keyboard freezes. As others have noted theeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee problem with about 100 characters that would pop up sometimes. This happened a minimum of 10 times a day.

3) Function Key seems to have stopped working, or at least with certain combos of FN + symbol.

4) Generally unstable behavior, this kernel while promising is not ready for every day use.
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
Its basically 2G , 2.5G and 3G

GPRS and EDGE (Enhanced GPRS) are on the GSM system.

3g, HSPA are on the UMTS system.

Moving from Edge to 3g, as we know, is causing problems.

I don't see how going from GPRS to Edge would affect the phone since Edge uses the exact same hardware and frequencies as GPRS (they are both apart the same system).

But apparently it is. I always have Edge or above so cant test it out =(
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I've just heard that if you either turn data off, or evidently lock it to 2g only... SoD disappears basically.

I can't test this, again as I'm on CDMA. RIL is so very borked, and doesn't allow for really any advanced features. The more WisTilt2 talks about how little code there is for CDMA, I'm surprised it works at all :p.
[Touch Pro2, Tilt 2 Android Development] toadlife:
In GSM land, Edge and gprs are both considered "2g", but yes, they different modes; slow and slower.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
They do have different enumerations in the RIL that could potentially cause a situation in which one triggers a bug and one does not.

I should try forcing 2G - forcing 3G does not solve the issue, I forced 3G once and still had a hang. (In my case, I sometimes have hang issues with the screen on, as I have the phone set to keep the screen on when on the charger. In this case, I had it in forced 3G, and it hung in a "no coverage" state.)
[Touch Pro2, Tilt 2 Android Development] riszani:
I guess so

Hi arrrghhh, I read further on this 2g-3g switching issue, now I think this is exactly why I have daily SOD, i live about 15 Miles from Office to Home, and some where in between there a place where 3G is not available, and by the time i arrive at home, voilla: SOD.

I'm trying to lock on 2G network only, via setting-wireless but the option is on grey/ i can't select that option.

any suggestion?

oh and one more thing, I don't know if anyone experience this, whenever i leave my phone charged, as soon as the battery full, it's just keep restarting. Don't know why,

I'm using FRX 05, March 1 Rootfs on GSM Rhod 100_uk Overclocked to 710 Mhz via sovereign's XDAndroid Startup Utility.
[Touch Pro2, Tilt 2 Android Development] afrizal_chen:
When you are in Windows Mobile, disable the 3G using Comm Manager. by doing this, my XDAndroid has never switched to 3G.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Grey wireless setting - Put the phone to sleep then wake it back up, it'll un-grey. Also, when you try to undo the option, it isn't persistent - to go back to 3G you need to sleep/unsleep to ungrey it, then check it and uncheck it.

Reboots on full battery - that's a new one... :(

Disabling 3G in WM - jives with some of WisTilt2's suspicions that our RIL is missing a lot of initialization stuff which might be why data in NAND is so hosed.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Yeah WisTilt2 confirmed last night that the hardware init of the 3g modem for GSM is done by WinMo, so if 3g is disabled in WinMo or if there is no WinMo to load from (NAND) 3g will not be available to us in Android. For once something that works better on CDMA!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
hehe, makes me giggle that GSM doesn't work on NAND, when our current RIL is setup for GSM... Irony!

To riszani, disabling 3G in WinMo is probably the easiest method to ensure it's fixed to 2g in Android presently. That check box that grays/ungrays seemingly at random seems flaky at best - doesn't work at all for CDMA :p.

As for the charging bug, can you be more descriptive? You mean when you get to a full charge it reboots to WinMo....? That is definitely a new one, if so.
[Touch Pro2, Tilt 2 Android Development] dswaggz:
@Arrrghhh tell wilst2 to get gsm nand on tha ball so we can all benifit
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
WisTilt2 is not working on NAND, please don't post this in my kernel testing thread as it has nothing to do with testing this kernel whatsoever.
[Touch Pro2, Tilt 2 Android Development] dswaggz:
Hey noob question any chance the hd2 kernals can help the gsm guys on nand
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Please, don't post any more NAND-related questions in this thread. They have nothing to do with this thread.

I don't think the kernel from another device would help out NAND at all, no... Not sure why it would either, their device is not only drastically different, but their NAND is also different - AFAIK they don't use tinboot (perhaps their LK bootloader does, but MAGLDR certainly doesn't).
[Touch Pro2, Tilt 2 Android Development] riszani:
SOD

Hi arrrgh

Just loaded this kernel on my GSM Rhod100,

While booting, i have less linux booting text appearance, not exactly counting, but quite sure it boots faster.

I Don't see much different yet, since I keep having SOD even though I disable 3g before running harret.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Within 30 seconds of getting to the home screen, or later?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
So far I've had several hours with no SoD after forcing 2G. Looking good. Going to try merging the latest Diamond ril into ours and see if things work better, since right now the Settings menu for 2G doesn't work.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
CDMA or GSM?

It sort of does on GSM. Go to the menu, put the phone to sleep, wake it back up - it'll be un-greyed. To switch back to 3G, do the same, and check/uncheck the setting.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Like it says in my signature, T-Mobile Rhod210 - it's GSM only.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Spoke too soon. Now I've got blinking green LED, but frozen. (was set to 2G only...)
[Touch Pro2, Tilt 2 Android Development] gamefanatic:
Well I was using the 3.17.2011 kernels then switched to this one. The main thing that I have noticed is an increased battery life time. I went from being able to play Zenonia for no more than 2.3 hours with a full charge. Now I have been playing for the same 2 hours and have approximately 65% life left. Not sure if it's a fluke. But you can rest assured that I will keep playing when I can... ;)

Another thing I have noticed that seems random is the lights are staying on for all 4 bottom buttons. I believe a restart should fix this, but that started.

BTW I have been running 3G the whole time.

Other than that the boot up time is more than 30 seconds for the moment.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
It isn't random at all. If they are on when you launch haret, they stay on. Android hasn't got control of them (quite) yet.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I've patched the libhtc_ril_wrapper code to enable in-call audio. The code is here

http://gitorious.org/~hyc/htc-hd2-android-libraries/hycs-libhtc_ril_wrapper/commits/tp2

I've also attached a binary. To use it, you have to edit your /init.rc (which starts out in init.cfg/init.froyo.rc) and change the rild line to reference the wrapper library instead of the libhtc-generic-ril.so.
[Touch Pro2, Tilt 2 Android Development] riszani:
hi arrrgh thanks for the tips, yesterday i redo everything from formatting SD and load your original frx05 package. on my way to the office i use 2g only and no SOD or freeze. and on my way return home, i enable 3G, and practicly steering @ my phone during 45 minutes trip, and it works perfectly. so at this moment i stick whit the original frx05 kernel and rootfs, and test the charging issue. last time it happens my phone boots back to win mo, i had the latest rootfs and kernel from autobuild site
[Touch Pro2, Tilt 2 Android Development] kastg1:
As I assume most other CDMA users have experienced, I also get SOD's (both orange and blinking green) occasionally, particularly in low service areas. I also have experienced freezes that exhibit the same behavior as an orange "sod," only with the screen on. I just got back from spring break and so haven't had access to a computer/adb (which I'm new to as well, and hopefully will fully figure out by this weekend :D ).

However, one thing that I did notice about this build was the number of reboots that occur. The first few happened while I was using the phone, which I assumed had something to do with what I was doing on the phone. However, recently I've noticed that the phone will reboot 1-2 times per day even if I don't use the phone at all -- it will just be sitting on my desk sleeping, and then will flip to an orange LED and reboot. This did not occur on the prior 3/1/11 kernel. Because I don't get great reception in my house, it is possible that this is occurring when there is a signal loss, although I tried leaving the phone on my window sill where I typically get good reception, and the issue persisted. Is this an issue that others have been experiencing as well?

I'm using a Rhod400 on Sprint, syncing one gmail account, clocksync, and the weather app.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The new RIL library I've posted here may help you

http://cleanimport.xda/index.php?posts/12334841/

I've also noticed frequent crashes when the signal changes rapidly. I've made a number of patches to the ril library to fix this - mostly memory leaks that occur on each of the status change messages. I used to get SoDs within minutes of booting up, but now the phone has been online for most of a day with this library.
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Does Wistilt2 have this? How can we test it?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Bind mount it using the user.conf file.

This is basically upstream fixes to our existing RIL. I don't think WisTilt2 has seen it, but he's also more or less doing a complete rewrite of our RIL.

This RIL doesn't include all the missing CDMA commands, which is what is taking WisTilt2 so long.
[Touch Pro2, Tilt 2 Android Development] gamefanatic:
That might be true... I wasn't really paying attention, but I didn't think they were on before I made a phone call from the phone. Hasn't happened again yet.

Battery performance remains Great!

I am using a Widget called "Battery Solo" which shows the battery level and on tap shows the battery temperature. I noticed with this kernel it's not doing a good job of showing the temp. Usually defaults to 122F. Occassionally I have seen it show 77F. Not sure what's going on there.
[Touch Pro2, Tilt 2 Android Development] muziling:
Greate job, seems added some code to hand CDMA mode.

arrrghhh say WisTilt2 works RIL CDMA AT COMMAND?

So, thanks for your works. :D
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Sorry for the noob question, but what commands do we use to mount/bind this to the user conf file?
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Probably the same as this one.

Don't copy, paste this Change the name of the file
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Not quite.

The bind destination for Froyo devices and hyc's RIL binary needs to be:

/lib/froyo/libhtcgeneric-ril.so
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
So assuming I drop the files just onto the root of my sd, is this the correct command then?

mount --bind /sdcard/libhtcgeneric-ril.so /system/lib/froyo/libhtcgeneric-ril.so
[Touch Pro2, Tilt 2 Android Development] highlandsun:
No, it should be:

mount --bind /sdcard/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so

like Entropy512 already said.
[Touch Pro2, Tilt 2 Android Development] muziling:
Does F22 latest kernels merge your code, I like this kernel, no SoD, so hope F22 can merge this and NAND boot test will use this kernel too.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm F22 isn't going to do that... he was compiling kernels while the autobuild was down (which was an awesome service he did for the community) but to my knowledge he has not made any kernel commits...

WisTilt2 needs to clean up the PM code before he can push it to the autobuild service. He got a little sidetracked, so it's taken longer than usual between commits.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
New fixes on deck - enjoy guys!
[Touch Pro2, Tilt 2 Android Development] porkovich:
I know i am not the right user to report but just for info. I am using the latest Kernel on Topaz GSM. Device starts much faster than with the latest official build. WiFi is broken, data over 3G network seem faster. Pressing the sleep button kills my device.

Tested on 2.3.3
[Touch Pro2, Tilt 2 Android Development] toadlife:
Button lights!

Having the button lights is great!

Everything working fine so far.

:)
[Touch Pro2, Tilt 2 Android Development] SilverLynx:
That setting didn't work for me. I couldn't even connect with the network. I have to use the following command before it would load and work.

echo "Installing Modified RIL Driver"

mount --bind /sdcard/andboot/mods/libhtcgeneric-ril.so /system/lib/libhtcgeneric-ril.so

I am using a Tilt2
[Touch Pro2, Tilt 2 Android Development] husam666:
My EYES!, bright light under the screen :eek:,

Jk :p

Edit: false alarm

sent using a hw keyboard
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Wow iv been waiting for this update with bated breath:D

Will download, and then test and report after school :D

EDIT: got exited and decided to do intial testing early :P

Okay hardware buttons! Nice :) only thing iv noticed is that when you pull out the keyboard pressing the keyboard keys lights up the hardware buttons . . . . No biggie but idealy the hardware button light on front should turn off completly while keyboard is being used and only turn on when pressed in portrait mode(which they do perfect atm, with a perfectly timed timeout)

On to the more important stuff, first up sleep/wake, havnt done much testing yet, but thus far its wrking great. I'm not sure if its the 'great transition to deep sleep in first few hours running new kernal' phenomenom . . . Or if its permanent but I'm hoping it, but transition to deep sleep is usually within 3-5 secs! Brilliant! :D best yet :) hardly get to see the blinkn green led :D

Onto keyboard . . .Awesome! No multiple letter bug or keyboars freezes so far, had a random keyboard backlight flash. But no freeze!! So its great.

RIL . . . Yet to be properly tested. :) (might risk running android in the dreaded coverage zone of an old school building tomorro :P if it gets through a day there then I'll know it works.)

And too husam666, I'm on a 210 and its all good for me :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
[To SilverLynx & Jandyman] RIL isn't being tested here. Checkout hyc's thread for that ;).

[To Jandyman] Glad you like it tho! The PM fixes are responsible for the fast sleep :D.
[Touch Pro2, Tilt 2 Android Development] electricalve:
dude i have the radio off bug on the test kernel fck, i have a cdma running on a gsm network, soon as the phone goes into deep sleep the network mobile goes off. i have the same problem with the autobuild site kernels, so im gonna stick to the previos test kernel

everything else seems to be fine,
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Which previous test kernel does this work on? I think I know which autobuild kernel it works on, but there's a test kernel that this works on!?!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Really fast sleeps. Not so fast waking up, ~1-2 seconds. But nice. Keypad lights, I'd forgotten they exist. :P
[Touch Pro2, Tilt 2 Android Development] pdawg17:
On my Rhod400 everything is working great except it doesn't always go into deep sleep like the 3/11 kernel...I have all the same programs - only changed the kernel out...

Panel wake when it is in deep sleep occurs 100% of the time which is AMAZING! Longest panel wake is maybe 1 second...

UPDATE: Rebooted and now it's sleeping fine again...maybe just a weird "blip" before...will keep testing...
[Touch Pro2, Tilt 2 Android Development] Starfox:
I do appreciate the lack of dmesg scroll to see what's going on, I should still be able to run dmesg after to see the full output,, right?

Two things. /init tries to insmod /lib/modules/lzo*.ko which doesn't exist, and I see two errors about improper module, xvmalloc and ramzswap, I think. I know the lzo issue has been around for a while, not sure about the latter.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, some modules might be missing. This stuff is for testing, so things like that might be broken... so long as they're not present on autobuild I think they can be safely ignored.

I would actually rather not include any modules and just include the kernel, but then people would be upset with me about not having wifi :p.
[Touch Pro2, Tilt 2 Android Development] wormy315:
Using a 2.1 Sense image I get a Quadrant score of 490! (With OC of 720). Think thats thirding the faster ever kernal claim. Just bluetooth and the camera to sort now. Keyboard backlight works flawlessly for me.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I've had this with previous kernels... I think the way linux handles repeat keypresses is different from the way Windows Mobile does it. May just be a part of the paradigm shift.
[Touch Pro2, Tilt 2 Android Development] jchutch2:
Question for anyone who may be capable. On the slide out keyboard for the Rhodium at the very top a little to the left, there are 2 little white lights. One for caps and one for alt. What are the chances of getting these to work? Is it difficult to do?

Damn, I sound so trivial when I look at that. I'm really not being demanding. Just curious as to how difficult it would be to do.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It'll get fixed. One thing at a time man ;)
[Touch Pro2, Tilt 2 Android Development] elamodelmerol:
ok kb bl seems to be working fine on my sprint rhod400...wifi it's partially working...

i am able to connect to open/wpa secured networks..

wep secured networks won't work/ can't connect at all it only keeps trying...

anyone out there experiencing the same issue?
[Touch Pro2, Tilt 2 Android Development] jchutch2:
My wifi tends to constantly go into "error" mode. Really not sure why. It'll come on when I reboot it occasionally. Or if it's too bad, I'll copy back the data.img file I have backed up and poof it works. Wish I knew of a way to debug why it's doing it.

**EDIT**I think it may be a time issue. WinMo goes 5 hours ahead when I reboot for some dumb reason. If I don't reset the time, the Wifi won't come up.
[Touch Pro2, Tilt 2 Android Development] jchutch2:
Honestly, I just wondered if it was such a small issue that noone noticed. :)

Also was curious if it was something I might be able to handle, if given a point in the right direction. Would love to actually be able to contribute.
[Touch Pro2, Tilt 2 Android Development] elamodelmerol:
how's your wifi secured? WEP, WPA2/PSK , Open?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Make sure you have the correct matching modules file, and any old modules have been removed.

WEP doesn't work, and is extremely insecure. Any 12-year old script kiddie can crack it with simple packet injection software. They'll have your key in less than a minute. Use WPA2...

Also this is status quo for Android - as in this is how all kernels have been...? Please let's try to keep this thread on-topic guys. Wifi is NOT the point of this test kernel.
[Touch Pro2, Tilt 2 Android Development] elamodelmerol:
ok i understand WEP is not secure at all i don't use it myself but unfortunately there is still a lot of people/business that still use this primitive algorithm. can't make them all to modify it just like that...

i thought wifi had something to do with the developing of this kernel (since you guys just fixed it) if not i beg your pardon i was just trying to give my 2 cents making sure u guys are aware of this.
[Touch Pro2, Tilt 2 Android Development] ksper6986:
hey arrrghhh is the 1\2\11 kernal new because it has the same commit code as 1\1\11