yashsingh1/xdaforums huggingface dataset:
[HTC Aria General] CrimsonJSRF:
I updated my Aria today and I have two questions

1) Froyo was supposed open up the LED API's right that way it would allow us to change the color through third party apps, how come I still can't do that even after I disable the notifications is settings like the app instructs me to?

2) The Facebook app for android is supposed to have push notifications for android 2.2 and above devices, how come I'm still not receiving these notifications?
[HTC Aria General] tpbklake:
In examining the ROM.zip file in the RUU, the HBOOT loader is now version 1.02. The original Aria HBOOT loader is 0.57. I just found an old post that stated the Gratia had HBOOT 1.01 and I believe that the Asian Arias that have taken the Froyo 2.2 OTA were updated to HBOOT 1.0x. So that my evidence and conclusion.
[HTC Aria General] tpbklake:
OK, I came across this thread post by attn1 on the Asian Aria upgrade thread. On it he thought that it might be possible to run the original Aria RUU with a gold card to restore back to an older version and possible restore your root.

http://xdaforums.com/showpost.php?p=9944299&postcount=9
[HTC Aria General] jeebuz:
Ok. Thanks :) just wanted to know
[HTC Aria General] andrewishcool95:
I tried this and can't get it to work, visionary freezes, and I don't understand how to do the goldcard.
[HTC Aria General] tpbklake:
Google it and then check out this tool. It will really help.

http://xdaforums.com/showthread.php?t=970157
[HTC Aria General] NBA Brawler:
Any different links yet? HTC site has been slow since the update was posted
[Fascinate General] neh4pres:
I flashed supermarket for dj05 to my phone, and I love the theme. However it seems to make my swype go into a force close loop when I boot.. and swype can not be used.. any sugestions?

Rocking dj05 and jt's voodoo 5
[Fascinate General] nitroglycerine33:
Did the theme flash a different version of swype or a themed version of sywpe? You could grab a version of swype and replace the apk in the system/app folder and reboot to see if if fixed your issue. Someone might have packaged up a zip to flash through clockwork that might install as well. There is a thread here to install swype:

http://xdaforums.com/showthread.php?t=867831
[Fascinate General] neh4pres:
Yes. It was supposed to be moded version of swipe .. ill try this fix when I get home

Rocking dj05 and jt's voodoo 5
[Fascinate General] neh4pres:
okay.. tried to get the swype beta.. deleted the swype app and lib.so.. and the bata says overwriting file them does not install..??

i cant find any links to a decent way to just get swype back on my phone..

irc channel seems to have changed or is down.

feeling liike smashing this thing..

ideas??
[Fascinate General] neh4pres:
ok.. so i just went through hell getting this back working.. i got the black glass themed swype and lib from another page and pushed both to respective areas in system via root explorer.

i then used eoe app installer to install the blackglass apk.

however i dont believe this is a current swype for the dj05 rom im running..

anyone have a link to the most up to date stock file? please.. and thanks in advance
[Fascinate General] neh4pres:
ok. so never mind.. its still broke.. it seems to not have a librarry. and wont let me pick a language..

ohh i hope someone with vast knowledge has the answer that will let my fingers slide gracefully across my glass screen once again
[Fascinate General] neh4pres:
Anyone?. Please

Rocking dj05 and jt's voodoo 5
[Fascinate General] nitsuj17:
just reflash your rom...and if you want the theme w/o swype...use 7zip to open the theme, and delete swype.apk from system/app...close and flash it
[Fascinate General] neh4pres:
Ok.. ill try this soon.. thanks for the response.

Rocking dj05 and jt's voodoo 5
[Fascinate General] neh4pres:
If I wipe, will I have to odin the radio again?

Rocking dj05 and jt's voodoo 5
[Atrix 4G Q&A, Help & Troubleshooting] billwoo:
Man....I swear this thing seemed louder when I first got it. Anyone else having issues with sound not being loud enough when listening to media files? All volume controls are at max.
[EVO 4G Q&A, Help & Troubleshooting] jc8081:
Is it possible to do? Specific on go launcher? Thanks

