yashsingh1/xdaforums huggingface dataset:
[HTC Aria Android Development] Troggie:
I let it set for about 4 hours before tinkering again.. I get the same error just toggling the GPS on and off.

I/GPSButton( 343): ToggleState

I/GPSButton( 343): Update State

D/libgps ( 162): qct_gps_stop

V/libgps ( 162): DeferredActionThread pthread_cond_wait returned

V/libgps ( 162): DeferredActionThread calling send_end_session

V/libgps ( 162): PD command:

V/libgps ( 162): RPC_PDSM_PD_CMD_END_SESSION

I/GPSButton( 343): ToggleState

I/GPSButton( 343): Update State

D/libgps ( 162): qct_gps_set_position_mode = 1, fix_frequency = 1

D/libgps ( 162): qct_gps_start

V/libgps ( 162): DeferredActionThread pthread_cond_wait returned

V/libgps ( 162): DeferredActionThread calling send_get_position

V/libgps ( 162): PD command:

V/libgps ( 162): RPC_PDSM_PD_CMD_GET_POS

E/libgps ( 162): PD error: 17 command:

E/libgps ( 162): RPC_PDSM_PD_CMD_GET_POS

V/libgps ( 162): DeferredActionThread pthread_cond_wait returned

D/dalvikvm( 2053): GC_CONCURRENT freed 491K, 53% free 2915K/6087K, external 948K/1038K, paused 4ms+7ms

W/KeyCharacterMap( 2053): No keyboard for id 131074

W/KeyCharacterMap( 2053): Using default keymap: /system/usr/keychars/qwerty.kcm.bin

I/System.out( 394): [INFO:17875103]: LogSource: Running flush

I/System.out( 394): [INFO:17875141]: LogSource: Sending payload [bytes=988]

D/dalvikvm( 394): GC_CONCURRENT freed 490K, 47% free 3740K/6983K, external 884K/1038K, paused 6ms+6ms

I/System.out( 394): [INFO:17875741]: LogSource: Response [http=200,length=249]

I/System.out( 394): [INFO:17875743]: LogSource: Read id 2, status code 200

I/System.out( 394): [INFO:17875800]: LogSource: Read id 1, status code 200

W/LocationMasfClient( 394): uploadCollectionReport(): no ReplyElement

here is the logcat from the same phone with the CM6.1.1 for comparison purposes.

http://pastebin.com/Wib2KGmB
[HTC Aria Android Development] jeebuz:
Menu > Settings > Call Settings > scroll down for Additional Settings. Input your phone number there. Note, this goes away if you do a reboot; for some reason it can't read your SIMcard (someone correct me if I'm wrong) and thus does not recognize your phone number and your voicemail number.

