yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] jmorton10:
There is no box for NY, that is the problem.

~John
[HTC Rezound] jbh00jh:
Click the edit button and you should see your location and New York.

Sent from my HTC

LTE 4G Rezound
[HTC Rezound] jmorton10:
When I click the edit button, there is only my location listed there.

New York is not shown there at all.

~John
[HTC Rezound] kgbeezr1:
Are you in or near New York? It seems that by default it picks up your current location (from Google location services) as slot 1. Try starting over by clearing the data in the "weather" app from the main applications menu (main settings>applications>manage applications>all) and then add your city in the widget settings (click and hold, then drag the widget to the lower left of the screen) and then choose the city that you just entered on the first page that says "select a city" at the top. It should always display that choice by default on the home screen. The integration isn't perfect between the widget and the weather app.
[HTC Rezound] jmorton10:
OMG, what a buggy POS this widget is!!

I finally thought I had it working, it was showing my current location all day today in various locations and New York was completely gone.

Now, I just swapped batteries and when it restarted New York was back and I can't get my current location (which is a 7 hour drive away from NY) to show.

I loaded LauncherPro Plus in the phone today, and using that (which really flies) I can use Weather and Toggle Widgets. The Weather and Toggle flip clock/weather looks identical to the HTC version and with that the weather works perfectly. The only problem is, the clock/weather is slightly smaller than the HTC version because of the high def screen so I would really rather use the HTC version.

~John
[HTC Rezound] jmorton10:
I just tried this again. I added my home city, then dragged the widget to the lower left. That gave me a select city screen with two choices. The first one was "current location" and the second was "New York". I clicked on current location then done, but the stupid widget still says New York.

I even did a factory reset today trying to fix it and even that didn't work.

I guess I'm giving up on the POS at this point.

~John
[HTC Rezound] nev310:
Mine usually says can't find data or something untill I open it.

Sent from my HTC Rezound
[HTC Rezound] kgbeezr1:
Add your city in the widget. Drag to the lower left "edit", then on that screen where you see "current location" and "new york" click "add" in the upper right corner. Add your city there in the widget edit screen, not the weather app, then select it on that same screen after it's added. Sorry, works fine for me. I even tried clearing app data and re-adding different cities a couple times to be sure, can't understand why you're having the issue. Also, to use the "current location" option, make sure Google location services are enabled. I use current location mostly and it follows me accurately from city to city. Hope you can get it worked out...
[Thunderbolt Q&A, Help & Troubleshooting] bcrichbich36:
Hello friends,

Anytime I switch between apps while music is playing, the sound "hiccups" for a split second. It happens with headphones in and through the speaker. I'm currently running liquid 3.1 with the newest imoseyon aosp kernel. .906 radio. Happens no matter what app is playing the music. I've never had a problem like this so I don't know where to start hahah
[Android General] silver03wrx:
hey guys please sign that petition. Htc's ceo lied and said no more locked bootloaders back in may well the vivid has a locked bootloader. Lets please support our android brothers http://www.groubal.com/htc-vivid-has-locked-bootloader-contrary-to-statements-by-the-company/#sign
[Android General] silver03wrx:
In may there ceo said none of there devices would have locked bootloaders anymore. Htc is saying att did it and they lock all of there phones bootloaders. Which obviously is not true ours is not. And no samsung phones are. And att is saying htc did it. The rogers version the radar is exactly the same as the vivid and it can be unlocked on htcdev.com yet not the vivid
[Android General] hawkeyefile:
The best support is with money, don't buy from HTC if they lock their devices down. Companies rarely take advice from petitions.
[Android General] thatBilly:
Link doesn't work.
[LG Thrill 4G] keith134:
This will get you adb up and running 100%

http://www.youtube.com/watch?v=b1qgKA_eT2g

have to give thanks to AndroidHax0r's
[Nook Touch Android Development] LastSilmaril:
I did some more digging around and it seems like wpa_supplicant and dhcpcd in /system/bin/ also have slightly different binaries in 1.1.0. But when I replaced them with the binaries from 1.0.0 (but using the 1.1.0 tiwlan_drv.ko), it didn't work, and DHCP still doesn't complete successfully. I have no reason to believe that using the older driver would magically fix anything - doesn't this sound like some configuration issue somewhere?

The thing is, I'm not quite sure where these configuration files or dbs would be. I dug around a bit more and found that wpa_supplicant refers to the wpa_supplicant.conf in /data/misc/wifi (the one in /system/etc/wifi doesn't seem to ever get updated). But this has no bearing on what goes on with dhcpcd, and I haven't been able to find out what, if anything, controls it :(

