yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] phazi:
Thanks

hey been in the shadows watching the whole development going down. you guys have done really done an amazing job. every issue i have had has been fixed by an update from you guys.

But i think i might be having this issue only as i cant find it being posted any where else. i don't know if its a kernel related issue but thought this is a starting point to find a solution .. i receive a sms from any one and instead of the message being displayed it displays a a message saying "Bad SMS Encoding" its happened with 2 different contacts some times no matter how many time the person sends the txt i receive the same message, and sry if it isn't a bug in the kernel

i have the Verizon touch pro 2
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
Loving this new 2/28 kernel. Thank you devs. Been running droid on my tilt2 and not going back to windows.
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
awesome kernel super fast wake & speed. best kernel to date. now i cant wait for the camera & instawake to get commited in the same kernel
[Touch Pro2, Tilt 2 Android Development] rpierce99:
It's funny you should mention that.....
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Shhhhh... I need to have some tricks up my sleeve.
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
what u mean by that
[Touch Pro2, Tilt 2 Android Development] vnes1984:
you holding out something? Please do tell
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'll post it tomorrow... that is all.
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
yaaaay, thats going to be great
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Heh, assuming the issues can be ironed out. I was hoping it would "just work" but I'm running into all sorts of weird issues...
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
take ya time my rhodium aint going anywhere especially since i cant sucessfully reattach my hd2's lcd + digitizer
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I tested this, cuz I was curious. Seems to be a bug, as the phone isn't actually charging... try it for yourself, do what you describe and then wake the screen. Doesn't start charging until you wake it... I'll mention it to WisTilt2 to see if anything can be done about that.
[Touch Pro2, Tilt 2 Android Development] codedesignr:
Yeah I saw that, the battery icon takes a moment to change to "charging" when you wake it. Good to know. Thanks. One more thing. I had the phone charging with a USB cable from my computer, I unplugged it, but a half hour later, I still had the USB testing/connected icons on my screen. The phone wouldn't sleep, and I don't know if it was because the phone thought it was connected, or, more likely the Redbox app may have turned on GPS. I'll try connecting it again tomorrow to see what happens.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Had the same thing with 26/2 version and usb charging, the icons wouldn't go. Sleep was no problem though.
[Touch Pro2, Tilt 2 Android Development] afrizal_chen:
27/2 was a nightmare, phone freeze for about 30 seconds after making call, a lot of flickering. I change to 28/2 this morning, and it works smoothly until now, no freezes no SoDs. Good work! :)

I'm using RHOD100 from Taiwan, but RHOD100_UK matches my keyboard layout best.
[Touch Pro2, Tilt 2 Android Development] shatred:
love this latest one!

seems like 28-02 is it(except the recharge bug), been using it now for 5-6 hours, not an single failed wake-up or sleep.

using f22 latest rootfs + latest GB from stine's repo.

