yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] nickleby:
So far everything is working fine for me (camera, wifi, bluetooth, hw3D, sensors, evdo) but I just noticed that cdma sms delivery status is not working as in Froyo. That's the only bug I've found till now.

Edit: I just confirmed that cdma sms delivery status bug seems to be related with my service provider since the New Year, is not XDAndroid related :) But it will be good if someone else can test this.

Thanks to the XDAndroid team, hope to see the final release soon!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well I don't use traditional SMS, I use Google Voice. If it helps any, that's been working flawlessly lol.
[Touch Pro2, Tilt 2 Android Development] intergon:
Hmmm... Wifi is working for me, but now the phone crashed. I think this is due to camera. A minute earlier I opened "Camera" but there was only black screen so I closed it ;) Is that known issue on rhod100?

I noticed that Android can't unmount sdcard while shutting-down.

12-02 02:54:59.530: D/Vold(1267): Volume sdcard state changing 5 (Unmounting) -> 4 (Mounted)
12-02 02:54:59.530: W/MountService(1857): Duplicate state transition (mounted -> mounted)
12-02 02:54:59.560: W/ShutdownThread(1857): Result code -7 from MountService.shutdown
12-02 02:54:59.580: D/MediaScannerService(2014): start scanning volume external
12-02 02:54:59.610: I/MediaUploader(2434): No need to wake up
12-02 02:54:59.640: I/BootReceiver(2237): Got intent with action android.intent.action.MEDIA_MOUNTED
12-02 02:54:59.660: V/MediaProvider(2014): /sdcard volume ID: 997225952
12-02 02:54:59.780: V/MediaProvider(2014): Attached volume: external
12-02 02:54:59.960: D/MediaScanner(2014): found .nomedia, skipping directory
12-02 02:55:00.130: D/MediaScanner(2014): prescan time: 90ms
12-02 02:55:00.130: D/MediaScanner(2014): scan time: 260ms
12-02 02:55:00.130: D/MediaScanner(2014): postscan time: 0ms
12-02 02:55:00.130: D/MediaScanner(2014): total time: 350ms
12-02 02:55:00.140: I/ShutdownThread(1857): Performing low-level shutdown...
12-02 02:55:00.340: I/sysproc(1857): Grim Reaper killing system_server...

Some logs while booting:

12-02 03:09:46.890: E/Sensors(1313): couldn't find 'lightsensor-level' input device
12-02 03:09:46.890: E/Sensors(1313): Couldn't open /dev/lightsensor (No such file or directory)
12-02 03:09:47.830: E/Sensors(1313): couldn't find 'detect' input device
12-02 03:09:47.970: I/SensorService(1313): 3-axis Accelerometer (KXSD9 or BMA150)
12-02 03:09:47.970: I/SensorService(1313): CM3602 Proximity sensor
12-02 03:09:47.970: I/SensorService(1313): Light sensor
12-02 03:09:47.970: D/SensorService(1313): nuSensorService thread starting...
(....)
12-02 03:10:14.110: E/Sensors(1313): Couldn't open /dev/lightsensor (No such file or directory)
12-02 03:10:14.110: E/Sensors(1313): LIGHTSENSOR_IOCTL_ENABLE failed (Bad file number)
12-02 03:10:14.110: E/SensorService(1313): Error activating sensor 4 (Bad file number)

EDIT: Bluetooth works fine I think.. I can transfer file in both ways and pair with other phone
[Touch Pro2, Tilt 2 Android Development] Himalayas:
I am using a RHOD400 and kernel 3.0. No WIFI (show 'error' when I tried to turn it on) and BT. (update: phone status shows WiFi MAC address Unavailable, BT address unavailable)

A noob question: Does the following output look normal? I did not see any *.ko files in the folders. But I did see those when I used the the previous 12/30 bundle (I used the .27 kernel ).

Do I have to manually extract the .ko files to one of the folders to get working WIFI?

Thanks for the great work!

$ ls -al /system/lib/modules

ls -al /system/lib/modules

drwxr-xr-x 2 0 0 1024 Jan 2 16:40 .