Any takers?
[Nook Touch Android Development] LastSilmaril:
Also, the reason I thought that it still worked was that the static configuration that WiFi Static makes for you is not deleted by default when WiFi Static is uninstalled. To shut off static ip, the settings table at

/data/data/com.android.providers.system/databases/settings.db
​

has to be modified so that the entry with name "wifi_use_static_ip" should have a it's value="0", not "1".
[Nook Touch Android Development] domi.nos:
Probably it will not help, but in my experience Nook couldn't connect when my router (Siemens SLI 5300) has secured with WPA-AES key. Then i've made some experiments and i found out that using WPA2-AES key it works without any problems. 1.1 firmware of course.
[Nook Touch Android Development] ros87:
"Connect" and "obtaining IP address" is two different things.

I did some digging trough the sources today but couldn't find anything obvious in regards to the dhcp issue.

As this seem to be quite a common issue I'm a little surprised that B&N hasn't released some sort of fix yet.

With that said, I've only experienced this once, and that was with 1.0.1 :D
[Nook Touch Android Development] LastSilmaril:
There is also the following in /init.rc. But shouldn't that only get run once?

service wlan_loader /system/bin/tiwlan_loader \

-f /system/etc/wifi/firmware.bin \

-i /system/etc/wifi/tiwlan.ini \

-e /rom/devconf/WiFiBackupCalibration

disabled

oneshot

service ifcfg_ti /system/bin/ifconfig tiwlan0 up

disabled

oneshot

service wpa_supplicant /system/bin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf -dd

socket wpa_tiwlan0 dgram 660 wifi wifi

disabled

oneshot

service dhcpcd /system/bin/dhcpcd -ABKL -d tiwlan0

disabled

oneshot

# TI WLAN Soft AP related services and configuration

service wlan_ap_loader /system/bin/tiap_loader \

-f /system/etc/wifi/softap/firmware_ap.bin \

-i /system/etc/wifi/softap/tiwlan_ap.ini

disabled

oneshot

service udhcpd /system/bin/udhcpd /system/etc/udhcpd/udhcpdWlan.conf

disabled

oneshot

service hostapd /system/bin/hostapd -dd /data/misc/wifi/hostapd.conf

disabled

oneshot

service keystore /system/bin/keystore /data/misc/keystore

user keystore

group keystore

socket keystore stream 666
​

I haven't got an earlier version of init.rc to compare this to.

Is there any way to specify that dhcpcd let DHCP_DISCOVER actions take longer? I thought it was supposed to take 60 seconds by default, so it is being configured otherwise elsewhere. But where??? Right now it sort of gives up right away.

-e
[Nook Touch Android Development] ros87:
Well, we don't have the sources for the kernel module, nor the binaries, so I was just looking at the kernel stuff.

My guess is that it is some miniscule thing somewhere, but not in kernel nor the configs as far as I can see.
[Nook Touch Android Development] LastSilmaril:
Well if it's not in the kernel that's good right? And by kernel, do you mean the kernel itself or the driver?

I found a manpage for dhcpcd; the following switches are being passed to dhcpcd in init.rc:

http://roy.marples.name/cgi-bin/man-cgi?dhcpcd

-A, --noarp

Don't request or claim the address by ARP. This also disables

IPv4LL.

-B, --nobackground

Don't run in the background when we acquire a lease. This is

mainly useful for running under the control of another process,

such as a debugger or a network manager.

-K, --nolink

Don't receive link messages for carrier status. You should only

have to use this with buggy device drivers or running dhcpcd

through a network manager.

-L, --noipv4ll

Don't use IPv4LL (aka APIPA, aka Bonjour, aka ZeroConf).

So as the lack of much standalone configuration files for dhcpcd has already hinted, uh, this doesn't seem to be a dhcpcd config issue.

I'm not sure how to be able to write to init.rc (so I can add "-t 30" to see if that'll do anything). I don't know what partition it's on but cannot just write it back to root (read-only filesystem). Setting system to writable makes no difference, so we can assume it's not hiding on there somewhere. There is a copy of it at /data/local/tmp/init.rc but just modifying that does nothing; /init.rc is not a symlink to /data/local/tmp/init.rc.
[Nook Touch Android Development] LastSilmaril:
This thing might be helpful, but is a bit over my head.

http://blog.linuxconsulting.ro/2010/04/porting-wifi-drivers-to-android.html
[Nook Touch Android Development] LastSilmaril:
LOL, I've been pushing and pulling things without giving a second thought to proper permissions. Can somebody please run ls -l on the following files and post what the proper permissions are supposed to be? I haven't run into issues yet, but I don't want to muck things up.