Very stable build, with good battery life (used the phone for 5-6 hours and it only used 30%
[Touch Pro2, Tilt 2 Android Development] snalbansed:
New kernel very nice. Still getting SODs though, and no sensible logs. 2 so far today.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
I have not has such issue with the pre-2/28 test kernel from this thread. So you are saying that 2/28 kernel breaks charging while screen is not awake, or was it this way all along?

The reason I ask, is I guess I use a work around anyway when charging and didn't even realize it this bug has been there from the start, because I only charge at night when going to sleep, and I use the alarm to wake-up so I put it in clock mode and dime the screen, so it never actually goes to sleep, and the screen stays on all night in a dim setting, so therefore it always charged for me.
[Touch Pro2, Tilt 2 Android Development] codedesignr:
The phone will charge if you plug it in while it's awake. From there it can go off and to flashing green or you can press the power button and it will charge no problem. It won't charge if you have it in deep sleep (solid green) before plugging in the power cable.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
I'm trying it now - Previously I turned on GPS to keep the phone from going to sleep and had it on a charger all the time.

One thing, in terms of terminology, I have seen "Sleep of Death" and also "failed wake" - I previously thought these were two terms for the same thing, however some people have been keeping independent counts of both - what is the difference?

So far no problems, although I assume logging is broken if I do encounter an issue from the brief "failed to open tty, logging disabled" or something like that error at the end of the first phase of the boot process prior to displaying the xdandroid animation loop.
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Yes, this is true or you can plug in your phone and then turn the power on and off to get it charging. I also noticed my screen did not turn on while charging when I received a call. I swiped my finger in the place the unlock is and I was able to talk.

Great kernal though
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
WisTilt2 said this only applies to USB. Unfortunately I have no AC charger with me to confirm, but he said that every time he plugged in AC it eventually woke and started charging on its own. With USB, it doesn't wake on its own and won't charge unless you wake it up. If you plug in the charger when the phone is awake, you won't have any problems.

I'm in the process of posting a new kernel. It's going to come with A LOT of caveats... but people really wanted it!

Alright guys, kernel posted. Let me know if I'm just crazy on the libs thing, maybe I just have some outdated libs? I have the "newest" stuff that's public in jb's cam testing thread...
[Touch Pro2, Tilt 2 Android Development] Germypan:
Sorry i have a question... the new autobuild kernel is the 1276 but the kernel download from the first post is a 1260... have this ultimate kernel some settings from autobuild kernel?
[Touch Pro2, Tilt 2 Android Development] mbellot:
Just dl'ed it and the archive has the same file sizes and dates as the 02-28 archive I dl'ed yesterday. (2/28/2011, 14:39)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oops! Thanks for saying something guys. I uploaded the wrong one, d'oh. I double-checked this time, it's right now! Go ahead and re-download... Sorry 'bout that!
[Touch Pro2, Tilt 2 Android Development] Germypan:
Thanks... i downloaded and now i'm testing the new kernel!

Thanks

Germy
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ok, so this is interesting. The libs are obviously suspect, and when I have the libs disabled and try to use cam, the phone refuses to sleep. So if you use this kernel with the libs disabled and don't touch the cam, you'll be fine... but that was kinda the point of this kernel. I guess the first one can't go perfectly, eh? :p
[Touch Pro2, Tilt 2 Android Development] jmstumme:
Interesting, I've just took 2 pictures and the phone is solid green light. arrrghhh, is this what your getting, or is it just blinking green?
[Touch Pro2, Tilt 2 Android Development] rpierce99:
After the issues I had last night, I rebooted and left the libs mounted, camera and camcorder. I am currently sleeping fine (solid green) and have been all day.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What did you do differently...? I've rebooted tons of times, still can't get the phone to sleep. I haven't re-enabled the libs tho.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Just to add to the feedback, I'm using the 3/1 kernel and my phone goes into deep sleep fine...

Btw, is it known that audio does not work on camcorder?
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Small report on the 28/2: lots of freezes and erratic behaviour in apps, even suddenly booted into bootloader (the green red blue white screen)! With a new data.img however things are ok again. But battery life seems still best with 26/2 version. Will try the new version tonight. Btw, how do you disable the user libs?
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Sleep works for me after using Camera..

I used the standard Camera App for Android. I took a couple of pictures, and then pressed the power button to get it to go to sleep, and I get deep sleep (solid green LED) just fine. I just added the kernel and zimage to my folder and did nothing else for it to work.

Not to thread jack, but I was under the impression the camcorder still didn't work period. I activate it, and camera app force closes on me after teasing me and actually allowing me to press the record button.
[Touch Pro2, Tilt 2 Android Development] sb283:
Can the cause of the phone not sleeping be the same as with GPS? It looks very similar to me. You can have GPS ON in the settings and everything will be fine until you use it. Then, you will never see the green LED until you disable the GPS. According to some posts in this thread the camera behaves the same way.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Result of trying 2/28 - At some point my phone spontaneously rebooted, since then I'm stuck in an acore force close loop. Gonna have to nuke and repave tonight.

Gonna try 3/1 tonight too.
[Touch Pro2, Tilt 2 Android Development] skimike02:
Full sleep, google goggles, camera, video all work. Thanks!

Rhod210 FRX04, this kernel, 2/28 rootfs, libs and conf from camera testing thread, ipv6 enabled.
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
yea my phone used to do that when i was restoring text, calls, and all the storage options with titanium backup. now i only restore apps and it doesnt show the acore loop ;)
[Touch Pro2, Tilt 2 Android Development] hashtowent:
3.1. kernel is fine for me fast staple and camera is working with new blazn build!

