yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] Entropy512:
I just had the "stuck no service" situation happen again.

Is there any way to save a dmesg and adb radio log without downloading anything or using ADB?

Otherwise I'll probably lose the logs from this event, no ADB for hours and no service to download anything from the market. (If I reset the radio, the logs for the event will disappear - the log depth isn't large enough to hold everything from a radio reset.)

Crud - never mind, it's not just stuck no service, phone UI is completely hung. I suspect it's the same as "orange LED death" except that the screen was on to begin with.

Edit: Just thought - I have a calendar widget and I was poking at my calendar quite a bit before this happened.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
I'm running GBX04 with the 3.1 Kernel and I havent had any SODs in about 3 days. even when I dont have service, my phone stays asleep.

When i was on FRX05, I use to get a lot of SODs when i didnt have service.

Or maybe I dont get any SODs cause I reboot my phone before I start my day.

battery life is awsome. I disconnect my phone at 8am and by 4pm, I have 95% of battery left.

Thank you Devs!
[Touch Pro2, Tilt 2 Android Development] Entropy512:
To clarify, when you say SOD, do you mean "phone unresponsive with green light" or "phone unresponsive with orange light"

I'm finally learning the terminology, but the "classical" SOD is an unresponsive phone with a green light. These apparently were kernel issues.

An unresponsive phone with an orange light isn't a "classical" SOD, but it's pretty similar - what should the proper terminology for "orange LED death" be? - These issues seem to be occurring in userland (likely RIL) - and the difference between FRX05 and GBX0A is telling here, as in this case, you've changed userland but not the kernel. (There are different RIL branches for gingerbread and froyo - how much difference is actually here?)
[Touch Pro2, Tilt 2 Android Development] Jandyman:
hhhmm about the same as me, not the SOD but battery life is similiar. Except i have a rhod210 so i have and EID panel.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
With a fair amount of usage, this isn't unheard of.

However, if you guys are saying 6hrs -> 50% in deep sleep the entire time, there's something wrong ;).
[Touch Pro2, Tilt 2 Android Development] shatred:
using this with frx05 now for 3 days. i currently have an up time of 18 hours (when i started phone it was fully charged) now the battery is at 23% with light usage. (i did not recharged or connected to pc in meanwhile)

i only had 2 sod's but those happend when at the startup (when the lockscreen appeared i waited for 2 min's, then i tried to unlock the phone but it was frozen, rebooted and everything worked fine)

so battery life is pretty neat for me.

BTW. i noticed that when you set brightness to max the phone battery drains about 3 times so fast for me.

for example, if i set brightness on lowest i have 90% battery after 30minutes of heavy usage with wifi enabled.

if i set brightness on max i have only 60-70% battery left after 30mins of heavy usage with wifi enabled.

Is it normal that the brightness drains so much battery?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Autobl is best.

But the battery meter isn't so accurate - don't trust it. One of the many things being worked on...
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
I switch from simplicity rom to the latest energy rom and i have seen a big diference on battery when im using GBX04. when i had the simplicity rom battery was really good. Can a wm rom make a diference?
[Touch Pro2, Tilt 2 Android Development] snalbansed:
What is this GBX04 you keep referring to? Are you trying to wind us up, or are you just mistaken? Everyone else is on FRX05 or GBX0A (Alpha, not even at 1 yet!)
[Touch Pro2, Tilt 2 Android Development] husam666:
Alpha 4 is released on neopeek
[Touch Pro2, Tilt 2 Android Development] shatred:
yep here :http://www.neopeek.com/viewtopic.php?f=14&t=5764
[Touch Pro2, Tilt 2 Android Development] Entropy512:
That isn't GBX04, so please don't call it that.

In fact, the FRXxx/GBXxx designations are one used by the xdandroid team for their releases, so please don't use any of these designations to refer to a Neopeek release.