/system/etc/wifi/tiwlan0-drv.ko
/system/bin/wpa_supplicant
/system/bin/dhcpcd
/system/etc/dhcpcd/dhcpcd-run-hooks
[Nook Touch Android Development] LastSilmaril:
really? I'm surprised more people here aren't completely up in arms about this issue, which is a matter of basic usability. I've even come across someone with an e2000 with dd-wrt with issues, so it's not just old routers/crippled ISP routers that this is happening to. BN is completely unresponsive, so it's up to us!
[Nook Touch Android Development] LastSilmaril:
Correct permissions (per my backup) are:

1. /system/bin/dhcpcd

755, root.shell

2. /system/bin/wpa_supplicant

755, root.shell

3. /system/etc/wifi/tiwlan_drv.ko

644, root.root

4. /system/etc/dhcpcd/dhcpcd-run-hooks

550, dhcp.shell

Also, the diffing I did that led me to think that wpa_supplicant and dhcpcd had changed may not have been accurate, since it may be that the Linux Reader extracting program I was using mucks with the files. When I compare the file sizes of wpa_supplicant and dhcpcd between my 1.0.0 and 1.1.0 backups, I found no difference. The difference is there between the WiFi drivers though - that's something that's definitely changed. But simply dropping it in *still* does not work. It's maddening...
[Nook Touch Android Development] ros87:
I don't think this is a problem for that many users of the NST, you might find 20 - 30 reports on the net, maybe a hundred if you really go at it, but that still is just a fraction of the NST owners. So don't expect to see much interest in this topic I'm afraid.

Now, the tiwlan drivers are not unique to the NST, they are part of the omap3 platform and maintained by TI and you might want to look for similar problems there and even updated sources (if the tiwlan module is at fault at all).
[Nook Touch Android Development] LastSilmaril:
That's exactly the problem Roger - I'm not sure how it is they are at fault if dumping in the old 1.0.0 driver does not help matters...but I can't seem to find anything else that's changed! In the meantime I mucked things up poking around, and decided to go back to stock 1.1.0 and am now re-rooting.

In the meantime though, I'm not sure where exactly to poke around; do you know what version of OMAP3 is in the nook?

(BTW- does anybody know a way around the 'sideloaded books on sdcard do not persist in shelves' problem? Happens in all firmwares, stock or rooted...)

-e
[Nook Touch Android Development] LastSilmaril:
...how do we 'decompile' (meh...) stuff in android?
[Nook Touch Android Development] LastSilmaril:
I have discovered apktool.

Poking around framework.jar under smali/android/net/wifi, there are several changes in there in comparison to the framework from 1.0.

1) BnIpConfig.smali and friends are not in 1.0 (at least not in android/net/wifi)

2) WifiStateTracker$DhcpHandler.smali is 3KB bigger in 1.1.

and many more...

Could this finally be it? I'm tempted to simply dump the android/net/wifi folder in from 1.0 and see what happens (love being fully backed up).

Also, /system/lib/libnetutils.so has changed.

I'm a little bit uneasy messing with this, but I've got backup upon backup now, including several CWM backups, so I'm gonna press on!
[Nook Touch Android Development] LastSilmaril:
I think I may have finally figured it out, after some further testing. Nothing to do with patching framework.jar. But, last time I thought it worked, status would change to 'Disconnected' for no apparent reason after a few minutes. If I'm still connected to WiFi in two hours, I'll post a solution and instructions.
[Nook Touch Android Development] LastSilmaril:
EDIT: ...Yup, it's definitely disconnecting at some point. I'm not sure if this is normal behavior or what, but somehow I doubt it.
[Nook Touch Android Development] LastSilmaril:
OK, quick update...

1) First, it seems that the only file with any relevance (and this makes sense) is libnetutils.so. The older binaries of dhcpcd and wpa_supplicant are not necessary to get the dhcp to complete.

2)WiFi intermittently switching to 'disconnected' is because of a failure to associate with the AP - not anything to do with dhcp. Why it has to associate again - what causes the 'Disconnect event' - I do not know. But as my wpa_supplicant when this was happening was from 1.0 (and the failure to associate was unambiguously reported by wpa_supplicant), I decided to push back the stock 1.1 wpa_supplicant. Let's see if anything changes as a result. If so, then this whole masturbatory thread will have turned out to be about one measly file :)
[Nook Touch Android Development] LastSilmaril:
Anybody having this issue should see the first post in this thread and try the solution I posted there. Seems to be working for me...