jlayton15 (just giving some credit (: ) gave me a tip to use QuickPic from the Market. Free, simple, and gets the job done.

If you're using ADW, hit Menu > Edit. It should bring you to a scrollable panel of the screens you have "active". Each screen should have an "X" on it so you can delete screens as needed.

For LauncherPro, go into LauncherPro's settings and go to Homescreen Settings.

Thanks!
[HTC Aria Android Development] attn1:
Again, I am suspecting a data connection issue when supplemental data for AGPS is requested.

Try deleting maps data from setting > applications > manage applications

then delete & reinstall maps

then reboot, & start NAV from within MAPS after using maps to get directions.

I know it's a long way around, but if it works we can look into why.
[HTC Aria Android Development] j.fignole:
Maybe its the 1300 photos on my SD card but the 3d gallery is having a hard time developing thumbnails for the albums/pics. I'm on Nightly #7. On sense it could load them up pretty quick.

Oh and for the record book attn1 and cm... holy crap. You guys never cease to amaze me. These nightlys are showing the middle finger to att in a way I wish I could.
[HTC Aria Android Development] gdeadfan:
Thank you much for the replies, guys. Quickpic is awesome, I decreased to 3 homescreens, and I have my contact picture showing up in messaging. I just installed HandCent SMS and that allowed me to set my contact picture. I think I like handcent better anyways..
[HTC Aria Android Development] sd73ta:
Hate to quote myself but anyone???
[HTC Aria Android Development] Troggie:
Ok this is what I had to do to get GPS working..

I had to go into File Manager then Android/data and I had to delete the folder called com.google.android.apps.maps

this was after a clean install of CM7 nightly 7 without installing Maps yet.

I then installed GPS Status and had a lock within about 30 seconds. After installing Google Maps again I was able to get the navigation portion working just fine.

I couldn't just go to Settings > applications > Manage Applications because I hadn't installed Google Maps yet.

I will say that I did try GPS Status before deleting the com.google.android.apps.maps and it still would not lock on so there must have been something in there causing issues.
[HTC Aria Android Development] Nutshell69:
I refreshed completely (build 7) - didnt install MAPS at all - so its not on my system.

installed maps (version 5.0.0 )

rebooted - turned on GPS - started MAPS - started NAV to get directions....

....:(

only shows 'Searching for GPS'

I have Strong Wifi connectivity and strong 3G

anything else I can try out?

my logcat : http://pastebin.com/FaSBtxRD
[HTC Aria Android Development] drowningchild:
Delete the cache under sdcard/android/Com.cooliris....
[HTC Aria Android Development] mosamjc:
No

#repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
#cd <your workspace directory>
#repo sync

Grab coffee and wait. No clone necessary to just build.

http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Liberty
[HTC Aria Android Development] boxcar8028:
went to sleep with battery life at 70% 7hrs later the alarm on my phone goes off and battery life is at 69% ......amazing..... cm7 n76 :)
[HTC Aria Android Development] DanGeorges:
Which kernal and cpu governor setting are you using to achieve this?
[HTC Aria Android Development] DroidRunner:
I'm rather curious too. My phone on airplane mode doesn't even do that
[HTC Aria Android Development] Darius_bd:
So this happens to all android phones out there using the Smartass governor? Why no sound as there been of this before?
[HTC Aria Android Development] cHarley04:
I suppose your guess would be as good as mine.

I can venture a guess, that most people don't have or run apps that create a significant CPU load when the phone is "Screen Off" with Smartass, and the (relative) handful of people here running experimental kernels/governors, make up a miniscule portion of the "typical" Android user running the stock OS/Kernel.

Based on many of the posts I've seen lately, there are more people concerned about which way the arrow points when trying to use their phone as a GPS receiver, than those truly evaluating the phones overall performance through a range of task scenarios.

I don't have all the answers. I've certainly asked a lot of questions regarding this issue as I experience it, and posted what data I have come up with that I think may be relative to the problem.

I've seen a number of people on here ***** about the fact that CM BT phones all have the same BT MAC address and that it's causing problems when they and their spouse both have phones with the same address. But, I've never seen anyone here, offer up a report on their CM7 phone running Smartass while streaming over BT during Screen Off mode.

Drowningchild was kind enough to link the smartass kernel source, and based on the obvious comments in the source code, it seems to me that anyone having a fundamental knowledge of computer engineering, would grasp the concept that you can't blindly throttle a loaded CPU without having a negative result.

Is a mediaplayer the only android app out there, that has the potential to run in the background, screen off, and keep the CPU loaded to the point that causes a crash when Smartass shifts into Screen Off mode and chokes the CPU clock? Given the size of the Market, I doubt it. I suspect that it's just a matter a time, if Smartass makes it way to the general audience, that similar reports will surface.

I'm still waiting for someone else here to replicate the BT streaming senario with Smartass to confirm what I'm seeing, or to explain how you can allow a governor to intentionally "choke" a loaded CPU, and not expect that to cause a problem???

This really isn't rocket science....... ;)

EDIT: Don't take me wrong, I'm loving CM7 and am very grateful for all of the efforts put forth by the Dev's here. :)
[HTC Aria Android Development] boxcar8028:
Yeah, this was the first time I have ever got such good battery life. In the past 7hrs of sleep would be around 5-8%. This was right after flashing cm7 n76 with no kernel flash just the stock cm7 n76 build. My settings are: ondemand 245-768 with quadrant benchmark results 966

I flash n76 let aria rest for about 1-2 hrs and reboot. Then I'll use the phone to make calls maybe surf the web and check my email and then repair the permission and reboot. thats it. I hope this is the new norm. love this rom, thanks guys the devs are awesome :)

btw: Im getting the same results on my nook color with cm7 n69
[HTC Aria Android Development] DanGeorges:
I'm trying this tonight.

Thank you for the information!
[HTC Aria Android Development] Moh_Jay:
CPU on conservative Max 806 min 245 with screen off on demand Max and min 245. Minimal use at school (7 hours) and battery only goes down 1 -3% on build 75.

Signatures are fancy.
[HTC Aria Android Development] ibussa:
Does this Rom has a chance of get flash lite?
[HTC Aria Android Development] bkmo:
Hey OP you need to change the title of this thread to "kernel testing and cpu settings" Wait nevermind, there is a kernel thread. ;)
[HTC Aria Android Development] brswattt:
Im' getting 11/11 sat fixes but It takes a long time to get a lock.
[HTC Aria Android Development] cHarley04:
Yea, sorry. I don't know how we wound up with this discussion here, this should have been in drowningchilds Kernel Thread.