As to WinMo ROM making a difference - I remember people always saying that after flashing a ROM you had to run it a while until something calibrated to get good battery life. This never made sense to me - but maybe they meant you had to run it a while to get the battery level reporting calibrated? I'm wondering if reflashing a WinMo ROM nukes some calibration statistics that are used to determine actual battery levels properly. However, since I don't think we yet fully support the battery management capabilities of our hardware (which is why battery reporting is inaccurate), I'm not sure if this even matters. (I'm still trying to understand the battery handling source code... I haven't yet found the calculation for actual battery level, but it seems like we're basing it solely on battery voltage because of how our battery meter behaves - an accurate battery meter will base level readings off of voltage and current, or even better, will coulomb-count every milliamp that is drawn from the battery - however I'm not sure if our battery monitoring hardware supports the latter approach.)
[Touch Pro2, Tilt 2 Android Development] husam666:
I know, I didn't say that's GBX04!!

I said it's alpha 4, maybe what the other person referring to.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Heh you tell 'em.

This thread really went for a turn... What's up guys?!? :p

Don't worry about the battery code. Jonpry and WisTilt2 (mostly jonpry TBH) wrote a battery calibration application, and when we get it tuned it will run automatically and calibrate to each individual battery - because every battery is different. Even if you have "the same" battery - make, manufacturer, heck even if they rolled off the line together - they will act differently and need to be calibrated individually.

So far the process is extremely manual... jonpry wants to sort out just how long the calibration tool should run before it crunches the numbers and applies the changes. Read up on the #htc-linux logs, it's pretty interesting ;).
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Dude, thanks for the link. I'll have to try and start hanging out there, might make my GPS work more productive. (I'm hoping to try and fix a few other things before making up a patchset.)

I think since it's been a while since the last kernel release (potentially because the kernel may not be where our stability problems lie), this has started to evolve into a generic stability debugging thread... Maybe it's time to create a new thread that focuses on a comprehensive effort to troubleshoot weak-signal stability?)
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Lol unfortinatly i am :P in deep sleep all the time i always work it out as getting about 7%per hour. . . but as to why is still a mystery to me :) iv mentioned before and there hasnt seemed to be a solution. It also appears to sleep fine. But i recently formatted my 8gb sdhc as a last resort, becasue i havnt in a long time and havnt recorded battery since, so unless this miraculously fixes it. . . XD

Also have a suspicion that maybe the problems with the RIL has caused my radio to eat the battery. . . im not sure.

But besides RIL issues the kernal is working flawlessly so far!
[Touch Pro2, Tilt 2 Android Development] Entropy512:
FYI, a weak signal is going to cause your radio to eat battery even when in deep sleep.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Indeed. Poor signal will kill any device, as it struggles to get signal. If you know you're going to be in a poor signal area, airplane mode might be the best remedy...
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Hhhmm yeah that's probly it. I usually have full coverage at my house (where I usually test battery) but in places in the house coverage drops so me walking through better/lesser coverage areas is probly the problem. . . ..also I kno for a fact when I test at school cov erage is definatly draining my battery.

I'll try testing in a full coverage area and hope for the best :)

Also I can't wait for the next test kernal, the progress is amazing :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
New kernel guys... great stuff on tap here, let me know what you think ;).
[Touch Pro2, Tilt 2 Android Development] duhovnikov:
first feedback compared to 1276 used on FRX05:

Boot -> faster (with less console text)

Faster deep sleep (solid green in standby)

Much faster wake-up (before sometimes I had to press the power button several times until it wakes up)

RHOD100
[Touch Pro2, Tilt 2 Android Development] Quincux:
Downloading and testing the new kernel. Thanks
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
SoD

I didn't do anything with my phone for about 1,5 hour.

I wanted to wake it up but didn't respond.

Waited 20 minutes but didn't do anything.

It was trying to sleep(Blinking green led).

So a SoD.

Kernel from 3/1.

Will try the newest kernel now.

EDIT:

Can't upload file in the XDA app for android.

Is there an app for a website where i can upload things?

(Not having to upload in the browser)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
As to your edit, there's an app called dropbox - allows you to upload things to your dropbox account and provide a link easily.

As for your log, sorry, it's empty. Still can't get WisTilt2 to enable them, I think it's related to moving the FB into SMI memory instead of EBI.