Edit: or another app that does the weather animation when unlocking...
[Captivate General] scuba_d:
Just saw on samfirmware twitter that the galaxy s i9000 is supposed to be getting an official samsung update to 2.3, hope one or some of the devs can jump on this and hook up the cappy owners with a working rom.
[Captivate General] Phoenix-Lead:
Well if this is true I will be playing with it a bit. I just checked it and it is not out yet.
[Captivate General] scuba_d:
no they said march, so hopefully soon.
[Captivate General] goob1284:
Ya go get'em!
[Captivate General] ryude:
Only good thing about 2.3 is google made ext4 a requirement. Rfs can no longer be used.
[Captivate General] Phoenix-Lead:
I smell a debbie downer!!
[Captivate General] scuba_d:
I can picture the badass roms already. wish I was more fluent in android dev. I would certainly be cutting up the base rom in a heart beat.
[Captivate General] rajendra82:
They never said what year though :)
[Captivate General] scuba_d:
yeah but this isn't an att and samsung update, this one is for the galaxy s i9000 in europe. they are usually on time with those
[Captivate General] NhocCuteGirls:
Originally Posted by scuba_d

Just saw on samfirmware twitter that the galaxy s i9000 is supposed to be getting an official samsung update to 2.3, hope one or some of the devs can jump on this and hook up the cappy owners with a working rom.

Well if this is true I will be playing with it a bit. I just checked it and it is not out yet.

__________________

| Icon Remover 1.4 | Form Pilot Office 3.0 | Quick Timer 2.2 | ezCheckPersonal Check Printing Software 2.0.4 | Christmas Gift - iPhone Backup Pack 5.0.0.0
[Captivate General] davwman:
^^^^^^ WTF!^^^^^^
[Captivate General] whiteguypl:
Made me laugh.
[Captivate General] Phoenix-Lead:
I am glad I could make you laugh. I just lengthened your life
[Captivate General] TRusselo:
wheres 2.4 candycane?
[Captivate General] rajendra82:
Like Froyo on all carriers by September?
[Captivate General] shaolin95:
Give me an OCed 2.3 and you will prolong my life too! :D
[Captivate General] jcabibi:
You are the biggest DBag on the forum!
[Captivate General] jbcap43:
Bahahaha!

Candy Cane? Let's get 2.3 up and running first!
[Captivate General] bames:
i think you missed his point.

they handle the update direct for their european devices without the carrier having to test, approve, add bloat, etc. so they generally meet their deadlines.

The i9000 has had froyo for quite a while now.
[Captivate General] scuba_d:
thank you, yes this was my point precisely
[Captivate General] ballz0iron:
a. 2.4 is going to be called gingerbread, and is going to, for the most part, set it up so phones can use the same apps that are written for 3.0 on tablets.

b. you are a douche. go away.
[Captivate General] Kaik541:
incorrect. what the update for 2.3 said was they have now switched over from straight yaffs2 to ext4 for optimization. every manufacturer can do whatever the hell they want with the software.

in 2.2, yaffs2 was the defacto, yet the G2/Desire Z had a /system partition mounted as ext3. CyanogenMod chose to transfer over to ext4 as well, I think, because it actually is an improvement. Samsung can continue to put RFS all over the place if they so see fit. The Nexus S is a mish mash combination of ext4 and yaffs2
[Captivate General] bay_wolf:
... ... Isn't 2.3 gingerbread? I don't think calling him out on the wrong name then putting another wrong name is very nice. 2.4 is named Ice Cream and is suppose to be a bridge between Gingerbread and Honeycomb.
[Captivate General] zelendel:
A simple search would have lead you to one of the many threads that has already been talking about this. I hope we see a port as well sense I am sure at first that is all we will see. The captivate got its update lol.
[Desire HD Q&A, Help & Troubleshooting] kamranh3:
I've made two backups on ClockworkMod, yet EVERY time I try to reinstall data, it restarts midway, and when I start my phone up the bootanimation becomes an flashing android logo, what am I doing wrong? Please help! :(
[Desire HD Q&A, Help & Troubleshooting] lilil:
Hmm..that's a strange problem.

Did you try to reinstall the CWM??

Edit: I pushed the Thanks Button unfortunately -.-
[Desire HD Q&A, Help & Troubleshooting] kamranh3:
Every little helps ;)

And I've tried, no such luck, so I'll try an older version and see what happens

EDIT: There's a thanks back!
[Desire HD Q&A, Help & Troubleshooting] kamranh3:
Okay I've tried a different recovery, no luck :(