(= it rocks kinda

love your work wistilt! go ahead!
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
how do i enable the libs for camera? because when i open the app its just a black screen and my phone no longer sleeps
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Hey Arghhh question on your problem and sleep mode...

I finally got the Video Camera working on my build. I didn't have all the proper libraries downloaded from the camera thread. Before I was just able to use the camera only, and it still went into deep sleep.

Now it will still go into deep sleep after using camera or video camera, but instead of the LED blinking green like 10-20 times before going into a steady Green LED meaning sleep, it only blinks 1-2 times then gives me a steady Green LED. Is the LED giving us false readings again like the GPS enabled/sleep mode did with the earlier test kernel from this thread?

I am just wondering if I am truly in sleep mode or not. Only way to find out if you don't know is to test battery life for 24 hours or so I guess.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Blinking green means it's partially sleeping, solid green means it is in deep sleep, there's no fake sleeping anymore.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
3.1 Kernel

Damn! I'm tempted to try out this new Kernel but the 2/28 Kernel is working so perfectly. from what I have read on ppls feed back about the 3.1 Kernel, it still needs to be ironed out.

I have a tilt2, anyone with a tilt2 running this new kernel? and how is it working.

I'm a litle anal when it becomes to my phone.
[Touch Pro2, Tilt 2 Android Development] afrizal_chen:
On Rhod100: I switched from 2/28 to to 3/1 last night.

- I never get blinking green light (which I had on 2/28)

- Start the camera, feels smooth, take one picture, and tada.... phone freeze. have to reset.

- No SoD until this morning, except the freeze caused by camera.

- Battery life is Good, I charged it full before i sleep, and when i woke up (8 hours), it's still 87%
[Touch Pro2, Tilt 2 Android Development] ivwonka:
This 3/1 kernel work very good for my rhod400. thanks. And I wish I would have learned sooner to turn gps off so it will sleep right. Maybe add to first post?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Considering it's not unique to this kernel, that's not going to happen... Read the FAQ.

Also, glad to hear you guys got some good experiences on this kernel. I found the no sleep issue was caused from not having the proper libs, as was posted earlier ;).
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
3-1

using tilt 2 with 3/1 and the battery life seems pretty great! I had running since 6:30am and used all through school (downloading apps,games,etc). its 6pm and at 45%.

No FC's or SOD's while out. Haven't played with camera yet and wifi/a-gps still puts me off south Africa =*( but when im outside using real gps it works fine.

seems very stable!