Need to get that enabled... grrrr
[Touch Pro2, Tilt 2 Android Development] highlandsun:
No real change here. With data enabled, hangs within 10 minutes of going to sleep. (Was sleeping with solid green LED, hangs with orange.)
[Touch Pro2, Tilt 2 Android Development] Sebastian55129:
"first feedback compared to 1276 used on FRX05:

Boot -> faster (with less console text)

Faster deep sleep (solid green in standby)

Much faster wake-up (before sometimes I had to press the power button several times until it wakes up)

RHOD100 "

same at my phone too. But i have one Problem: At Incoming calls the Phone only vibrating. No sound. Ringvolume is 100, In Menü i can play and hear the Ringtone.

But when a call incoming, no ringtone.

Checked this in deep standby and in on-mode.

any idea?

greeting

sebastian from mainz, germany :)
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
I forgot to mention that after the reboot, i upgraded an app and when it was installed it rebooted(flying android things).

Thx for the app.

I can't make any sense of the second part of your reply, but thanks anyway for the explanation:P
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm. Seems like there may be more than one cause for the SoD (not surprised there). The RIL issue with SoD is still present, it would seem. You and others have confirmed that for me, thank you ;).

Uhhh... never heard of that issue being kernel related. Almost certainly userland - delete data.img, call me in the morning.
[Touch Pro2, Tilt 2 Android Development] Sebastian55129:
Thanks, this Fix that Problem. But now all Apps an Settings away. I try now the old one and test an Backup app.

Thank You
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oh yea, sorry I didn't make that clear.

Doing that will blast out all you've installed and changed :p. Titanium Backup makes this a little easier pain to bear ;).
[Touch Pro2, Tilt 2 Android Development] Sebastian55129:
I dont delete the old one, i. Renamed it ;)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Good for you! TB is awesome, although annoying to restore unless you pay for the app.

I got sick of it, and ended up paying for the app :D.
[Touch Pro2, Tilt 2 Android Development] eik:
Not sure if it is coincidence but I noticed some less deep sleep (after having used it sometimes it does and sometimes doesn't) and had my phone almost run out of battery in 7 hours or so. Wasn't used to that anymore ;)

Just rebooed my phone and will see what it does overnight.

rhod100_uk AUO panel.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, I haven't noticed any sleep problems/additional drain. Make sure there isn't any apps keeping it awake, or the usual GPS/loc etc.
[Touch Pro2, Tilt 2 Android Development] budbrown:
quick install/all file list for tilt 2

I've been having major problems with most xdandroid versions since the 1/23 update. I can't seem to get 1/23 to install using the the update feature with the utility so I can't start with that and upgrade to this.

I have a tilt 2 with the stock rom. can someone with a similar setup help me out?

in addition to the wistilt files, what specific files should I use to create a working build
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Please, these files are for testing only.

If you have build related questions, post in the build thread.

The update utility should not be used any longer to update - it doesn't update anything AFAIK.

If you want to use FRX05, I have created a bundle found here.
[Touch Pro2, Tilt 2 Android Development] eik:
After the reboot yesterday I left it overnight and the drain/sleep is now normal again (at least what we've become to think is normal after Wistilt2 did all the work for the AUO panels :D)

Will keep an eye on it.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
Just installed booted back into Android and used Maps, the map marker was way off. Booted back into winmo updated satellites and it was back on track. Weird thing is I updated satellites yesterday so the info should have still been in the system. I would not think that the kernel update would affect the satellite data. Just an observation.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Eh, if we ever get the XTRA interface working so we can use Android for agps instead of needing WinMo. This'll become much more important when we go NAND - for better or worse, the HD2 guys don't have this working either ;).
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Define "way off"? Is it typically at lat/long 0,0? (It could be elsewhere, but it usually is around 0,0). There's a bug where the GPS driver gives position reports to the upper layers when there is no lock - so your position is whatever the contents of some uninitialized memory are. (Typically translates to a small number, but it could be something other than 0,0).

