yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
GetLogs isn't the only way to pull logs, it's just the easiest :rolleyes:.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Could someone post the default gps.conf?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, for why?

I can try to pull it out, I assume it's in the system image (which again you should have, right?)... Never even bothered to look at this file before.

Edit - attached. I had to add the .txt extension, wouldn't let me upload as a .conf file. So just remove the .txt on the end...
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
You've never messed with gps.conf :confused: That actually surprises me. Anyways, it's in etc and I overwrote my original one a while ago. I'm always tweaking my gps to try to get decent lock speeds and I want to see if the original does any better than what I'm using now.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, if you really think that'll help. I'm betting whatever you can muck with in that file is pure snake oil - without advanced GPS features, mucking with a conf file won't do jack, y'know? Oh well. I attached it above.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
The worst part is, you're probably right. Ah well, hopefully it doesn't actually hurt anything
[Touch Pro2, Tilt 2 Android Development] detule:
The only thing I can see being parsed from gps.conf are xtra related parameters. Unless you are using a customized lib incorporating xtra functionality, mucking with gps.conf is useless imo. If you are using my xtra patched gps lib, changing the parameters might make a difference but not likely for the better.

On a side note, in the current rendition of gbx0b there is a gps related bug. In particular after the following sequence GPS ON (GPS box checked in Settings->Location) -> GPS OFF (GPS box unchecked) -> GPS ON (GPS box unchecked) gps will _not_ work (regardless of what the check mark says). Basically, any time you DISABLE gps in Settings, you will not be able to use gps based location until you restart the device.

This is due to a bug in frameworks/base that has already been patched in the xdandroid gitorious tree. However, this patch only made it recently, after the latest bundled build was compiled.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
If it's been pushed to GIT, I'll rebuild.

As a sidebar, do you think your GPS libs are ready to go in as well? This is still in 'testing' after all ;).