Q: Has anyone looked into the SOD/freezing caused when cell reception is lost. I live in a dorm and have no reception while in room therefore i have to use AT&T's microcell. It works fine booting android when im in my room and all. The problem i get is entering room i loose reception and then it usually picks up the microcell but everytime it SOD's and never wakes up again =( i remember others committing about this issue in low reception zones.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Known issue, related to our horrid RIL. Hopefully we can get an actual radio programmer to look at the code soon, but until that happens... there's really nothing we can do. Unless you know how to rewrite RILs :p
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
how do i reapply the libs
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
That happens to me too, i get SODs when there is no reception. How can i fix this?
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Don't. Just update to FRX05.

http://files.xdandroid.com/system-FRX05.ext2.zip
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Did you not read my post? Oy.
[Touch Pro2, Tilt 2 Android Development] wmg316:
Ok...call me slow...but if I download the new ext2 file and run this 3/1 kernel, I still need to follow instructions in the camera development thread, i.e., use the adjusted user.conf file and the lib_camera folder?
[Touch Pro2, Tilt 2 Android Development] AkumaX:
wtf FRX05's out? is there any documentation?

edit: http://southcape.org/2011/03/01/xdandroid-2-2-2-froyo-build-frx05/
[Touch Pro2, Tilt 2 Android Development] rpierce99:
No, the reason you would upgrade to FRX05 is because all of the libs that you would normally have to mount via froyo.user.conf and put in lib_camera are baked right in. FRX05 + this kernel (or autobuild) = camera/camcorder, stock.
[Touch Pro2, Tilt 2 Android Development] wmg316:
3/1 Kernel with 3/1 FRX05 ext2

Post moved to Camera thread
[Touch Pro2, Tilt 2 Android Development] pfeng:
HI, FATAL EXCEPTION occurs when switch to video record on my Tilt2. here is the error log:

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): java.lang.RuntimeException: java.io.IOException: prepare failed.

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at com.android.camera.VideoCamera.initializeRecorder(VideoCamera.java:942)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at com.android.camera.VideoCamera.access$300(VideoCamera.java:85)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at com.android.camera.VideoCamera$MainHandler.handleMessage(VideoCamera.java:201)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at android.os.Handler.dispatchMessage(Handler.java:99)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at android.os.Looper.loop(Looper.java:123)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at android.app.ActivityThread.main(ActivityThread.java:4627)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at java.lang.reflect.Method.invokeNative(Native Method)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at java.lang.reflect.Method.invoke(Method.java:521)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at dalvik.system.NativeStart.main(Native Method)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): Caused by: java.io.IOException: prepare failed.

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at android.media.MediaRecorder._prepare(Native Method)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at android.media.MediaRecorder.prepare(MediaRecorder.java:503)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): at com.android.camera.VideoCamera.initializeRecorder(VideoCamera.java:938)

03-02 13:43:39.270: ERROR/AndroidRuntime(2943): ... 10 more
[Touch Pro2, Tilt 2 Android Development] wmg316:
Is the kernel posted here in this thread with "dirty" in the file name the same as the kernel posted at glemsom (no "dirty" in the file name)?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No.

The "dirty" modules means that there are local commits basically. If there is no "dirty" in the modules, that means it's from the autobuild...

It's not readily apparent which kernel is which, short of the 'dirty' modules, and obviously when you boot and go to About Phone.
[Touch Pro2, Tilt 2 Android Development] shatred:
latest kernel has AMAZING battery life for me. when i tried this kernel my phone said it was 80% in winmo. after booting in android it said 78%, and i have been using it after that for 2 hours, then i was sleeping for 7 hours so the phone was in deep sleep, en now this moring i have used it for 1 hour again and guess what? battery is at 52 % (did not recharge or put in to pc at any time)

further, i haven't tried the camera libs yet but i confirm what aarrgghh said about the sleeping bug with cam, if you dont activate the libs, then you can just use it normaly with good sleep just be sure you DONT start the camera app as that will make your phone unable to deep sleep until you restart it lol.

Gonna do more testing today for more feedback.

to check what build i use see my signature.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Another update (Frx04)

Battery life for me today decreased by 40% after 6 hours all deepsleep(no waking, no internet, no apps open)

Dat 'roughly' works out at about 7percent per hour.

*with as close to 0 usage as possible. Battery drain is much higher with any usage . . . . . So battery life still isn't up to par with what others have been getting on identical setups :( still havnt figured why this is.

Also the latest kernal is stable in the short term, but I got and SOD today, tried ringing the fone but still no luck. I don't think any of the test kernals yet have survived the 5hour sleep stint from morning to lunch for me XD