I've identified a fix for the issue and have it working, but haven't gotten around to making/submitting a patch file yet. I was hoping to clean up some other GPS-related items first, but I'm beginning to think I need to just submit what I have to the devs so they can release builds that at least don't do really screwy things.

As far as the known issues:

On Rhodiums, the GPS reports height events long before it has a lock. This isn't possible, either the chipset is severely broken, or what we think is a height report is something else. (This is the root cause of the "position without lock" bug - my fix is just a workaround for now.)

On Rhodiums, we never get satellite status until we're locked.

XTRA (QuickGPS) interface is not implemented. It's stubbed out in such a way that any app which tries to load XTRA data will report success even though nothing happened. Without some documentation or an ability to sniff the interface in WinMo, this will never get implemented.

Interface for "hinting" the GPS with a rough lat/long/time for faster fix isn't implemented. Same criteria for implementation as XTRA.

Edit: Does anyone know if the XTRA data is nonvolatile once sent to the GPS? Or does it have to be sent to the GPS on every boot? (e.g. always hit QuickGPS within WinMo before you start haret?)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You're doing awesome work! Can't wait to see some patches on this... although if you have some cleanup for the GPS code, that would probably be best.

As to your edit, I think it does survive reboots - I'm not sure how I can confirm this for certain, other than just gauge how long it takes the GPS to actually get a lock. I can certainly try that a few times and see if there is a big difference between booting Android after a fresh QuickGPS run and after a full soft reset to WinMo and hit Android again without running QuickGPS....
[Touch Pro2, Tilt 2 Android Development] EazyVG:
Did a small research on XTRA and perhaps this might help us. I still have QuickGPS fresh, another 6 days to go, and then without updating it will try GpsFix to see if it helps ... anyways try and let us know .... http://www.appbrain.com/app/gpsfix/com.androidlab.gpsfix

This thing works on HD2 and some other WinMo devices when running Android!

UPDATE: With above situation I got fix in less than 10 seconds.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, but the HD2 still doesn't have the XTRA interface functional - as in, it cannot affix the agps data onto the chip like QuickGPS does for us in WinMo.

Correct me if I'm wrong, but that app just allows the GPS radio to stay on so it can keep its fix, no?
[Touch Pro2, Tilt 2 Android Development] EazyVG:
To reply with confidence will have to wait till the WinMo QuickGPS expires ... will report later :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Fair enough. What about the other question? If you do a full reboot does the QuickGPS data stick?

I have yet to try this - doesn't seem like a real good way to confirm, other than to see if GPS gets a quick lock or not..
[Touch Pro2, Tilt 2 Android Development] eik:
I try to understand the GPS behaviour... I expected the fix to be faster when the most recent fix was fairly recent. But today I had a fix in the afternoon. Then in the evening when I switched on the gps again it took over 30 mins to get a fix. Weird. It is a bit of a bummer to hear that it might not get solved...

On the other hand I haven't had a freeze of the phone so far with the newest kernel. This is quite exceptional as I almost always see the phone freezing when traveling around. I had to switch the phone a few times to airplane mode and back to get the data connection going again.

rhod100_uk AUO

Edit: still having freezes
[Touch Pro2, Tilt 2 Android Development] Entropy512:
I'm getting to the point where I'm probably going to submit a fix for the 0,0 thing and debugging within that file (the 0,0 fix is a one-liner), but getting sat status working right is making my head hurt.
[Touch Pro2, Tilt 2 Android Development] Eodun:
I'm pretty (99%) sure that it's nonvolatile. I get fast locks for days, then one day it takes too long and et voilà: have to run quickGPS.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
about 2 or 3 city blocks. I am offroading it on main street
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Heh, hang out in #htc-linux more and bounce some ideas off of some of those guys... Even if they don't have a RHOD they're usually very helpful. Especially if you know what you're talking about (which you obviously do ;)).
[Touch Pro2, Tilt 2 Android Development] DopeyOne:
This new kernel is amazing on my rhod100 (Auo), before if I left my phone overnight it would either sod or die from battery drain... last night I left it and woke up with lots of battery and a functioning phone! Only thing changed was the kernel from 3/3 to 11/3

