yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] fortunz:
There isn't much a setup in play. I ran all the logs I've posted on a brand new data image with just getlogs and xdaledregime installed. I didn't even bother to sign in on it. Since sleep does work on the old build, that should rule out hardware/firmware differences.

So far, I have not been able to replicate my earlier success at getting a green led upon turning the device off with the new build/old kernel. The logs I pulled from that initial test still show wake locks, more of them actually. But since I don't really know how to read the logs, I don't know that the locks weren't somehow resolved. Was it a fluke, or was the device not really sleeping? I don't know. Those logs are attached below.
[Touch Pro2, Tilt 2 Android Development] detule:
I was hoping someone with a CDMA rhod who knows their way around adb, can help me test a lib or two to get aGPS (XTRA) working.

Ping me on #xdandroid.
[Touch Pro2, Tilt 2 Android Development] thenexus:
Issues with Audio Routing

Maybe I did something wrong here... I copied 10 .xls files from my WinMo folder to the card root, and put GBX0B on the card. Boot into Android fine, but BT audio routing does not work at all. Everything else does, but not BT audio.

I'm connecting the device to an Infiniti G35 BT headset protocol in my car. When in a call, I can route audio between the earpiece and the speaker, but when selecting BT I just get speaker audio.

I'd like to be able to graduate from "guy who uses XDAndroid" to "guy who actively helps the testing community." I'm a fairly savvy WinMo and XDAndroid user, as well as a hobbyist programmer and network IT professional. If you can help me walk through the initial troubleshooting steps, I'd love to help make this work.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I said it once, I'll say it again.

BT is not so great. It probably won't ever work well, unless someone actually takes it upon themselves to fix it. I'm surprised it works at all.

Some people said it works great, others have said not at all or very poorly. So I don't know what to make of it, other than BT is just flaky. Good luck.
[Touch Pro2, Tilt 2 Android Development] jonners59:
I agree arrrghh

My BT is working great compared to all the other builds of the past, but on one of my HS has no input audio, Others it works great.

Anyway, not the point of my thread reply.

I had my dreaded no data again yesterday. There were messages in my eMail in box when I started at 6AM, which I read but it would not sync or get network. Kept saying network error. Tried flight mode. Rebooting, etc.. I was not able to get data back until 3PM. The data connected logo was in the top panel and I had excellent signal.

The only similarity to last time is that WiFi was on over night. Also since yesterday I have noticed two changes in the phone. Twice it rebooted by itself, odd because it has not done this before (this build) and it is taking longer to start up and is slower.

Any thoughts...

Otherwise, she is still a dream and proving to be almost perfect - I believe.. Only app I have trouble with is ROK Tv which requires Adobe Player, which of course is unlikely to work
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I guess pull logs? I don't know what to tell you.

There was one other user that had a CDMA/GSM device that he was using in GSM mode, and when he went in a no service area the phone would get 'stuck' in CDMA mode.

I know you have a RHOD100, which is GSM only... So I'm honestly not sure, unless it's hardware. Does this happen in WinMo?
[Touch Pro2, Tilt 2 Android Development] RBraverman:
Android.Process.acore

... is not responding, when I hang up from a call.

I've searched, but only found stuff from years ago.

What info can I hand out to help this?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Every single call?

On a fresh data.img, no apps installed?

Logs please assuming the above is true. Preferably from the fresh data.img, thanks.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Can the log run in the background all the time and only need to access IF or When it happens again. As it is intermittent I do not know when it shall happen again if at all? Sorry, I have not run logs before so before I start exploring and learning I just want to know the scenario.

WinMo - It has not happened before in either mode, but then again I have moved away from WinMo for such a long time now - thanks to you guys I can't really comment.
[Touch Pro2, Tilt 2 Android Development] jazzmoca:
SIM toolkit

How can I install and use SIM toolkit in this build?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I have no idea what that is, but it sounds mildly illegal.