Also just to mention . . .don't tink it has anything to do with wistilt2s commits but u kno the error with freezing on one letter and typing about 190(I counted) of that one letter? (And can't be stoped) iv been gettn more of dem lately . . .3in writing this passage :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, that's some odd drain. I thought WisTilt2 said he put the sleep_mode forced to 1, but what sleep_mode do you have on?

Also, was the phone sleeping correctly? As in solid green LED?

As for the out of control repeat letter, I have had that before... No clue what it is tho, very frustrating indeed! I have a suspect it is related to the kbd bl code, but I'm far from positive.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Yeah I'm using sleep_mode=1, just checked to be certain . And yeah it was solid green wenever I checked on it. GPS disabled as usual and sync was on . . . .but after checking gmail it hadn't synced in four days(forget to restart autosync) so I'm pretty sure that wasn't the cause of it. Its rather puzzling O.o any more theorys? :)

Also about the letter repeat, I forgot to mention that actually, you are probly right, this glitch did start around the time of the Keyboard backlight and alt/caps. But I presume someone is probly working on it as its hardly an inconspicious bug :)
[Touch Pro2, Tilt 2 Android Development] wmg316:
So do you know if the camera changes in the "dirty" version of this thread were implemented in the autobuild version?
[Touch Pro2, Tilt 2 Android Development] snalbansed:
FRX04 rhod100_uk AUO panel

1st March kernel - still getting SOD.

I'm now wondering if they are related to the RIL issues you refer to arrrghhh. At home, I rarely have a SOD. I always leave my phone in Android on charge at night, and I don't remember the last time it SOD at night, so the alarm is quite reliable.

During the day at work, I frequently get SOD, sometimes minutes apart, sometimes hours. The only way to avoid it is to go back to Novembers kernels.

At home, I usually have a reasonable 2G signal. At work, I usually have a 3G signal with 0 bars.

What do you reckon?
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
no camera

Been trying this for the entire day. Everything is fine for the most part up to now, but the camera is not usable. Most of the time it reboots into winmo when I open the cam app, but sometimes it shows a distorted image, sometimes orangish, sometime blue-ish, cut into parts etc. When I go back to the home screen and try again, it says "cannot connect to the camera"

I tried the following:

formatted SD to fat43 with HP tool

downloaded stock FRX04 and put on SD

replaced kernel and modules from this thread

replaced rootfs with most recent

replaced system.ext2 with the FRX05 (from a few post earlier)

Any clues?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sorry, we're not going to troubleshoot the camera in this thread... if you're having issues with the cam code, address it in viruscrazy's thread.

I'd say the service is the problem. WisTilt2 is looking at RIL issues with SoD.

Uhm... Not sure how to answer this. WisTilt2's newest changes are not in the autobuild kernels, but WisTilt2's kernel is completely up to date with autobuild.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
feedback on 3.1 Kernel

I'm using the FRXO5 with the above kernel. So far its working great But not using the camera at all. I will leave the camera alone for right now.

Thanks Devs
[Touch Pro2, Tilt 2 Android Development] ivwonka:
I have been running this kernel for 17 hours off one charge and still have 56% battery! This is with no phone calls and trying to be conservative with screen use, but it is still proof of point. Great battery life. I am going to keep this going and see how long it will go. Maybe post a screenshot of battery use. No sod or freezes of any kind
[Touch Pro2, Tilt 2 Android Development] shatred:
i had one reboot 2 hours ago though, the phone froze for 2 mins then it rebooted itself (showing boot animation again). but this was probably because i am running gingerbread and i was running out of ram :p
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
frxo5

rhodium 400 frx05 and this kernel. Initial startup is slow need to make phone call for server reset. Drains battery quickly, but I think my battery is at the end of its life. bar-code scanner works scanned several bar-codes.. Navigation works. Clock widgets work. Skyfire works. Movie phone plays trailers. Everything seems to run smoothly and stable.

I had it on FRx04 for 24 hours before no problems put it through the ringer.

I think you guys are hitting the nail on the head. Ata-Boy and all the hoopla.