drwxr-xr-x 7 0 0 3072 Dec 30 18:41 ..

-rw-r--r-- 1 0 0 0 Dec 30 18:41 .keep

lrwxrwxrwx 1 0 0 12 Jan 2 16:40 3.0.9-g50eb1d1-dirty -> /lib/modules

$ ls -al /lib/modules

ls -al /lib/modules

lrwxrwxrwx 1 0 0 19 Nov 19 15:33 /lib/modules -> /system/lib/modules
[Touch Pro2, Tilt 2 Android Development] detule:
There's currently a problem with the 3.0 auto-build (the kernel and the modules up there don't have the same vermagic). We can get this sorted out as soon as WisTilt2 is back in town.

In the meantime, I started a new thread for these kernels http://xdaforums.com/showthread.php?t=1424495 . This might aid in differentiating issues between the GBX0B and the kernels themselves. In the first post, I point to an alternative 3.0 kernel pack until such time that the auto-build is updated.

I haven't checked but I believe .39 and 3.1 are still built fine on the auto-build.
[Touch Pro2, Tilt 2 Android Development] NeoMatrixJR:
arrrghhh, I switched back to the bundled .27 kernel and added the libGLES myself. (thanks for straitening me out on IRC). What are you seeing in maps? I'm getting blank white spaces where things like interstate symbols should be. (at least that's all i've noticed so far.)

On a mildly related note maps completely crashes my tablet after the last update...so hopefully this is a true issue on many devices and google will fix it soon.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I've had the same experience as MadBeef. Unfortunately not really motivated to investigate it.
[Touch Pro2, Tilt 2 Android Development] detule:
That's unfortunate, try as I might I can't reproduce this on my cdma rhod. The only log i've seen is in this post and I see no crash there.
[Touch Pro2, Tilt 2 Android Development] MadBeef:
Is there anything I can do to help? I'm very comfortable with Linux and used WinMo since before they were phones but relatively new to Android.

It occured to me that, with WinMo ROMs, the RIL has to match the radio. Could the same be true here?
[Touch Pro2, Tilt 2 Android Development] detule:
We've been fairly successful at using a single RIL across multiple devices. In fact, highlandsun pieced together the RIL we are currently using.

More logs are always a good idea. Let's not confuse the issue, just GetLogs output from gbx0b (latest edition from January), on GSM devices, capturing the InCall screen disappearing act on an outgoing call. If it's indeed some sort of a crash, there should be a stack trace or *something* pointing to a culprit.

Does it happen when dialing from the contact screen, or from the call log screen, or when entering the number directly? Does it happen if you turn off dial tones? If it's indeed radio/ril related have you tried changing the network type (there are several gsm options and several cdma options) using *#*#info#*#* ? Is there anything non-generic about your setup - SIP, googlevoice?

Hopefully someone smarter than me can figure out what it is.