Isn't that something provided by the carrier anyhow?
[Touch Pro2, Tilt 2 Android Development] jazzmoca:
STK allows GSM carriers to load a simple set of menus and 'applications' on your SIM card. Some carriers in Europe send services via SIM card with weather, stock values, menu with special numbers, etc. STK is the only way to comunicate with SIM to use those services. Some Android phones sold by GSM carriers have that app. In image that I uploaded here the icon of SIM STK appears in applications.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This isn't provided by the provider...? We're not your provider.
[Touch Pro2, Tilt 2 Android Development] krekol:
Stumped

I hope somebody can figure out what I am doing wrong. I have a Sprint TP2 running on the AT&T network with XpressDusk Full Dusk ROM. I am not overclocking the phone. I installed FRX07.1 without any problems, installed it into it's own folder, increased the data.img size to almost 2 gig, and been having a ball with it. Only the occasional program crash to speak of (Google Maps). I am not running any dual boot programs, just a short cut to get Android running. I decided to try GBX0B because of it being a newer build. I followed the directions including copying the *.CSV files to the root of the SD card. I have tried three different SD Cards (2, 4 and 8 GB) formatted with the HP format program to Fat 32. This is what happens: I click on Haret with a file manager program. The box with Haret: booting Linux loads. The phone vibrates, goes black and reboots back into windows. I am stumped. I have tried with the Sim card in and out, airplane mode, its own directory, in the root of the SD card, and downloaded a new copy of GBX0B. Every time it does the same thing. I hope somebody can give me some suggestions to help me get this installed. Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Probably your ROM lying about your processor arch. We found a few doing that, very nice trick by the builder (assuming that's what is the case here).

2 things. Try to run HaRET.exe w/o a startup.txt and read what it says in the box. Paste it here.

Second, try taking the HaRET.exe from FRX07.1 and try booting. Should be fine, just stick with the bundled .27 kernel.
[Touch Pro2, Tilt 2 Android Development] krekol:
It said "Found machine Leo".

Well that worked. Fired right up. Looks like you are saying with this method I will not be able to try the newer kernels. I think I can live with that for now. I really like my Windows Rom and don't want to give it up. Thank you for your help.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There's your problem. You certainly do not have a Leo... Your WinMo ROM is trying to lie to WinMo to make it faster? lol. It just causes problems... :rolleyes:.

np. For whatever reason the 'old' HaRET doesn't seem to care, while the new one fails if it's given the wrong input. Oh well, at least you have a workaround.
[Touch Pro2, Tilt 2 Android Development] detule:
Nobody should be living with .27 :) This is what you want.

Rather than deleting modelname.txt as suggested there, try first changing both it and the reg setting to say "T7380". Soft reset, try running the new haret.
[Touch Pro2, Tilt 2 Android Development] krekol:
Thank you very much that did the trick. The ModelName.txt was in the ROM so it took me a minute to figure out how to change it. Changing the Model killed the swype keyboard but I can easily live with that. Time for some new kernels. :)
[Touch Pro2, Tilt 2 Android Development] jonners59:
Oh well. Never got to run those logs. The phone has just thrown a wobbly this afternoon and I am just starting to re-format the card and use a new data image.

After a battery change the phone would boot up as normal, enter the SIM PIN and then it would have a black screen with panel... A message to the effect "system acore is not responding - force quit". Over and over.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nice, I figured there was a file or registry value somewhere that was being changed. Never looked into which one ;).
[Touch Pro2, Tilt 2 Android Development] Steefje:
first of all great work with the build guys. was working with Froyo 7.1

but this looks a lot better and works a lot smoother. accu holds up

for a day so real improvement with the 7.1 that held for a couple of hours

at my place.

but still i got a couple of problems:

1. when i'm receiving a call i'm not seeing any caller id. just a black screen

2. can't get wifi to work (not working with WEP or anything just with a MAC-adress filter)

3. need to press the on and off button a couple of times before the screen light up

4. sometimes apps just quit. and need to reboot the whole phone again before using it

i know it's a testing build. but just wanted to be sure you know of my probs.