:o
[HTC Aria Android Development] bkmo:
I was just breaking balls. :) But yeah keeping it in one place is a good idea.
[HTC Aria Android Development] ARMarlowe:
77 is up, testing out battery tonight -> tomorrow, will report
[HTC Aria Android Development] DroidRunner:
I'm going to try this tonight. I committed myself to 2.2.2, but this peaked my interest. I had to set the CPU to 806, im super anal about scrolling speeds.
[HTC Aria Android Development] CallMeAria:
Can I get a couple people to test something for me:

Menu>Settings>Wireless & Networks>Tethering & portable hotspots: select the 'usb tethering' checkbox.

I'm getting a reboot everytime and just want to see if anyone else is getting this and what nightly you're running so I can see if it's a rom issue or something else. Thanks.

Sent from my cm7 Aria.
[HTC Aria Android Development] Darius_bd:
You're not alone there, pal. Wish everything could be buttersoft as iPhone. There, I said it.
[HTC Aria Android Development] dandrumheller:
Yep - I got a reboot. CM7.0.3 Drowning 7-5 kernel.
[HTC Aria Android Development] hi2u2:
GPS is working wonderfully, and the GPS icon status bar bug has been fixed it seems.

Several issues though:

1) As of nightly 70, the screen is blank if booted while charging. I have to toggle the power button to get the display to show up. I think this might be related to the offmode charging commit (http://review.cyanogenmod.com/#change,4727). Wondering what that commit does, as CWM screen still appears if phone is turned off and plugged in.

2) This issue: http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority

Seems this is a cross-device issue. If you experience it and it annoys you, please click the link and star it!
[HTC Aria Android Development] hi2u2:
No reboot. On nightly #78, stock kernel. There was a commit in nightly 75 by attn1 that fixes USB tethering. You could try that.
[HTC Aria Android Development] drowningchild:
issue with my kernel as i didnt add that commit
[HTC Aria Android Development] drowningchild:
also htc marvel(wildfire s) source released

2.6.35 soon? :P
[HTC Aria Android Development] Noobla_Khan:
No reboot on nightly 77. Stock kernel.
[HTC Aria Android Development] boxcar8028:
hey, you guys should try this. its a great little mod. I have it running on my aria and my nook color with ADW and I'm loving it :)