Another issue with debugging, is that, the build being signed and all, replacing just Phone.apk is not an option.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Count me in. If I can't get this working, I basically have to throw this phone out; I can't use it in WinMo (WinMo has its own set of issues; performance is awful to the point where I can't even really use it as a smartphone -- the text messaging stuff sucks, I have to reboot it if I want to use Internet Explorer, and Opera isn't really that usable, and if I'm not paying careful attention it'll run its battery down in two hours while it's sitting idle in my pocket) and my wife won't let me use a phone that can't place calls reliably.

So count me in. I've got an Android build environment set up already and all the motivation a hacker could want, just not the Android experience to know what to do next.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Here is you a GetLogs capture: http://pastebin.com/YtvjcNA0

I had it up a long time so you may have to go toward the end, but what happened was I called it from another phone, and by the time it actually started ringing it had already went to voicemail on the other phone. Then I tried to place a call out and hit the call button (from the call history pane this time, but it doesn't matter if I dial the number, go from contacts, or from the log it will do it from any of them.) It sat there forever, I had to force close it once then the call finally went through, but because I had hit it multiple times eventually it caught up and wanted to place another call was I was in the middle of the call. So that is pretty much what happens to me everytime. Hope the logs help.
[Touch Pro2, Tilt 2 Android Development] detule:
I appreciate your continued reports, but I am not even going to bother with this. You quoted my entire message, did you fail to notice that I was asking for:

a. GSM reports

b. People who are on the latest gbx build from January

neither of which includes you.

You have the same device as me -> 400, which I assume is serviced by Sprint. My philosophy in this is if I can't reproduce it on the same device with the same setup -> it must be something on your end. My suggestions to you is to 1) Flash the verizon radio 2) Start with a clean data.img 3) Stop using Juice Defender and whatever Task Killers you have reported using in the past -> in my experience none of these (excepting v6) work well and often cause more issues than they claim to solve. 4) Don't use googlevoice if you don't need to

Edit: Against my better judgement I took a look at your log and just as you placed your call, your auto-task-killer pooped out (perhaps even killed by lowmemorykiller). Get rid of all that crap. Start with a clean data.img and install only what you really can't do without, no silly task killers no stupid widgets/add-ons/groupon/tweeter/gosms/apps that may have a persistent memory footprint.

3-09 18:23:35.780 I/ActivityManager( 1313): Starting: Intent { act=android.intent.action.CALL dat=tel:xxx-xxx-xxxx flg=0x10000000 cmp=com.android.phone/.InCallScreen (has extras) } from pid 1416
03-09 18:23:37.321 E/ActivityManager( 1313): ANR in com.rs.autokiller
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
If it helps: I installed GBX0B a few weeks ago, I don't have an auto task killer installed (I've got V6 as of a couple days ago but the log I posted was before that), and I've got GSM (RHOD210). Running pretty stock, the only thing I think I've changed on my rootfs is updating the wifi firmware.

My experience matches that it doesn't matter if I dial from contacts, call log, or the dial pad.

As for widgets, the only non-trivial widget I have is Plume, and I've got it tuned pretty conservatively. I'll remove it if you think it'll make a difference. I have background sync turned off for all apps. And the only customization I have is that I switched to Zema Launcher a couple days ago on a recommendation from another thread here.

So is there something I can do?
[Touch Pro2, Tilt 2 Android Development] pfc_m_drake:
I'll relate a personal experience:

A few months back I was having a lot of dropped radios, calls that wouldn't go through, texts that wouldn't send, etc. This was in WinMo. I would do a soft reset, boot into WinMo - things would go ok for the first call/text, but then very quickly slip back into dropped radios/no connection/failed texts/etc. Behavior was both in XDA (FRX at the time) and WinMo (I boot back and forth pretty regularly).

I tried re-registering my credentials with my carrier (Rhod 400 on Sprint), but to no avail. Even spent time on the phone with Sprint Tech Support - they did some resetting on their end but it didn't clear up the issues.

I ended up having to do a hard reset in WinMo, and then re-registering credentials with Sprint. That cleared up the problem. Obviously you know the implications of a hard reset, but I wonder if it's worth a shot for you or somebody else similarly affected by this bug???

Just a thought - and I'm just throwing it out as an idea...definitely not dictating that anybody should follow my advice...and of course I take no responsibility for any decisions that you decide to make with your own phone :eek:
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Dude did you see in several places where I am running GBX0B? Yes GBX0B. not FRX07.1, but the latest GBX0B. The only thing I have done with it was put your GPS library in it and fix the wi-fi issue. My wife is the one that runs FRX07.1, and I am hoping that GBX0B can be stable enough to put her on it. I guess you didn't read my posts either. Why would I be in the GBX0B thread if I wasn't running it man?

Second of all before I added any task killers or memory fixers this was happening. Now grant it, those things may be making it worse now, but I highly doubt it considering hyc and others are reporting the same problem. I only added the Memory fixers and task killers after you suggested the android memorykiller was having issues, so I added those apps to see if I could fix it even more. My issues with the phone.apk were happening before putting any kind of apps at all on the build. So don't try to help me that is fine, but at least read my freaking posts instead of assuming stuff you are wrong about. Also have you ever thought that the way you have yours set up (ext4 partitions, etc...) might be the reason you aren't having problems on the same phone I have? So don't tell me you have the same phone and can't reproduce it when you aren't even running it the same way I am to begin with.

Also if I am not installing apps I like to use on my smartphone because it may screw up my phone, I might as well just buy a dumb phone and be done with it. GoSMS is the only fix for sending MMS for sprint because of their stupid issue, and to my knowledge the build or kernel has not been fixed yet to let the standard messaging app for android send and receive MMS's yet. I use DroidWall (which was suggested in the tweak thread on this board) so that only certain apps get access to the data. I have everything turned off from using the data except the stuff I want. I use twitter, facebook, sirius, google music, iheartradio, titanium backup, words with friends, google maps, dropbox, etc.... So if you are telling me that I can't use those apps to get voice working then forget it. I am also telling you you are wrong on that because before that on a clean data.img without only the apps installed in the initial install the phone.apk was acting the same way. So while I appreciate you suggesting it is one of my apps causing it, I have experience that tells me it isn't.

That being said I will be glad to give you a GSM report if you tell me how to give you such a report.
[Touch Pro2, Tilt 2 Android Development] detule:
"Dude", from your log:

[ro.build.display.id]: [full_msm-userdebug 2.3.7 GINGERBREAD eng.bryan.20111230.132558 test-keys]

The time stamp on the build doesn't agree with what you are saying.

Snip your self-righteous nonsense....

I am done.

Perhaps one day you'll know enough to understand that you have no business lashing out even as I was trying to help you out. At any rate, this being a testing thread, ignorance is not an excuse for stupidity.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
If you are talking about he recompiled GBX0B that arrrghhh did, no I didn't upgrade to it because I have Net Loc working and his latest complete build did not have it working, and I just didn't really feel like re-patching everything to be honest. If I use it I will have to repatch NetLoc to get it working, re-patch Wi-Fi hotspot issues which actually requires me to fix the rootfs(unless I can find the fixed one I fixed earlier), and fix the GPS thing again. I just didn't really feel like patching all those things again. Being that everyone else is complaining about the same phone.apk issues including your much beloved hyc who knows a hell of a lot more than you or I put together, I am not sure upgrading to the newer build is going to fix the problem anyway, as it is an old bug that keeps happening regardless of build so far.

As for GSM report? I know what GSM is but I am running CDMA. I have no clue if you mean "GSM report" as something other than GSM versus CDMA or if the GSM means something totally different or not. You have to remember not all of us are up to speed in Android/Linux speak. I try, and I know all things Windows and computer related, but I don't program and I don't know much about Linux except for the occasional patch here and there to fix my phone. So don't get pissy just because I have no clue what you are talking about when you say you want a GSM report.

You know you have very few people left around here that actually care about helping you fix issues with your builds, why be so condescending and belittling? Why run off people that are only trying to help? I will be glad to help you, but for the record, I am not and idiot. I can follow directions (ie obviously I can patch rootfs files, and other things that need to be patched). I am not some idiot on here who can't get haret to run or the build to run. I am simply trying to help you fix a problem with phone.apk that plenty of people are having, not just me. Even Arrrghhh had complained in this thread that the phone.apk is a bag of crap. You are acting like the stupid tech support people that go through scripts that know less than me when I call my cable company about my internet being out(when it is always on their end). I understand that some people are stupid, and need those scripted answers, but I am not one of them.

I will update to his latest build and patch all the stuff that is not in his latest build(netloc, wi-fi tethering, AGPS) and give you another logcat with a new data.img and just the apps that I use. I will give you anything else you need also, but if it some other log that is not a logcat then you are going to have to tell me or point to me a place that tells me what it is and how to do it.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Here is a logcat with the right newest build...detule

http://pastebin.com/bbGzzqhB

I did as I said I would do in my previous post. I will explain exactly what I did and what happened.

Placed an incoming call to my cell phone. It rang 4 times on the other phone before the cell phone woke up and showed the UI. That particular time it rang the ringtone on the cell also once the UI showed up, and the UI allowed me to swipe to answer the phone. That is unusual. Usually it is so delayed it doesn't allow me to swipe until the person has hung up or it has gone to voicemal for them.

I then called my cell phone again, it took about 4 rings again before the UI showed up on the phone, but this time no ringtone and no vibration on the cell phone, just the UI on the screen. I was still able to answer it which is again unusual for my symptoms.

I then attempted to place an outgoing call to the same number I was calling it from previously. So I went to the call log area of the phone.apk and hit the phone icon to call it back. It sat there for about 3 minutes doing nothing. I thought maybe I didn't tap it good enough so I tapped it again, still no response. Finally it started the call. It went through fine. Then after hanging up a 1-2 minutes later it tried to initiate the call again (since I had tapped it the 2nd time thinking I didn't tap it correctly the 1st time). It went through fine, but I was unable to get the phone to hang up even after the phone icon in the notification window disappeared. I had to hit the phone button again go to the dialer and even though the dialer said I was not in a call, I hit the green phone button at the bottom and it disconnected the phone call.