http://xdaforums.com/showpost.php?p=19897624&postcount=1

What the offending code is within that file, I don't know. However, it should have been obvious from the beginning that that's where to look:

http://www.netmite.com/android/mydroid/system/core/libnetutils/
[Nook Touch Android Development] copieux:
Thank you for the advice; I replaced the 3 files with the v1.01, reboot, changed permissions and it work flawlessly so far.

whoever wrote that the wifi problem is a non-issue is wrong. I know 6 nook st users personnaly and they all have the same problem with 1.1 upgrade.

I haven't tested it long enough to see if it disconnect, but so far it is perfect.
[Nook Touch Android Development] LastSilmaril:
Great! I'm glad to get some independent confirmation.

I just realized that I didn't attach the original file to the post above; it can now be found there.

Eh WAIT, hold on, only libnetutils.so should be replaced. Replacing the others, particularly wpa_supplicant, may cause problems.
[Nook Touch Android Development] copieux:
ok, but did I misunderstood this quote in the first post:

"Replacing /system/bin/dhcpcd, /system/bin/wpa_supplicant, and /system/lib/libnetutils.so with their 1.0 versions - and you need all three, and you need to make sure to use the correct permissions after pushing - gets dhcp to 'work' again! In other words, without any additional configuration whatsoever!"

Anyway, I did a backup of the 3 files, so should anything go wrong, I'll replace wpa_supplicant with the original file and I'll keep you informed.

Thanks again for finding this fix. I would probably have gone back to 1.01 without this thread.
[Nook Touch Android Development] LastSilmaril:
Right: that was the wrong information, but I don't know how to write a strikethrough so I kept it. But I think I'll go ahead and delete it now, because it's causing confusion...
[Nook Touch Android Development] GabrialDestruir:
I found when I was having issues like this it was caused by Filter WAN NAT Redirection being enabled, as soon as I disabled Filter WAN NAT Redirection I could receive my IP from DHCP just fine, so this might be something to look at first if you're having issues and are running something like dd-wrt on your router (or if your router has this option)
[Nook Touch Android Development] LastSilmaril:
Thanks for the clue Gabrial. That's better than assigning a 'static' ip via dhcp but doesn't really help for hotspots. And frankly I'm not sure if the Verizon ActionTec router has the setting you're referring to. At the end this is something BN needs to fix; it really is unacceptable for a consumer electronics device that, uh, needs the Internet in order to be fully functional (to access the BN store at the very least)
[Desire Q&A, Help & Troubleshooting] spamrijk:
Hi,

Technical information:

HTC Desire

Android version 2.2

Baseband version 32.49.0032U_5.1105.27

Kernel version 2.6.32.15-gf5a401c htc-kernel@and18-2 #1

Build number 2.29.405.5 cl293415 release-keys

Software number: 2.29.405.5

Browser version Webkit 3.1

(USB-disconnected)

Today I started trying to flash a new ROM (my first attempt ever) on my HTC Desire, using this xdadevelopers guide: http://xdaforums.com/showthread.php?t=814381

The first 2 parts (the rooting with UnrEVOked) went fine. But in part 3, step 3) the trouble starts.

In this step you'll be told how to backup your current ROM via Nandroid.

I followed the instructions and eventually started the backup process, which gives the following onscreen output:

ClockworkMod Recovery v2.5.0.7

SD Card space free: 7647MB

Backing up boot...

Backing up recovery...

"an continuously changing line"

But every time it tries to backup libopencore_download.so (@ ~45% backup progress) it comes to a standstill and doesn't continue. I can only aboard this process by removing the battery.

So I started looking for a fix on the forum and WWW, but every suggested fix for similar problems hasn't worked for me.

I tried:

- Formatting my SD card (Because at an normal start up, the SD-card was in read-only mode. Formatting fixed this problem).

- Reset to factory settings via settings while getting there with a normal start up.

- wipe cache partition while in ClockworkMod recovery.

- wipe data/factory reset while in ClockworkMod recovery.

- mounts and storage -> format cache while in ClockworkMod recovery.

- mounts and storage -> format data while in ClockworkMod recovery.

- mounts and storage -> format sdcard while in ClockworkMod recovery.

- mounts and storage -> format sd-ext while in ClockworkMod recovery.

- advanced -> reboot recovery

Who knows what I'm doing wrong, or how to fix this problem?:confused:

(Hopefully) thanks!
[Desire Q&A, Help & Troubleshooting] spamrijk:
Anyone??????
[Desire Q&A, Help & Troubleshooting] MatDrOiD:
Which pvt-version does your desire have? You get this information from your hboot.