Edit - I also need to sort out how to integrate the CSV's into the build - I'm all ears on that.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
I appreciate the heads up. Generally I shut my phone off every night, and I've been restarting every time I mess with gps.conf. I'm curious that this hasn't been noticed or commented on before (or has it?).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It's the first I've heard of it - but I don't think people used GPS extensively, mainly because it didn't really work well. I know I didn't really use it very much until Detule released his libs.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Well I switched back to the default gps.conf (I've have one more slightly modified one I want to try), and I've never seen that phone lock onto that many satellites that quickly in my life. If the other conf goes well, I'll put it up (or post a link to it as it is on xda).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
With detule's libs, I get ridiculously fast locks. No mucking with gps.conf.
[Touch Pro2, Tilt 2 Android Development] detule:
It's in there thanks to emwe.

The xtra lib is only rhodium-safe, and in its current incarnation will likely blow up on other xdandroid devices (particularly amss5225). Could be made safe across the board but probably not worth the testing effort at this point.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Well, the other gps.conf is working but I can't tell if it's working better or not. Probably just going to switch back to stock for the time being.

Link to modified gps.conf http://xdaforums.com/showpost.php?p=19655131&postcount=16

The only setting that stands out to me is GPS1_CLEANUP_ENABLED=1 which some have said negatively affects their locking, but someone else has said severely cuts his GPS power usage. (=1 is supposed hurt locking but improved power usage). Whether or not any of the extra functions actually work on our build and phones is not something I can determine.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Cool, thanks man.

As for the XTRA lib being RHOD-only - can you isolate it to RHOD, or is there no way...? Sorry for my ignorance here.
[Touch Pro2, Tilt 2 Android Development] detule:
Don't confuse the thread with mysterious gps.conf files. CLEANUP_ENABLED isn't parsed in aosp builds (neither are all other extraneous .conf options).
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
I've been waiting on this since I read about it in the IRC logs. Do you have any files I can test and where to put them? Was hoping the Xtra would fix me having to boot to WM to download GPS data every week.

Your efforts are greatly appreciative. I know many people have left here and the phone for greener pastures, but my wife and I are still using it waiting on either the Galaxy Nexus or Galaxy S3 to drop on Sprint mid-year hopefully. Probably waiting for the quadcore S3 though.

So in the meantime the better I can get the Rhodium to work the better for us. I still got the wife on FRX07.1 due to the phone.apk bugginess on GBX0B that is a lot worse on it compared to FRX07.1. Sadly I am guessing there is not enough developers left to try to look into the problems with this, and my knowledge in linux/android would be no help to program only to test.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Then I will stick to stock. Thanks for the clarification
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
So this isn't just me? That's good to know. Are you experiencing crashes when you try to place outgoing calls?
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Occasionally, but really what usually happens is that I will hit dial (try not to hit it multiple times, as it will eventually try to make the call multiple times putting your call on hold!), it usually goes back to the Home Screen and eventually places the call, most of the time when it seems when I really need to place a call it decides to act like this, but then sometimes it works fine. I find the longer it has been since reboot that the worse it gets.

Incoming calls are worse, I miss probably 8 out of 10 calls coming in because the Phone.apk won't answer the phone before the caller hangs up or it goes to voicemail.

This has been a known issue throughout all builds of XDAndroid to my knowledge, but in FRX07.1 it happens a lot less.
[Touch Pro2, Tilt 2 Android Development] detule:
I posted the lib a while back, and with +40 downloads and few-to-no reports to the contrary, I guess it's working well. The thread specifies CDMA, but the lib *should* work on all rhods - I just don't have the time and resources to chase bugs on gsm rhods.

The bad news: (I am fairly certain) the lib won't work with froyo, and I don't have a froyo build environment set up to build a froyo specific lib.

The phone app crash must be something plaguing gsm devices as it's never happened to me (rhod400) and I've been using gbx for quite some time now. Unfortunately, like you said, developers with the right device in hand to troubleshoot a particular problem are harder and harder to find these days.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Ok I missed that thread because it has been over a years since I visited PPcgeeks. I am CDMA, and Rhod400, and I hardly ever have phone.apk crash on me either in GBX0B, but it is slow making outgoing calls and I miss quite a few incoming calls because it won't start ringing or answer it time. I think that is a totally different problem then the actual apk crashing. You do have the slowness in placing and receiving calls correct?
[Touch Pro2, Tilt 2 Android Development] detule:
No, not really. It does happen once in a while, but whenever i sit down and decide to try and reproduce it (like just now) I get ten-out-of-ten perfect wakes when I call the device. Placing calls I never have any issues whatsoever.

My setup (ext4 partitions/3.2 kernel/verizon radio) is perhaps not bone stock. I always wondered if some of the adjustments we made to lowmemorykiller (making it super aggressive) were to blame for these reported latencies in displaying the InCall screen. Looking at the lowmemorykiller code, it's written rather poorly in some ways -> for example while it's traversing the process list looking for things to kill and free up memory (and it does this in gbx quite often since we have asked for a lot of free ram with the default settings) it holds a tasklist lock which i think prevents the creation and destruction of any new processes. I am not sure what are the mechanics behind displaying the InCall screen and if android tries to create a new process in doing so, but if it does, and lowmemorykiller is traversing at the same time, it could be causing some delays.

You could try changing the lowmemory settings on the fly. For example try

echo "1536,3072,5120,6400,8192" > /sys/module/lowmem*/para*/minfree
echo "0,2,4,7,12" > /sys/module/lowmem*/para*/adj

This should make lowmemorykiller less active than what it is by default. Note however, default settings will be restored upon reboot.

Another issue is the acoustic related dmesg and logcat spam in gbx. I know it's possible to overwhelm some of these buffers to the point where the result is failed wakes, and perhaps we are doing that in some small way with the acoustic debugging messages, though this would not explain why I am not experiencing the issue as acutely as you are. At any rate, given that audio seems to be functioning pretty well, it might be time to calm down some of these messages.
[Touch Pro2, Tilt 2 Android Development] jonners59:
I have now noticed that there are three states in my connectivity problem:

State 1 all is well with green data (3, E and H) and sig strength

State 2 no phone or data, but the panel shows data and sig strength in white. Select automatically via Settings says error and then says registered to network, but it is not and there are no APNs in the Settings -> Access Point Names list

State 3 no phone or data, and in the pannel it only shows signal strength in white. Otherwise all as in state 2.​

Also noted in state 2 or 3 some apps like GetLogs do not work, Airplane mode also

OK, as before, here are the logs when the phone is working well i.e. State 1:

http://pastebin.com/z8EWcaf4

Enclosed are also the logs created when in 2nd state.

I can not create logs for the 3rd state as yet as it has not happened since I have been trying.
[Touch Pro2, Tilt 2 Android Development] detule:
Sure, it can be isolated but the more elegant solution would be to get it working across the board. This would entail in the very least extracting remote_apis_clnt.dll from ams5225 device.

At any rate, the patch-set is large-ish, and I am not sure that there is anyone left maintaining userland with the time to review it.
[Touch Pro2, Tilt 2 Android Development] jonners59:
From POST 365 above:

OK having said that I have not had a state 3 senario, last night I get one, so I ran Getlogs and it captured the state. I am NOT 100% convinced it is the full monty as it was far too easy to restore service and when I ran Select automatically via Settings it immediatly said registered to network, and there were APNs in the Settings -> Access Point Names list - though data had not been restored. One attempt at flight mode and restart, where-as it normally takes many over several hours - hence my reservations that it is a true reflection of a state 3.

Log attached.

I hope it is of interest and use...
[Touch Pro2, Tilt 2 Android Development] hao0907047407:
How to get sound from the old version FRX07.1(2.2.2) to this version(2.3.7). sound of the old version FRX07.1 better than the later version.thanks
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
LOL, that's funny. Good times.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Works great thanks, I like the Leo AGPS App also. Hopefully all should be right and a week from now I won't start getting horrible lock times because the lib and the app doing their job.

A little off topic here, but if I was to attempt to play around with this library and the App in my wife's Froyo build could it be as simple as dropping that lib in the system folder, or do you think the code would have to be changed to get it to work?

I tried this and it just bogged everything on my system down, very sluggish. Don't know what is going on there. I might try again soon, but I have AutoKiller Memory optimizer running now, and it seems to have made the system a little faster, maybe that will help some with the phone.apk issues. I guess the app just does basically what you wanted me to do which is play with the memory settings. I also got JuiceDefender which seems to save a little battery for me by cutting on and off data etc... when not using it.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Getting annoyed finding my phone off in my pocket. Is there anything I can do that will prevent the power off option from being displayed while the phone is locked, or is there a software shortcut I could use if I disable the dialog appearing on long press?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Wait, in your pocket you manage to long press power, and then tap on the screen to turn the phone? That's quite a feat indeed...

I'll poke around, not sure what options are out there. Are you sure the battery isn't just dying? That really does seem difficult to perform in your pocket.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
I've unlocked the phone in my pocket before and started apps. I'm not sure it's turning off, but pressing the power button turns the phone back on. Actually, something just came to mind. Shutting the phone down actually restarts it....I'm not sure what's going on here. If it is the battery, it shouldn't be dying that fast. I posted in the kernel thread asking what I should look for in the logs to make sure my phone is sleeping properly (have pm.sleep_mode=0). So far I haven't had any SOD and the screen wakes up as though the phone is still awake (with =0, =1, =2). But, I've posted all that in the kernel thread so :shrug:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Perhaps the battery isn't OEM? I had a Seidio battery in there for a bit, and it was just slightly smaller than OEM. It would consistently fail to make a good contact, and obviously the phone would just shut off. Happened all the damned time when I would slide the keyboard closed, I thought it was a hardware issue. Well it was, just not the kind of hardware issue I was thinking :p. Make sure the batt is snug...

Other than that, I can't think of anything. I don't know how you're unlocking the phone in your pocket either, that's also quite impressive. As for shutdown causing a reboot, that's not consistent... and at this moment I can't remember all the details, but I think the .35+ kernels behave differently than the .27 kernels in this respect. I haven't played with shutdown/restart in a while tho.
[Touch Pro2, Tilt 2 Android Development] MadBeef:
Just a quick message of support, particularly arrrghhh and detule I see a lot here :) Devs efforts continue to be appreciated :)