Amazing work guys!

If you need any dumps for the ril troubleshooting, let me know.. alll I have to do is move my phone away from my window while its asleep and 3/4 times it will lock up (it will generally come out of deep sleep and freeze (orange death)

Rhod_100 auo. Frx05
[Touch Pro2, Tilt 2 Android Development] salik1992:
I tried latest build (11/3) and with RHOD100 I get SoD when:

1) Turning off WIFI -I can turn it on, but cannot turn off (results in SoD)

2) Battery is charged 50% and lower - I mean I get SoD in 5 minutes after discharging below 50% or after reboot when it is 50% or lower charged.

I hope it will help you. Keep up excellent work.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
I had an issue with the new 3/11 kernel today. I received a test message. I pulled the top menu down to access it, and it froze half-way down. I then pressed several buttons trying to get it to respond. I finally pressed the power button to try to put it to sleep. It blinked green a few time, I then pressed it again to try to pull it back up. It was still frozen. I got a phone call on my office phone, so the screen was still up, but by the time I got back to my phone the screen cut off and I had an orange LED, and now have a SOD type issue.

Seems like the Text message caused the phone to freeze up. It is going to be hard to try to recreate the issue and get any kind of dmesg since I have to reboot.

Also this kernel still has an issue of having to press the power button a few times to get the screen to finally come up, but I can live with that.

Another FYI, I have probably had xdandroid running for about 48 hours without reboot when this happen. I am running a Rhod400.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
I haven't heard any reports with these exact symptoms. If they are accurate they could provide great insight into the problem. Did you run any of the previous test kernels? Did they exhibit these same symptoms? Does the autobuild do the same thing? This thread provides a kernel to test, but not a full build, what system image, rootfs, etc are you using?
[Touch Pro2, Tilt 2 Android Development] Atmosphere:
My Rhod100 had 2x SODs today.
[Touch Pro2, Tilt 2 Android Development] Quincux:
Battery life is poor with the 3/11 kernel. I can't get solid green light when a turn off the screen.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
you either have gps enabled in settings or you have an app preventing sleep. It is not the kernel causing your problem.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Sleep/ wake all good here on 3/11 kernal :) transition to full on sleep has sped up considerably too!

Have noticed something though when I check the battery stats the radio seems to be using a lot of battery, more so than in previous kernals I tink. More than twice as much as screen (25%) (radio-64%) (system-2%) and loads compared to system. It also says I was 50% of the time without coverage. That seems very unlikely.

I'm not sure wether the in-android statistics are playing up or what. But this means with the RIL fixes hopefully on the way, we could be looking at alot better battery to !:D
[Touch Pro2, Tilt 2 Android Development] Quincux:
I haven't any gps app enabled, only push mail. All others app i launch and close manually.

Sent from Tapatalk
[Touch Pro2, Tilt 2 Android Development] rpierce99:
Notice I didn't say GPS app, I said GPS enabled in settings. Whether an app is running or not GPS is enabled when it's checked in settings.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Something is awry, because others do not have a problem with deep sleep on this kernel.

I've had complaints of reboots to WinMo, which I also have not been able to reproduce.

Haven't talked to WisTilt2 in a few days, hoping to get to talk to him tonight!
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Grab a dmesg log so we can look for wakelocks...

(aaarghhh - you might want to put a link to some instructions on doing so in the original post, they're kinda buried within the thread...)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I guess I could post a link to the FAQ - I added a section for adb last night :p.

Fixed! Hopefully that helps out somewhat.
[Touch Pro2, Tilt 2 Android Development] Quincux:
GPS satellites under Settings-> Location/Security Network is disabled :confused:

I will try it.

After a few days with this kernel under FRX05, i saw that battery meter is a little more accurate than previous WisTilt2's kernel, but battery drain is faster.

I rebooted my Tilt 2 and only i get green led blinking.

Anyway, All other features works great, except WIFI and BT on my Tilt 2 (on WIFI a can connect to a WPA network but without internet conection)