Sent from ICS with Transparent XDA App
[Epic 4G General] silver03wrx:
hey guys please sign that petition. Htc's ceo lied and said no more locked bootloaders back in may well the vivid has a locked bootloader. Lets please support our android brothers http://www.groubal.com/htc-vivid-has-locked-bootloader-contrary-to-statements-by-the-company/#sign
[Epic 4G General] k0nane:
Done. 10char
[Epic 4G General] silver03wrx:
Thank you sir. I dont even have an htc device anymore but there fight is a valid one
[Epic 4G General] AproSamurai:
Done, I agree with where you're coming from. :)
[Epic 4G General] silver03wrx:
In may there ceo said none of there devices would have locked bootloaders anymore. Htc is saying att did it and they lock all of there phones bootloaders. Which obviously is not true ours is not. And no samsung phones are. And att is saying htc did it. The rogers version the radar is exactly the same as the vivid and it can be unlocked on htcdev.com yet not the vivid
[Epic 4G General] psycho450:
Done! That's not cool!
[Epic 4G General] ac16313:
Signed as well

Sent from my Samsung Legen-wait for it-dary! 4g
[Epic 4G General] xopher.hunter:
Done. #150.
[Epic 4G General] The Root:
done and tweeted
[Epic 4G General] mattallica76:
Signed.
[Epic 4G General] vwags:
Signed 10 Char
[Epic 4G General] Ceelos09:
Signed, #175

I will tweet this also
[Epic 4G General] xgerryx:
signed10char
[Epic 4G General] shane6374:
Done.

F'n HTC
[Epic 4G General] Alias8818:
Done. #185!
[Epic 4G General] thomasskull666:
Signed!
[Epic 4G General] silver03wrx:
Look........
[Epic 4G General] diego1985:
Why is the date from May? That's kind of old.
[Epic 4G General] Looneyrat:
Do you see why I hate htc with passion? Worthless pos company with underperforming devices. The cripple their phones and lie. Gtfo. Tp2 was my final mistake.
[Epic 4G General] squshy 7:
Done. Although, i have to say, when trying to start a petition, one should at least proof read their description. "Ridiculous", not "rediculous". Lol
[Epic 4G General] slayer450:
Signed and shared on facebook.
[Epic 4G General] tkeyes:
Signed.

10char
[Epic 4G General] billyp707:
Done. 10char.
[Epic 4G General] TexasLTE:
Signed #233 ;)
[Epic 4G General] cisco723:
Signed...!!!!
[Epic 4G General] || Acer ||:
Signed. 10char
[Epic 4G General] darkierawr:
Nice.

Way to go HTC.

Signed and shared.
[Epic 4G General] Looneyrat:
Fak you htc!
[Epic 4G General] jrock32:
Signed...
[Epic 4G General] Looneyrat:
Burn im hell htc!
[Epic 4G General] KennyG123:
I did my part too!
[Epic 4G General] Looneyrat:
Htc..... I hope you go bankrupt you liying POS!
[Kindle Fire Android Development] orntar:
I just automatically got the update to 6.2 and now I'm stuck in a launcher boot loop.

I rerooted, and attempted to install launcher pro again, it says it exits, I copied it into the system/app dir, but now what?
[Kindle Fire Android Development] Unheard:
Shooting in the dark, but clear data/cache for LP?
[Kindle Fire Android Development] orntar:
thanks, a reboot or 2 seemed to have done it. I am rerooted, and everything seems to be working. :)
[Galaxy S II Q&A, Help & Troubleshooting] Kirot:
Hello, I just bought a Galaxy S2 and I would like to root it, reading on the different tutorials it recommends to use the kernel with a code as close as mine for the insecure one, and that in any case I can put back the original kernel after the rooting, all that is nice and understandable, however I'm unable to locate the kernel UHKI2 (I checked here http://xdaforums.com/show....php?t=1101671 and here http://xdaforums.com/show....php?t=1075278 in this second one I do see some files for my kernel but they are exe files, so not sure what to do with them), is there any other one that I can use without having the risk of damaging the phone? Any specific measures that I have to take while rooting?

Thanks in advance
[Galaxy S II Q&A, Help & Troubleshooting] anisbombaywala:
Read this one:

http://xdaforums.com/showthread.php?t=1321582
[Galaxy S II Q&A, Help & Troubleshooting] Kirot:
Thanks, but it doesn't answer my particular question, what I would like to know is which kernels to use for the rooting process