This outgoing thing is very consistent with symptoms I have been having in GBX0B. I was not having outgoing issues with FRX07.1 only the incoming issues. If I had stayed in the first call, eventually the phone would have tried to initiate the 2nd tap I did and make a three-way call out of it mid-call putting the first on hold. So I try not to double tap generally, but I could see how people would do it having to wait 2-3 minutes for the phone to actually place the call might make someone think that they didn't tap correctly the first time and try again causing the double call issue due to the phone.apk not placing an outgoing call in a timely manner.
[Touch Pro2, Tilt 2 Android Development] detule:
Since you seem incapable of revisiting your actions to identify your mistakes let me make the herculean effort of going back one page and quote myself. Perhaps now you'll understand why you had no business getting upset over me pointing out you didn't read my post carefully:

But that's fine people make mistakes, I certainly have when I was posting as a new user on other forums. What truly bothers me is the sense of entitlement oozing from your post. At some point the tables seem to have turned, and instead of lauding people that are volunteering their time and effort to get android working on your device, you are shamelessly asking for recognition for "helping me(us) fix things with my(our) build". As if that somehow entitles you to a special treatment, apparently one that ensures you are not to be reminded to read posts carefully before hitting the "reply" button. That just makes no sense to me. What do you think is in this for me? How do I benefit from identifying where in your logs your task-killer failed, or that there are multiple ANRs (application not responding) in your logcat tied to all the other applications I mentioned in my previous post (gosms, widgets, etc) that could very well be causing your issues?