thanx again for the build. keep up the great work!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I just installed it, finally. Using 3.0 kernel. First app I installed after bootup was Connectbot from Market; on my rhod210 the Ctrl key is not mapped on the keyboard. Now I gotta remember how to edit the silly keymap files...

Also, the rhod210 default startup.txt file is missing the "boot" line at the end. Why's that?

Called my voicemail, audio playback worked. I haven't tried the mic yet.

This is all installed on my old 1GB SDcard. Going to play with it a bit more before overwriting FRX on my 32GB card.

Camera works, camcorder hangs.

Plugging the USB cable in has locked up the phone on me a few times already.

Most of the text (street names and such) on Google Maps is unreadable/garbled. There are small white squares scattered over the maps (where some other icon should be). Rotating screen orientation garbles the display; same problem we used to have with Gallery3D. Bringing up the Settings menu and dismissing it (forcing a complete screen redraw) seems to clear up some of the graphics mess, but the text may or may not be fixed by that, seems to be 50/50 probability there. Seems like maybe I should install the older Gmaps from my FRX image, mebbe something going wrong with the 3D vector graphic stuff they're trying to do here...
[Touch Pro2, Tilt 2 Android Development] detule:
Yeah known issue. I would've blamed Alex's clocks in 3.0, but I think same happens in .27 with JB's clocks.

I use Google Maps 5.8.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
1. Happens. All the damned time it happened to me - I don't know if it was Phone.apk or what, but the phone waking for an incoming call properly was a rare occurrence... I just got used to calling people back.

2. Wifi works great. Need logs. Might also try on a completely open network to make sure it's not you.

3. Dunno, sounds like a kernel thing. Try a newer kernel?

4. Yup. When the phone gets slow (for any number of reasons) bad things happen...

Finally!! :p

D'oh! Was this fixed in FRX and a regression, or was this something you fixed yourself and never made it in...? They're fairly simple to edit, in ze rootfs.

Really? lol, no clue. I'll fix that tho. Derp.

This is on 3.0? USB/ADB is kinda funny on .27. I didn't test extensively on 3.0... on 3.2 it seemed OK tho.

Yea, detule is also spot on with the Maps thing. Downgrading fixes the issues... I think the G1 folk do the same thing?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I don't remember about the keymap, it may have been one of F22's patches. I remember that he and I discussed it before...
[Touch Pro2, Tilt 2 Android Development] Steefje:
just downloaded the latest kernel from the autobuild site from WisTilt2.

part 1: fixed (it needs to ring for 1/2 times but then you can see the dailer id)

part 2: fixed (no problem at all anymore)

part 3: fixed

part 4: not seen it work yet

so give hail to the new kernel :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, sounds familiar. Sounds like one of his patches that never made it mainline.

He never merged his work, and at one point I started going thru his rootfs to see what was kang/commit-worthy, and never really finished.

He had a lot of nice tweaks that definitely should go mainline. He had some other less-ideal ideas, but hey they can't all be winners :p.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
I'm working on an updated RHOD210 keymap already; when I get it ironed out I'll post it here.

As a brief discussion of mappings, though: I'm mapping the mail button to Search; it seems the most useful thing to put there. But what should I map to the back "mute microphone" button?

I also want to connect alt+, to the symbol pad, and I've seen other ROMs that do this, but I seem to be missing something.
[Touch Pro2, Tilt 2 Android Development] RBraverman:
FWIW, LBE Security was the culprit for me.

Uninstalled and the "... acore ..." problem went way-side.
[Touch Pro2, Tilt 2 Android Development] jonners59:
I just went througfh a complete rebuild again. I have noticed each rebuild has different characteristics. Never the same even if everything is... Odd.

Observations:

I deleted Phone Weaver and Data on Demand from my list of installed apps in AppBrain and my backups (Titanium and Astro File Manager).

After boot installed App Brain from Market along with Titanium and the Titanium Prokey. Then reinstalled from Astro and the last Titanium Back (apps+data ONLY)

Seems to be lovely, all works a treat at the moment except for my previous intermittent probs.