Been running this for a couple of weeks now. I really don't think it likes my radio. Texts will sometimes come back as unsent, retrying usually "fails" too. Then I get told I just sent a bunch of the same message haha :rolleyes:

Phone calls also not brilliant, a lot of times, dialing ends up in near-instant failure but the call seems to continue without the phone's knowledge. Then I dial again and sometimes end up with two calls to the same person occuring at the same time. Sometimes it will lose signal for no reason until a reboot. When in a call the quality is good if not a little quiet, but seems to drop calls more than with WinMo. (used CSV's from one of Jackos's latest 6.5.3 ROMs) Oh yeah and battery life is terrible ;) SODs but only every few days. GPS seems to work well but battery only lasts half a walk haha, wifi is great, not really played with bluetooth although it turns on & off fine :) Can't remember the last time I had an app crash on me but half of shutdowns freeze just at the point you would expect poweroff.

Not sure whether I will stick with it or go back to WinMo - the battery life is a killer although my 2 - 3 year old RHOD100 is still on it's original battery ;)

Anyway I will GetLogs if that is useful. Is there much generated as I would be inclined to go through it & remove any personal details before sending. Just adding my support and 2p anyway :) On a GSM RHOD100 UK o/c to 714, 2011-12-30 GBX0B, class 6 microSD, radio 4.49.25.91, linux 3.2.9-gf38316d, updated non-ap wifi firmware & data on ext4.