What have I done wrong? I seem unable to make any recovery. :(

I think the problem may have originated when I installed CWM 3.0.0.5, everything was fine before that
[Desire HD Q&A, Help & Troubleshooting] preacher65:
This is just a long shot, but have you tried checking your SD card for errors from your PC? The backup file could be corrupted, and that might fix it.

It would probably be a good idea to copy the /clockworkmod/backup folder from your SD card to your PC before you run the check. If it doesn't help or makes matters worse, you can copy it back.

Also, which version of CWM did you use to make the backup?
[Desire HD Q&A, Help & Troubleshooting] kamranh3:
I used 2.5.1.3 in both cases, went down to 2.5.1.2 to see if it was linked to the recovery itself, it wasn't
[Desire HD Q&A, Help & Troubleshooting] preacher65:
If you look in the /clockworkmod/backups folder on your card, in the folder for the relevant backups, what size is the data.img file? Have you got any earlier working backups you can compare it to? I'm wondering if the backup failed part way through. :(

I take it you're trying to restore data only using Advanced Restore?

I can't think what else could cause it apart from a damaged sd card or corrupt file, but I'm not a CWM expert.
[Desire HD Q&A, Help & Troubleshooting] kamranh3:
I have looked at the backup is around 1.11GB which is the expected file size, the data.img being around 730mb, it's done this twice, and I've always checked that I've had plenty of space before attempting nandroid, and nothing's ever happened to the sd, i've never moved it or anything
[Desire HD Q&A, Help & Troubleshooting] preacher65:
I'm not sure what else to suggest besides checking the sd card for errors. There have been some bugs with the HTC 1.72 stock ROM, which affect all custom ROMs based on it, that occasionally cause sd card errors. This is most likely to happen if you connect to your PC with a USB cable, mount the SD card as a drive in your PC, and disconnect the cable without using "eject" in Windows. It might happen at other times as well, I'm not certain.

This is usually fixed by checking the card for errors through your PC. Some people recommend defrag'ing the card, but I think a check for errors should be all that's needed. I'd copy all contents of the card to a folder on your PC first, just so you have a backup.

Otherwise I've run out of ideas, sorry. :( Hope you get it working.
[Desire HD Q&A, Help & Troubleshooting] kamranh3:
What I'll do is transfer my backup to my brother's SD card, and then attempting a nandroid then, if that doesn't work then I don't know what will, but I'm 99% sure it's probably due to a problem on my SD card.
[Desire HD Q&A, Help & Troubleshooting] preacher65:
Hope it works, let us know how you get on.
[Desire HD Q&A, Help & Troubleshooting] kamranh3:
Well it doesn't seem like option, brother's too stubborn, so I guess I'll have to stick with what I got for now until I can fix this problem, it's really bugging me :(
[Desire HD Q&A, Help & Troubleshooting] preacher65:
:( You didn't say whether you tried checking the card for errors from your PC, did you try that yet?
[Desire HD Q&A, Help & Troubleshooting] bur2000:
CWM created an MD5 checksum for the backup, so it's not very probable r/w errors are the cause of the problem. If the data was corrupted CWM would notice before attempting to restore the data.

But if in doubt you can verify the checksums manually. In the backup directory there's a file called nandroid.md5 it's a text file that contains the hashes for each backup file. Compare those values to the actual checksums. If you need a tool use Hash My Files.

CWM 3 backups aren't backward compatible with CWM 2? Then you could try restoring with CWM 2 and see if that works. Then you'd at least know if it's you phone or a software problem.
[Desire HD Q&A, Help & Troubleshooting] equlizer:
This may sound silly but did you upgrade clockwork to 3.0.0.6?
[Desire HD Q&A, Help & Troubleshooting] kamranh3:
I tried upgrading to see if it would solve the issue, it didn't.

And as for md5 checksums, it all checks out fine, everything starts to restore fine, and on two of the latest occasions it will not fully restore data, but will restart CWM between restoring. I really don't know what the cause is :/
[Touch Pro2, Tilt 2 Android Development] Entropy512:
I've been working on fixing the GPS data validity bug (where positions are reported at a lat/long of approximately 0,0 prior to lock)

Attached is a version of libhardware_legacy.so that should do the following:

Improve debugging of GPS operation (change printf()s in the main GPS library file to Android logging macros)

Fix/workaround the 0,0 bug (I say workaround because I have yet to identify the root cause of the issue - however it is "fixed" from the point of view of an end user

A few "under the hood" cleanups/fixes

Things that are NOT implemented/fixed in this library:

XTRA (driver/library support for QuickGPS data loading)

Obtaining satellite status prior to GPS lock on Rhodiums (behavior on non-Rhodium unknown, but this should not change actual behavior at all except for the false 0,0 fixes)

Any methods for improved lock speed - all this does is prevent you from appearing south of Africa prior to lock

To test this fix (Intended for FRX05, may work with other 2.2.2 based builds that are derived from xdandroid FRX05):

Unzip the attached zip file

Place libhardware_legacy.so somewhere on your SD card. For organization, I use bindfiles/system/lib/libhardware_legacy.so

Open conf/froyo.user.conf in your favorite text editor

Within the custom_shells{} section of froyo.user.conf, add:

mount --bind /sdcard/bindfiles/system/lib/libhardware_legacy.so /system/lib/libhardware_legacy.so

Restart, and at this point:

1) 0,0 false locks should go away

2) You'll see lots of new GPS debugging info in ADB logcats

Edit: For testing, I usually use the "GPS Status and Toolbox" app from the market, since Google Maps does not show sat status.

With the stock GPS libraries, GPS Status and Toolbox will immediately report a 0,0 fix on startup

With this library, you should see that funky "wait for it circle" in the lower status area until you are locked. As mentioned above - you will not see satellite signal strength reports prior to lock
[Touch Pro2, Tilt 2 Android Development] manekineko:
I was just looking at setting up the kernel build environment myself the other day.

The main useful reference I found was this:

http://forum.ppcgeeks.com/tp2-andro...modules-tinboot-nand-boot-more-beginners.html

However, that one's a bit of a firehose, too, since it deals with a lot of stuff specific to NAND.

In short clone these two repositories into the same directory:

git clone git://android.git.kernel.org/platform/prebuilt.git
git clone git://gitorious.org/linux-on-qualcomm-s-msm/linux-msm.git

The first is the vanilla kernel, and the second is the XDAndroid kernel modifications. You'll need the first to compile.

From that guide, compile:

cd android
mkdir modules
cd linux-msm
make clean
make ARCH=arm htc_msm_android_defconfig
make ARCH=arm CROSS_COMPILE=~/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- INSTALL_MOD_PATH=~/android/modules zImage modules modules_install

Follow that guide for putting together the modules for wifi and the location of your compiled files.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Thanks! I will take a look at that, although I get the impression from reading through things that that GPS handling is at a layer somewhere above the kernel but below where we start having to deal with Java. I just can't quite figure out where since I have never done any Android development before.

I am probably going to poke at the kernel at some point though to try and fix the LED behaviors. It is clear from the "sleep of death fix" test kernels that there is knowledge of how to change these behaviors - at the very least I want to make it turn things *off* when in deep powersave. (Seems nonsensical to me to indicate that the device is in a deep power save mode by turning on a bright power-burning LED, although maybe the LED consumption is negligible even when the device is asleep.)
[Touch Pro2, Tilt 2 Android Development] manekineko:
Whoops, didn't read carefully enough at where you'd narrowed the problem down to. I haven't gotten around to setting up an environment for the system build yet, sorry I couldn't be more of a help!
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Yup, http://gitorious.org/xdandroid/hardware_libhardware_legacy/blobs/master/gps/gps_msm7k.c is my first target. There may also be issues in gps-rpc.c
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
http://xdandroid.com/wiki/Getting_the_Source goes thru how to build the system image. It starts with getting the source and cascades all the way thru building a system image.

I'm setup to build it as well, and I've always wondered how we could fix this problem... Love to see it squashed!
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Thanks! I'll start working on that, although probably not until after the weekend is over at this point.

The ghetto approach as an interim fix would be to not set GPS_LOCATION_HAS_LAT_LONG if both are exactly zero - This is not the right way to do it, but the chances of it affecting anyone before a proper validity condition is identified are slim. (Even if you ARE near lat/long of 0/0, there will be enough noise in the GPS solution that you'll almost never actually be blanked).

Probably should assume that all of the other validity flags should not be set if we don't have a position fix. (Assumption: The MSM7k GPS does not take inputs from the magnetometer or accelerometer, if the Rhodium even has a magnetometer, didn't think it did.)

Of course, I haven't quite figured out how GPS_LOCATION_HAS_LAT_LONG and such roll up to higher levels. There's some odd interactions in terms of when SV status becomes available, for example.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Yup, definitely no magnetometer in the Rhodium.

Good luck with this, it'll be a nice little fix if you can get GPS to stop reporting locks before it has one.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Source downloaded, have a build going. (First an unchanged one...)

I'm working on a Froyo tree for the moment, since I think in the Gingerbread alphas GPS is simply "not working", although the degree of "not working" was not defined. Once I'm more familiar with the GPS handling code I might take a look at how it works for Gingerbread.

A few notes about the Froyo repo in its current state:

The URL for Google Apps that device/xdandroid/msm/unzip-files.sh is outdated. cyanogen-mirror.local.host.name does not exist any more. android.local.host.name does but doesn't have the HDPI Froyo apps. I forget which mirror I used - the list is in the CyanogenMod wiki if you search for gapps

The froyo build scripts direct you to http://source.android.com/download - URL no longer exists, it is http://source.android.com/source/download.html now

The process for installing Sun Java 5 on Ubuntu 10.10 is in the URL above - you need it to do a froyo build.

Also, the wiki instructions are missing lib32readline5-dev as an Ubuntu package that needs to be installed (it's in the source.android.com docs tho) - I'll try to update the wiki later.
[Touch Pro2, Tilt 2 Android Development] bzo:
Entropy512, glad to see someone is interested in looking at the GPS code. I helped phh with it in the last go around to get the RPC messaging part working working, but nothing has been done since.

The NMEA parsing stuff you see in the current gps lib is unused, all the data comes from RPC. Before getting the data directly from RPC was working, we took advantage of the fact that NMEA is output to smd27 and parsed that string data. In any case, once the GPS is brought up, that NMEA data is still viewable by catting /dev/smd27.

If you want to check out other similar code, look at the vogue gps code. I think it supposed to work pretty well, and the RPC behind it is similar. Theirs is a bit different in that they split the gps processing across the kernel and userland, where ours is all userland.

Ultimately, this stuff needs a bit of a rewrite, because the libhardware_legacy interface to GPS that the current lib is written to, is gone for Gingerbread. If we could just get the RPC stubs generated, we might be able to plug into the reference Qualcomm implementation and take advantage of that well sorted code. Check out the cyanogenmod libhardware gps to see what that looks like.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Thanks for the additional pointers bzo.

I'm at the stage where I managed to build the froyo tree, but have not yet had a chance to test the built system ext2 image. That's a goal for tomorrow.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
OK, dumb question - Since I'm now trying to understand that RPC code - Where do all those printfs in gps-rpc.c print to?

edit: Never mind, figured it out - it's buried in the logcat... Was trying to go back in time using Android System Info, but adb logcat lets me view it as it happens.

edit 2: Nope, those are D() statements in gps_msm7k.c - don't know where the printf()s in gps-rpc.c are going - nowhere? Should these be D() statements???
[Touch Pro2, Tilt 2 Android Development] bzo:
those printfs were from when that code was a console test application. Not surprising that they wouldn't show up by default in the logcat. I'm sure there is some way to make them show up. Dunno off hand, but some googling on android debug logging and redirection of stdout and such may dig up that info.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Ah. That makes sense why they aren't D() statements like in gps_msm7k.c

I tried changing as many of the printf()s to D() macros as I could, I'll test it tonight.

Edit: Had a chance to test it this morning. No output from any of the printf()s that I changed to D()s. Either I did something wrong, or none of those code paths are hit in a no-signal/low-signal situation prior to lock. Doing a make clean followed by a rebuild to make sure. :)
[Touch Pro2, Tilt 2 Android Development] bzo:
Those debug statements don't display by default. You'll have to change some compile and/or android settings to have them show up.

btw, if you're not already doing this, building just the gps lib and doing a mount --bind with just the lib in your startup.txt is a big timesaver, as opposed to updating the entire build
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Hmm, got any pointers in this regard? They are working for gps_msm7k.c, but not my changes to gps-rpc.c - these are built by the same Makefile and components of the same library as far as I can tell. Is there a log tag filter somewhere?

Thanks for the mount --bind tip - will try that on my next build attempt.
[Touch Pro2, Tilt 2 Android Development] bzo:
if you copied over the same #define for D(...) from gps_msm7k.c, it seems like it should work the same in the other file. I haven't looked that much into android logging though.