Issues:

Phone does not always ring and there is sometimes no indication that anyone called, or any notification from my service provider that a vMail has been left, yet I have full signal. I find I have missed the call when I access my vMail messages.

Some calls just can not be answered. Phone is just too busy to grab them in time

Sometimes I loose data access even though it shows I have full access - all bars green and 3G or other showing. When I do a Auto sign in to network it says "network error. It then more often than not says signed in to network. When the data is lost there is also no APNs listed in the access points. Only way to get it back is keep rebooting.

Lastly, she often reboots shortly after settling down after starting up.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Which kernel are you using? I've not had problems with data access since I updated to 3.2 (specifically last week's 3.2.2 autobuild) and installed the wifi firmware from the kernel thread, with the exception that it can sometimes take a while to get a data connection after enabling it or when switching away from wifi.

I do reproduce having trouble with phone calls. Most people who call me don't leave VM so I don't know how many calls I've missed, but the dialer will sometimes crash on me immediately after pressing the dial button, kicking me back to the home screen but letting the call progress. The UI gives no indication that I'm on a call but I still have audio going in and out -- with no way to hang up.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
All these reports, and no logs.

If the phone is busy, it's going to be difficult to answer. Welcome to running Android on your 3 year old phone...

The remaining issues seem environmental. No telling without logs. This is still in testing, remember? Post logs if you're going to post complaints. Stack trace or it didn't happen!

:D
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Unfortunately I wasn't able to get logs. Last time it happened I had to reboot (really needed to place a call) before I had the presence of mind to say "oh, I should run GetLogs", and when I went to try to reproduce it later so I could GET logs... well... it didn't crash. Go figure.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ah, wasn't directed at you but yea logs from a reproducible incident are always good.
[Touch Pro2, Tilt 2 Android Development] jonners59:
No, directed at me.

I wasn't complaining at all. As I said I think she is working really well, but it would be nice to fix.

I have not run logs bfore so I'll need to read up on how to and shall post. I did try the app that came with the build but it said somethuing like symtex error and then my phone number. I also do not know where it saves the log to. As I say, I need to do some reading and then get back.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
http://xdandroid.com/wiki/Logs
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I'm getting this almost all the time too. Or something like it - dial, maybe hear a ring, then dialer immediately says "Call Ended". If this happens while I'm dialing voicemail, and I try another call to voicemail, it goes through, and the first one is there as well, on hold.

I guess I need to grab a radio logcat and see if the ril is sending garbage to confuse the Phone app, or if it's just the phone app being broken.
[Touch Pro2, Tilt 2 Android Development] jonners59:
No Radio

OK Today the phone was very flaky with network and finnaly from c11 (9hrs) I have been totally unable to get any connectivity, even when it says that it has registered to a network.

A note: The Settings "flight mode" is different to the on/off switch "flight mode" If either one is seleceted the other does not show the phone to be in the same state, and it only fully engages after a reboot. Also noted that the phone seemed to set up correctly after my SIM PIN was entered and seemed to settle down. It then, after a moment or two went in to the soft restart (xdandroid animation), it is only after that there is no network - I won't say signal as sometimes it shows full bars.

PS: WinMo works fine.

LOGS, before you say anything:

I tried it and as far as I can see it is not producing any - so I know I am doing something wrong.

Using Getlogs: The boxes at the top are all ticked.

I entered

dmesg > /sdcard/dmesg.txt

in the window (as suggested in the link) and selected "add"

Then selected "PasteBin"

I get a message

Syntax error U_REGEX_RULE_SYNTAX near index 1: +44(my mobile number) >

!

At least the radio has just come back, but the battery is almost dead so need to shut her down.

Not sure what to do now.

Found the attached in my build directory in Data and a sub directory for Getlogs.... Is this the log?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No clue what you mean, airplane mode works fine here.

Why the hell did you put dmesg > /sdcard/dmesg.txt in GetLogs!?!? You obviously didn't read that logs link I sent at all - you just skimmed it. C'mon, there's barely a paragraph to read. Read it.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Reproduced it today when trying to place a call. Apologies if there's any excess junk in the logs.