Keep it up guys :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Just curious, do you have any of these seemingly radio related issues on FRX07.1? I've noticed several people reporting issues that are service/phone call related - jonners, hyc to name a few...
[Touch Pro2, Tilt 2 Android Development] MadBeef:
Don't know, haven't really played with FRX07.1 in any depth. Will do a basic install now and let u know.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Matches my experience.
[Touch Pro2, Tilt 2 Android Development] MadBeef:
Just sent and received a text now, no problems so far. Gonna try a call or two. Wi-fi did seem a little fidgety but everything seems fine so far.

Should have mentioned earlier that once with GBX0B the signal went AWOL, reboot didnt cure it, I had to boot into WinMo, disable then enable airplane mode (I leave it set to enabled so I dont pick up any texts in WinMo) then boot back into GBX0B before I got signal back. Only happened once and cant remember what kernel I was using at the time, sorry.

---------- Post added at 10:55 PM ---------- Previous post was at 10:39 PM ----------

Wow haha ... just tried calling voicemail with FRX07.1

Seems to initiate calls just fine, bringing up the dial pad caused the external speaker to start buzzing like when u leave a phone next to a speaker, other times it would go into a kind of speakerphone mode. Similar thing happens if u press speakerphone.

Just had one text fail on me. Not looking good for FRX07.1 either from here.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Really never had that much problems on FRX07.1 using a Rhod400 other than an occasional missed call because I couldn't answer in time because the UI would not let me or didn't start ringing the phone until 5-6 rings into it on the other end. GBX0B I have all the problems you describe phone call wise.

I have found a solution or work around on the no signal issue. If I boot into android and it never gives me a signal, I usually can't initiate airplane mode it just hangs(won't show the airplane icon), but I hit it anyway, then run an Kexec instead of restarting the phone, and then android pops up in Airplane mode and I can reactivate the radio and it comes up fine, without actually having to boot back into WM.