Oh and before I make the following statement, which I must because it's been fomenting since I read your post, I just want to make it clear that I am in no way associated with the xdandroid project (other than as a user): Feel absolutely free to run off, and stop using xdandroid. Guess what, nobody gives a damn, I certainly don't in my capacity of just another xdandroid user.

No need, I just had a little reality-check. The xdandroid project has a designated team of developers and troubleshooters and they can take care of your problem, not sure what I am doing around here anyways.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Here is the deal, why are you asking for GSM phones only? Most of the people that are having issues are on CDMA. You yourself have a CDMA phone. So why not look at the logcat and see if you see any issue other than my app failing?

I have all normal apps that most people would put on their device, facebook, gosms(only out of a suggestion to get MMS fixed for Sprint since sprint has the bug that has not been fixed in the build to my knowledge, I wouldn't run the program otherwise), the widget is the only widget I have on my phone and it is a weather app that shows a clock also (beautiful widget) many people use the app with no problems, and again the phone issues were happening before I ever installed that widget. I have clocksync running, but by now I would hope you would know why anyone on xdandroid builds would be running that. Google Voice was already in the build to begin with, I didn't install it, and the only thing I can do is uninstall the updates from what android tells me. As for facebook, I would love for it not to load at startup or try to check things every two seconds, but for some reason it does. I really only want it to open and do things when I actually open the program.

Honestly I think it is very unrealistic to expect anyone running android to have no apps installed at all, and you only look and try to help people that have no apps installed at all.

As for calling me a newb on here, as you can see I have more posts than you and I joined before you. Been here before you and probably will be here after you leave given the fact that you are done with xdandroid, or at least that is what your post says above.