http://xdaforums.com/showthread.php?t=1040668
[HTC Aria Android Development] cHarley04:
+1 on this simple mod. Everything launcher related is now fast and smooth.
[HTC Aria Android Development] Jimmeh83:
What's the difference between this and the "keep in memory" option in launcher pro, besides the fact that it will work for any launcher?
[HTC Aria Android Development] artiemon:
Apps icon on main dock

I accidentally deleted the Apps icon from the middle of my dock and can't figure out how to get it back. The All Apps selection is no longer on the Menu button. I'm running CM7 N76. Any one out there know how to get the icon back?

**EDIT**

I figured it out. Created launcher icon on home screen and then dropped on dock.
[HTC Aria Android Development] DroidRunner:
I always thought it was the same thing.
[HTC Aria Android Development] cHarley04:
Been there, done that.

Locking your desktop will help prevent it. Menu > Lock Desktop ;)
[HTC Aria Android Development] bkmo:
Or even the cyanogenmod performance setting of "lock home in memory". It is all basically the same thing in my book. Well almost...two of the options have checkboxes.
[HTC Aria Android Development] boxcar8028:
I'm no dev, but I think cm7 "lock home in memory" is just for the apps not the launcher. as for launcher pro, not sure I'm using ADW.
[HTC Aria Android Development] bkmo:
No it is to lock the "home" app or "launcher" as you call it in memory to avoid reloads.
[HTC Aria Android Development] cease:
USB Tethering

Works fine, running CM7-Nightly 77.
[HTC Aria Android Development] hungmung:
Has anybody else lost the back light on the buttons at the bottom of the screen in n77 & n78?

Sent from my Liberty
[HTC Aria Android Development] Noobla_Khan:
Heh...missed that one. No back lights on nightly 77 for me.
[HTC Aria Android Development] sd73ta:
Yup me too

Sent from my Intruder running CM7
[HTC Aria Android Development] CallMeAria:
The check box attempts to lock the home in memory when other apps are opened. Attempts being the key word. Android will still kill the launcher as it sees fit to keep memory spread out. I've been using the check boxes for a long time and they work for the most part. But the mod in the link ensures that the launcher can not be killed, period. Other apps will FC as a result of low memory instead of android just killing the launcher. This isn't a problem with the aria as it's got enough memory to prevent the FC issues. No lag from sleep, no redraws ever (except of course if you manually kill your launcher).

Sent from my cm7 Aria.
[HTC Aria Android Development] retired_mnbooze:
Hadn't noticed until tonight, but yes.
[HTC Aria Android Development] cHarley04:
Now that you mention it, yep. On nightly77.
[HTC Aria Android Development] martiantakeover:
I'm not a fan of the lit buttons myself. I prefer them off.
[HTC Aria Android Development] plumberchuck:
Originally Posted by hungmung View Post

Has anybody else lost the back light on the buttons at the bottom of the screen in n77 & n78?

Sent from my Liberty