http://pastebin.com/tbhpS2Bh

I haven't actually looked at the log too closely, but the last stuff to happen before getting the logs were an attempted outgoing call that crashed the dialer, and an incoming call that I accidentally rejected.

Edit: >.> I should probably have thought to sanitize the phone numbers. *sigh* Oh well. Too late now.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Are you saying, you have not seen it so have no idea or just being dismissive? It's an observation. If Flight Mode is set via the on/off switch it is not shown as on in Settings. And visa versa. It has been the same for me on 3 phones since Froyo 6 to be complete. It is not important, just feedback.

Ouch. Reading. I commenetd that I had tried the Getlogs before reading up. I tried by adding nothing and just sel;ecting the Bin, etc and got no logs at all, just the error message.

I mentioned I was going to read up and you kindly sent the link. The detail there is short. I read it many times. It is NOT a how to use just background.

It's only guid was - cut and paste:

You can also run these on the phone directly, I recommend doing dmesg > /sdcard/dmesg.txt in order to put the dmesg log to a file on your SD card.

I have also tried without the above, and again I just get the syntex error message.

That said I did connect to my PC and did a scan of the whole card and found a log of sorts in tthe GetLogs Data directory which I attached to my reply. It seems to look much like the ones others have pasted thogh it seems to have a lot of personal data which worrying.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No, I'm saying it works fine here. Like I said before.

It's only guid was... Wow. You should perhaps slow down a bit - or not venture into testing threads if you're not prepared to do a little leg work?

Again, slow down. Don't post logs if you're concerned about the personal info - troll thru the logs and see what is in there that concerns you, and mask it out.

GetLogs does a pretty good job of masking that stuff automatically.

Either way, if you're not willing to post logs to debug problems, then don't post. Seriously. This is xda-developers. This never was, and hopefully never will be, just another support site.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Just to tag a follow-up to my previous post: I'm having similar issues with text messages. The Messaging app itself doesn't crash, but it intermittently reports that the message failed to send -- despite the recipient getting the message just fine. I've got a log of this but no way to upload it at the moment, I'll follow up on it in a few hours.
[Touch Pro2, Tilt 2 Android Development] his1k:
what happen on my HTC TP2 coz no sound just vibrate active
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Did you follow the directions in the first post? There's a pre-install prep section that's pretty freakin important.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Logs enclosed: http://pastebin.com/z8EWcaf4

These were collected when it was working. I'll try and get similar when it is not as a comparison.

A trick I have found to prevent the phone going in to reboot is to put it in to "flight mode" before shuting down, if you have the opportunity. Once booted and settled down, coming out of flight mode seems to prevent the reboot. Sadly not 100% on getting the radio to work.

The issue with getting logs was due to a defective GetLogs app. I found an alternative, more up to date version. Once the old was uninstalled the new installed and after two reboots was able to retrive the logs using the same method I had done the first few times. Shame I was not told I had used the correct method the first time rather than being critisised, it might have saved a lot of time and my anxiety.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sorry I can't read your mind and see what you see. I had no idea that was your problem, and you didn't give us much to go on.

Either way, this is a developer forum - for developers, by developers. So if you're going to post, be prepared to know what you're talking about and perhaps get some thicker skin. This is the internet after all.
[Touch Pro2, Tilt 2 Android Development] ai6908:
Great job arggghhh, everything works fine right now. I had tough time turning on BT with sprint 2.32 radio, but then upgraded to VZW 2.35 and BT works (tested only paring with BT headset for phone).

So far no issues with the ROM, except for MMS. But its not a big issue for me as I dont use MMS much. I will keep running it and see how it feels.

I want to thank you really for getting the BT working on our devices..:D
[Touch Pro2, Tilt 2 Android Development] jonners59:
Logs are not available when the phone has the network problem. Getlogs just crashes mid way. Sorry, so only the logs (as above) from the phone when it is working. Hope it's enough.