I noticed when I was in the mountains with low to no signal that after not having a signal for a significant amount of time (more than 10 minutes or so), it will never get back signal, or if it gets back signal data fails no matter what while voice will still work. I can easily fix that by either toggling airplane mode on and off or turning off and back on data. I never mentioned the issue because there are more important things for the remaining programmers to fix than to concentrate on this minor thing which I hardly ever have happen since most of the time I am always in areas with great signal! :-) Was hoping someone would figure out the phone.apk issues to at least get it as good as FRX07.1 was!
[Touch Pro2, Tilt 2 Android Development] nickleby:
That do the trick, thank you! Gingerbread is awesome! Happy New Year! :cool:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm. Well, I guess I have some more work to do on init.

Happy New Year to you!
[Touch Pro2, Tilt 2 Android Development] Schumi_wk:
grabbed a log of the problem i have with the phone crashing after a call.

i hope this helps.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Shoulda used GetLogs :p.

Also, we know the prox sensor is a problem on GSM devices. If detule doesn't whip me up a new kernel soon, I'll just add it to the caveat list.

Edit, looks like he did already. Try me!
[Touch Pro2, Tilt 2 Android Development] NeoMatrixJR:
Did that fix wifi or just get rid of the log junk?
[Touch Pro2, Tilt 2 Android Development] intergon:
Hmm.. this testing thread will help in 'omgb nand' development or is this separate project? I can't wait when the nand version will be forever installed on my rhod ;)
[Touch Pro2, Tilt 2 Android Development] A cool username:
I got the 3.0 Kernel pack, and i'm getting no audio in the back speaker. I double checked that i had the right kernel, and i'v rebooted twice. Still no luck with audio in the back speaker. Any reason for this? Or is this supposed to happen?
[Touch Pro2, Tilt 2 Android Development] fortunz:
I'm pretty happy so far. Set up without a hitch. I'm going completely clean and not restoring anything from my last build, rather installing stuff fresh and I'm probably going to avoid a lot tweaks I used before. Now that I have a tablet, I plan to focus my xdandroid use a lot more and offload the luxuries. No window dressing, no games, nothing I don't need on my phone daily.

I'm already finding increased app compatibility. Groove IP never worked for me on FRX 6 or 7, but it works without a hitch for GBX0B. I've got some more I'm eager to try too.
[Touch Pro2, Tilt 2 Android Development] detule:
Without logs there is literally nothing anyone can do - use GetLogs.

I just booted 3.0 and tested the speaker by both calling voicemail and turning the speaker on, as well as playing ringtones from Settings->Sound. In both cases, the speaker worked flawlessly on my rhod 400.

I am waiting on some feedback from folks on BT in 3.0. If it works as it should (or rather, as well as in .27) we can add it to 3.1 and .39 as well.

As of this afternoon .39, 3.0 and 3.1 should have proximity support for gsm rhodiums. (thanks to ACL)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Wha?!? It just removed the modules. Not sure what you mean by "log junk".

HaRET and NAND have always been completely separate. Sorry for the similar appearing thread titles, I guess I'll change 'em all.

You already can flash it to your phone, so I have no clue why we'd need another thread for the same thing.

This happens only on 3.0? That makes no sense whatsoever. It works on .27? .39?
[Touch Pro2, Tilt 2 Android Development] A cool username:
The sound out of the back speaker hasn't worked for me ever in this new build. Everything i'v tried hasn't made it work (not even the bundle on the first page)

If it makes a difference, I used the rhod300 files from a previous post.

Strange this is, the microphone on the top of the phone works, just the back speaker won't work.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You're mixing your words...

but anyhoo, please pull the CSV files from your WinMo ROM. AFAIK you're literally the only one to report this issue.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Bump. Hopefully everything is fixed... I added detule's .27 kernel with the prox patch for GSM folk, I modded init to rm -rf /lib/modules/* before extracting, and I added the libGLES_qcom.so to the system image. Not sure that will be the last of it tho, I'm having weird artifacts in Google Maps. Neocore ran flawlessly tho...

I think those were the nagging issues. Sorry to make everyone redownload, but a new bundle (same link) will be up shortly... Look for the date/timestamp to change (the filename will not!!) on files.xdandroid.com, thanks.