Mine are working just fine
[HTC Aria Android Development] drowningchild:
My buttons are hit & miss when I wake the device
[HTC Aria Android Development] CallMeAria:
i noticed they come back on when I adjust the screen brightness.
[HTC Aria Android Development] martiantakeover:
Those lights just drain more battery.
[HTC Aria Android Development] drowningchild:
cant see them when its dark :(

and they shouldnt drain that much
[HTC Aria Android Development] juggalofr33k:
Haha.. i came here to post the same thing. My bottom lights are also hit and miss when I wake it...
[HTC Aria Android Development] cease:
Lights working fine

On Nightly 78, lights working fine on wake up.
[HTC Aria Android Development] bkmo:
There is a revert to a prior commit waiting approval that will revert what they broke. It was a commit to disable light sensor when not being used.
[HTC Aria Android Development] ladios:
Probably the commit that enables slide-open/close, not the one disable light sensor. I'll kang two rom to test, and then report to gerrit.
[HTC Aria Android Development] bkmo:
Look at the gerrit light sensor comments. It broke button lights on Wildfire and another device too.
[HTC Aria Android Development] ladios:
A clean install of a kang rom without reverting any of those commits, which is almost identical to n78, doesn't have the button lights issue... :confused:

EDIT: After nandroid restored and installed the rom over it, the lights did stay off. But, by toggling auto-backlight on and off, issue's fixed until next reboot.
[HTC Aria Android Development] ladios:
Another kang that reverted this commit shows me you are right.

EDIT: It's just reverted in gerrit by someone else. Next nightly (n80?) should be fine.
[HTC Aria Android Development] mtnlion:
81 up!
[HTC Aria Android Development] brivette007:
On 79 with built in kernal. Phone was fully charged. After 5 minutes of 3g web browsing, the battery dropped to 79. Ouch.
[HTC Aria Android Development] lilhaiti:
Just installed 81...and the buttons light up as normal.

Everything else is smooth as butter.
[HTC Aria Android Development] hungmung:
Same here back to normal button lights again

Sent from my Liberty
[HTC Aria Android Development] Noobla_Khan:
Same here on the buttons.

81 is looking good initially. Gotta test GPS and battery.
[HTC Aria Android Development] juggalofr33k:
Battery on n81 sucks, but gps locked in 13 seconds with only 4 satellites. Bottom lights are fixed too...
[HTC Aria Android Development] Divino:
Wait some days.

I uploaded 12 days ago and I used it a lot (wi-fi, gprs, web, sync, gps...) and is still charged at 22%, much like previous versions.
[HTC Aria Android Development] cHarley04:
Just curious how "uploaded" 12 days ago, what was just released yesterday?
[HTC Aria Android Development] lilhaiti:
I can attest that the battery life in n81 is a little worse than n76. I will give it some time to settle in first, then report back.
[HTC Aria Android Development] DroidRunner:
The fact he has 22% battery after 12 days bogus
[HTC Aria Android Development] hungmung:
I think done of you guys are reading too much into his broken english.

Sent from my Liberty
[HTC Aria Android Development] kabell4:
I think what he meant was to give it a few days. I posted a while back that it normally takes a couple of days for the stats to adjust. Especially if you don't flash when the battery is at 100%.
[HTC Aria Android Development] Darius_bd:
That's the fun part!
[HTC Aria Android Development] Divino:
LOL, 22% after 12 hours OBVIOUSLY!

(sorry, I'm italian ad my english is like... ...mmmmm... ...I can't say it in english)

;-)

82 is up.
[HTC Aria Android Development] Noobla_Khan:
My battery life on 81 seems on par with 79. Only lost 8% sitting overnight.
[HTC Aria Android Development] mtnlion:
82 shows support for kineto! Wifi calling will definitely be a plus.
[HTC Aria Android Development] wdavis0911:
Where can we post bugs we find?
[HTC Aria Android Development] powerchess:
here.

A bug i found, (maybe a bug) I cant get Ad free fix to work with 82.
[HTC Aria Android Development] s0be:
Requires userspace libs and an updated ganet kernel module. I have put together an update.zip with the libraries (stolen from HD/Leo, might not work for us), and am about to fling together a kernel with ganet.
[HTC Aria Android Development] kabell4:
OK, so I gave n81 two days and the battery drain was pretty bad. I switched back to n76 today. Anyone else have issues with 81? Is n82 any better?

Thanks!
[HTC Aria Android Development] Noobla_Khan:
I didn't really have any change in battery life from 79 to 81 to 82. Not the best for battery life but I wouldn't call it horrible.
[HTC Aria Android Development] bkmo:
No noticeable change for me either. I have 60% left today after 12 hours of use. N81
[HTC Aria Android Development] kabell4:
Perhaps I'll try it again. Just seemed to be much worse than 76. I also normally use ladios' kernel, but have been trying stock for the last couple of nightlies.
[HTC Aria Android Development] drowningchild:
how would wifi calling even work?
[HTC Aria Android Development] hi2u2:
Nightly 83:

Alarm clock application force closes when trying to change the alarm time. I pushed DeskClock.apk from 82 and it is fixed.
[HTC Aria Android Development] s0be:
I'm not completely familiar with the technical details of it, and it will probably only work with certain carriers, but my understanding is that the gannet driver and userspace libraries create a fake network over a tunnel to the carrier. It's a product from kineto (I know T-Mobile supports it). It creates another interface similar to the rmnet driver.

I didn't have time to put together the Kernel update.zip yet, but if you can whip one together (identical to whatever you have been making, only with the gannet.ko module installing to /system/lib/modules/), I could test some time today.
[HTC Aria Android Development] juggalofr33k:
N83 force closes when trying to mount as usb...had to mount in recovery.
[HTC Aria Android Development] ladios:
The module is gan-eth.ko which can be found in Espresso device repo. Also, you can check its commit history to see how Cyanogen enables it.
[HTC Aria Android Development] powerchess:
Am I the only one with problems with ad-free? On 82.
[HTC Aria Android Development] thomas_t:
BackLight N83

Using N83 and see the backlight goes out when starting the image gallery and watch a video taken by the cellphone. Try it out. Start a video and the backlight goes out.
[HTC Aria Android Development] Noobla_Khan:
Heh...I think I'll pass on 83.
[HTC Aria Android Development] juggalofr33k:
That didn't happen on mine...
[HTC Aria Android Development] Moh_Jay:
Backlight goes out while watching a video from the camera still on 85. Anyone getting force close when trying to mount SD?

Signatures are fancy.
[HTC Aria Android Development] hi2u2:
I only notice the lights on the buttons going out when watching vids, but not the backlight for the screen itself.

And no FC here when mounting SD--you do mean as USB storage right?
[HTC Aria Android Development] Moh_Jay:
Yea that's what I meant the lights of the buttons and I do mean the storage (haven't had time to test it).

Signatures are fancy.
[HTC Aria Android Development] cHarley04:
Post 2709 above reports the same.
[HTC Aria Android Development] Noobla_Khan:
Build 86:

Gallery app not causing any issues for me with back lighting or anything else.

Recorded a video and watched it, the only thing I noticed was the lights on the soft keys go out when playing the video. Don't see how this would be an issue though.

In settings I unmounted and re-mounted the SD card without any issues.

No force closes of any kind yet.

Need to beat on it more, just put it in a couple of hours ago but everything seems find.
[HTC Aria Android Development] juggalofr33k:
N86 the only problem I've found is gmail isn't syncing right. As far as recent emails go, my most recent sent email is dated 10/1/2010. I Send email all the time, So that's not right. I think I saw something about new gapps being added?
[HTC Aria Android Development] lilhaiti:
I install n86 over n81. Everything seems to be fine but one thing. On n81, I had the new talk app installed, after installing n86 it looks like I now have the old talk app again. I see they updated the get-google-apps to 5-01 why not 5-03 which has the new talk app?

Edit: Nevermind...I just read the paragraphs at the bottom of http://goo-inside.me/gapps/ it explains everything.
[HTC Aria Android Development] juggalofr33k:
And playing videos from file manager launches rom manager instead of the video player...I fixed permissions and wiped cache and dalvik...I dunno...
[HTC Aria Android Development] DroidRunner:
Try clearing some defaults with both programs
[HTC Aria Android Development] juggalofr33k:
Tried that too. I'm really at a loss...
[HTC Aria Android Development] Moh_Jay:
No backlight for soft buttons on build 88 but that's about it.

EDIT: Backlights on soft buttons now show up.

Signatures are fancy.
[HTC Aria Android Development] jdwhite87:
I have backlights on soft buttons... I also have permissions management and what appears to be widget locker widgets surviving reboots!