yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Accessories] airmaxx23:
A decent case at a store is going to cost $29 - $39, you can get basically the same thing on ebay for $12-$19 with free shipping. A lot of times they come with a decent screen protector for free.
[Kindle Fire Accessories] hrbib21:
Just got a TPU rubber case on Ebay for $6.95. Also got a neoprene pouch for $10.95. IMO, Ebay is the best option.

Retail, I don't know for sure, but I would think Radio Shack would carry something considering they carry the KF.
[Kindle Fire Accessories] Saddlebags:
Speaking personally neither the Targets nor the Best Buys near me carry accessories for the Fire just yet; plenty of regular Kindle covers/cases but none specifically for the KF. I can only assume this will change and soon, but as of last week I couldn't find anything.

Hope you guys fair better than I.
[Kindle Fire Accessories] JoshuaLintag:
Well, some people actually does sell cases outside, like here on Philippines.
[Kindle Fire Accessories] kfc0107@hotmail.com:
I bought kindle fire case from store4kindle.com $3.99. But the shipping is a little slow.
[Kindle Fire Accessories] scarsofthumper:
Interesting. The Supertarget by my place carries them. I got an M-Edge KF case for $29 there.
[Kindle Fire Accessories] blauciel:
Target carries some, but they're expensive.

//Tapatalk.KindleFire//
[Kindle Fire Accessories] jekswang:
My Marware Eco-Vue case is delayed.. so in the meantime I ordered a sleeve from Case Logic on-line, and I really like it. Was like $18 including S/H. Shipping was very fast.
[Samsung Galaxy Nexus] phatdub:
Exchanged the phone back to radio shack for all the issues that's been plaguing the forums. Got a new unit and I must say, 1000% better. Signal is way better,battery is amazing and next to no banding on the screen. I'm glad I didn't give up hope on this little beast.

I would post screen shots but the app says I'm disabled from posting pictures.
[Samsung Galaxy Nexus] skynet99:
What issues were you experiencing with your first phone?
[Samsung Galaxy Nexus] phatdub:
1. Couldn't hold data signal for anything, even in the VZW store where all the other GNex's where getting signal.

2.Horrible banding and blotches on the screen when set to a low brightness.

3.Phone would not switch from LTE to CDMA , always had to keep it on CDMA which was resulting in the battery draining in 4-5 hours
[Samsung Galaxy Nexus] ranova:
do you mean you had to keep it on LTE?
[Samsung Galaxy Nexus] phatdub:
It was always looking for LTE when CDMA was available, the Data bars where always gray with no signal unless I had it set to CDMA only. The new phone does not suffer from this problem.

Added Screen shots to my OG Post.
[Xperia Play General] Just Cause 2:
XDA must have an online chat room so we can easily communicate with each other and get online support !

And I suggest http://xat.com ¡!!!!¡

Regards,

JC2
[Xperia Play General] fma965:
They have Irc
[Xperia Play General] odst0016:
I made an xperia play irc nobody uses it lol
[Xperia Play General] Just Cause 2:
irc? What is irc :confused:
[Xperia Play General] odst0016:
Its an online chatroom like thing there is also an android app
[Xperia Play General] Fokezy:
Lol back in my day we only had irc and mirc scripts. Kids these days with their facebooks an twitters and whatnot...

Sent from my Xperia Play
[Xperia Play General] odst0016:
I prefer irc to all those alternative social communication sites its easier and in my opinion a more direct way of communication
[Xperia Play General] fma965:
IRC is Internet relay chat it is essentially the same as a free php chatroom but requires a IRC client. it also has much more features
[Xperia Play General] Logseman:
QFT. the Internet was simpler back then.
[Xperia Play General] Fokezy:
Lol today I used the computer at my grandma's house...It still has Mirc and 56k internet :D
[Xperia Play General] DeathTorrent:
mIRC is the ****...I still use IRC, altho there isn't a mIRC for Linux :'( lol I remember running the invincible script back in the day and thinking I was hot **** lololol
[Xperia Play General] Logseman:
There are tons of Linux IRC clients, beginning with Empathy... And for Android as well, such as AndIRC..

Swypesation
[Xperia Play General] Baltyre:
For android, the best is to use a bouncer like ZNC who act like an irc proxy.

You connect znc to all your chatroom and it will keep you here, logging all data.

Then you can connect as many much irc client that you want to the irc server and you will keep the same name and have the log of what's happen before you connect.

Very usefull on a mobile client to have the logs of previous talks
[Xperia Play General] Willie_Dynamite:
wow... now I feel old.. :)
[Captivate Q&A, Help & Troubleshooting] sdamarla15:
Help Needed.Looks like i screwed by Samsung Captivate.

here is what i did :

My captivate was running cyanogen mod 7 (nightly build cm_captivatemtd_full-181)

I wanted to re-install CM7 and did the following:

1)Phone already had the copy of the same build in root directory which i used for cm7 install for the first time

2)I kept the phone in download mode and Used ODIN to flash the Kernel.It went through successfully.

3)I used the three button technique and tried to install the Build which has failed with 'assert failed:getprop (" some blah blah) saying finally installation aborted.

Not sure if i should have recopied the build to the phone instead of using the same existing build in the phone

4)Though the installation failed...my phone is not booting up and when i reboot.. the phone is hung with a message 'galaxy S scg-i897 Samsung' and doesnt boot up.

Please help on how to recover my phone to a normal state.

4)
[Captivate Q&A, Help & Troubleshooting] prbassplayer:
This should be in CM7 thread. Did you try going back in to recovery? Try to get in recovery and factory reset+wipe cache and wipe dalvik and reflash?
[Captivate Q&A, Help & Troubleshooting] sdamarla15:
I did all the steps you have mentioned in recovery . May i please know what do you mean by reflash?

you mean again i have flash kernal and install CM7 ?

Also as you know the i cannot copy any build to the phone as phone is booting up . Do u mean i have to use fresh build instead of the one which is there since my first cm7 install..

please suggest.Thanks for you reply.
[Captivate Q&A, Help & Troubleshooting] prbassplayer:
If you can get in to cwm and you have a cm7 rom in your sd card, then you can attempt to reflash the rom. IF that's not possible ODIN back to a "stock" and start all over.
[Captivate Q&A, Help & Troubleshooting] studacris:
^Or...If you can get to cwm...you can mount the sdcard, in mounts and storages, and transfer what the hell ever you want over from your PC to your phone. Like a fresh download of cm7 for example...
[Captivate Q&A, Help & Troubleshooting] sdamarla15:
sorry i know i am taking your time .

i am very new to these techincal words..

1)can you please help me how i can go into cwm ?

2)How to ODIN back to 'Stock'?

Thanks.
[Captivate Q&A, Help & Troubleshooting] prbassplayer:
Lol You always know a better way lol xD.

CWM= ClockWorkMod its the modified recovery used to do a whole bunch of things one being flashing roms.

If you don't know how to use ODIN then you shouldn't be messing with AOSP's or flashing for that matter.

Read First thread

Captivatte Directory thread <- lots of guides there.

How to Gingerbread thread

All of these are stickied and you should understand most of them to flash "safely"
[EVO 4G Q&A, Help & Troubleshooting] MannyA:
Yes, I am a noob. Yes, I saw the video and followed the steps. Yes, I most definitely appreciate your help and realize it may take some time for a reply.

I do not have the know-how required to deal with a rooted phone. A friend of mine was the one who originally rooted my phone roughly a year ago. I decided to unroot it. I used the unroot method provided at androidforums.com

Everything happened as it was described. However, I still have SuperUser as well as access to ClockWork Recovery and bootloader. I can also see in Software Information the kernel version. It is my understanding that if your phone is rooted, you should not be able to access these. I feel like I shouldn't be able to access these and that my phone shouldn't be displaying the kernel versionSo these are my questions:

1. Will bootloader still show up, when you hold the down volume and on-off button, even if your phone is unrooted?

2. Should you be able to access Clockwork Recovery and SuperUser if your phone is unrooted?

3. How do I know with 100% that my phone is unrooted? Is there some kind of test or method of testing?

4. Do I need any of the ROOTING/UNROOTING zip files on my phone after it's been unrooted?

I simply want my phone to be stock, like it was when I bought it. I have read on these forums that if the bootloader displays s-on then the phone is unrooted; I have s-on but can still access these programs.

Once again, I just want to go back to stock. No SuperUser, no Clockwork, nothing, regular stock HBOOT#. How do I go about this?

I want to thank you ahead of time. I know you guys have tons of questions thrown at you. Thank you.

Current Phone Information:

SUPERSONIC EVT3 SHIP S-ON

HBOOT-6.17.0001

TOUCH PANEL ATMEL224_16ab

RADIO-2.15.00.0000

Mar 8 2001

Android Version 2.3.3

Baseband Version

2.15.00.0808

Kernel Version

2.6.35.10-gc0a661b

htc-kernel@and18-2#

Tue Jun 14...etc.

Build Number

4.24.651.1 CL61076 release-keys

Software number

4.24.651.1
[EVO 4G Q&A, Help & Troubleshooting] Notorious:
Your unrooted you just have to run a ruu to get rid of superuser.clockwork, and your hboot back to normal

---------- Post added at 07:03 PM ---------- Previous post was at 06:58 PM ----------

http://www.fileserve.com/file/3rVYVfd download the ruu rename it to PC36IMG.zip put it on the root of your sd card (not in any folders) power down to the bootloader accept the update reboot and youll be 100% stock
[EVO 4G Q&A, Help & Troubleshooting] MannyA:
Thank you, evo4gnoob.

When I unrooted my phone, I downloaded that file, transferred it to my sd and let the bootloader update. However, I still have superuser, clockwork, hboot like I mentioned.

I don't know if this will tell you anything, but whenever I restart my phone, it goes into a continuous restart cycle.
[EVO 4G Q&A, Help & Troubleshooting] Notorious:
i posted the download llink
[EVO 4G Q&A, Help & Troubleshooting] MannyA:
I edited my post once I saw your link. Thank you for adding that on to your post. Once I saw the name of the file, I recognized it. Yesterday, when I unrooted my phone, I downloaded that file renamed it to PC36IMG.zip and transferred it to the root of my SD. The bootloader updated and I proceeded. However, I still have all the previously mentioned conditions. Including the bootloop.

In order to be thorough, I have downloaded the file you linked. I renamed it to PC36IMG.zip, transferred it to the root of my SD and brought up the bootloader. I accepted the update. It updated a few of the things on the list, and then rebooted into bootloader and it continued to update. Afterwards, I turned it off, and try to get into bootloader but it would just start up normally. I did a battery pull and then it let me into bootloader. The HBOOT is now 2.16.

Should I proceed to delete all the zip files associated with rooting and unrooting?

THANK YOU.
[EVO 4G Q&A, Help & Troubleshooting] Notorious:
It's up to.you
[EVO 4G Q&A, Help & Troubleshooting] Notorious:
What made it go into a.continues

Sent from my PC36100 using bootloop

XDA App
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
Just out of curiosity, why did you unroot in the first place? Just to have it stock??

just had this conversation with a friend of mine, who wants to root his Prevail for the first time. Being S-off, itself, doesn't change anything on your phone, as far as how it runs, looks, etc.

It's like having the keys to a car you don't drive. Just because you don't drive it, doesn't mean you throw the keys away.
[Touch Pro2, Tilt 2 Android Development] detule:
Let's make life less complicated and start a new thread for people to provide feedback on 2.6.39, ... 3.3, 3.4 (NEW) RHODIUM kernels. The source repository is here. Note, older trees are not under active development.

By the way, these kernels are developed jointly with jonpry, WisTilt2, and bzo. In addition a lot of code is shared with people that maintain active msm kernel branches (emwe, acl, Alex). Finally, all Xdandroid Kernel developers have in one way or another contributed code.

1. Feel free to use any of these kernels, however DO NOT submit a post in this thread that amounts to "This feature does not work for me." If you wish to submit a bug report, make sure you are proficient at using ADB, AND have installed GetLogs. In your post you should:

a. Include GetLogs output of the problem (or it didn't happen).

b. Include Rhodium model (100, 210, etc).

c. Try to reproduce the problem on the other kernels.

All other bug reports will likely not receive full attention.

2. These kernels are to be used with GBX0B.

3. These are auto-built at:

Auto Built Service generously provided by WisTilt2

The autobuild is down. Please use these links, they were the final kernel builds that were on the autobuild site.

2.6.39.3

3.0.18

3.3.8

3.4.3

4. What works:

This list should look very similar to the current status of .27 with your device. Meaning, if you have a rhodium on which the camera does not work with .27 (for example), camera will not work with these kernels as well. Please do not report issues that are present on .27+your device.

- Only 3.0 has BT support. Would appreciate some feedback on this. I get the impression that pairing/connecting takes a bit of patience, but I am interested in how this compares to BT in .27. If we get some positive feedback we can enable BT support across all three kernels.

5. How do these three kernels differ: They are maintained by the same group of people, and consequently differ very little. There are slight variations in power management code, but other than that they are hard to distinguish in terms of functionality.

6. Kexec: To hot-swap the kernels (boot with a new kernel without rebooting into WinMo):

a. While in Android, copy the new kernel and modules to the same location (over-writing the zImage) as your current kernel (adb push).

b. Go to the shutdown menu in GB, and select "Kexec".

c. Phone will reboot within Android, using the new kernel.

7. Finally, I don't have too much time to hang around xda, so you shouldn't hope for "next-business day" response policy:) I am just hoping we can attract the advanced user to these kernels, that can do most of the troubleshooting on their own.

Enjoy, RHOD has to be one of only a handful of android devices that are pairing android with kernels as advanced as these.
[Touch Pro2, Tilt 2 Android Development] detule:
This you should note:

I. If you are experiencing problems with turning Wi-Fi on, try the procedure outlined HERE before posting.

II. With regards to usb related functions and 3.4:

This kernel uses ICS style usb drivers and as a consequence, usb notifications in GBX no longer work. To work around this issue we wrote a little app XdaRndisToggler, which should allow you to turn on ADB, as well as USB Tethering (RNDIS).

Using this app is pretty self-explanatory:

0. Plug your phone in (No notification will appear in GBX).

1. Start the app.

2a. To start the ADB service, select "ADB only" and click apply. At this point you can use ADB to connect to the device.

2b. To start USB tethering, select "ADB+Rndis" and click apply. At this point go into Settings->Wireless->Tethering and check the box that says USB Tethering. The blue "USB Tethering" notification should appear in your taskbar and you should be all set to tether.

3. To stop using ADB and/or RNDIS, select "Disable USB" in the app and click Apply.

FOR ADVANCED USERS:

Alternatively, you can use ADB without the use of XdaRndisToggler (app is still needed for tethering), by making the following changes to init.cfg/init.gingerbread.rc (note, you will need to remount / as rw)

on property:persist.service.adb.enable=1
- start adbd
+ start adbd
+ write /sys/class/android_usb/android0/enable 0
+ write /sys/class/android_usb/android0/idVendor 0x0bb4
+ write /sys/class/android_usb/android0/idProduct 0x0c01
+ write /sys/class/android_usb/android0/functions adb
+ write /sys/class/android_usb/android0/enable 1

on property:persist.service.adb.enable=0
stop adbd
+ write /sys/class/android_usb/android0/enable 0
+ write /sys/class/android_usb/android0/bDeviceClass 0

Above, minus/plus is used to denote delete/add line respectively.

Downloads:

XdaRndisToggler 06/19
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Ts-calibration is not working on the 3.0.9 kernel.

I can't see the [+]'s.

I was forced to use my own calibration file.
[Touch Pro2, Tilt 2 Android Development] marcopolo:
I am using the temporary 3.0 kernel and till now, I have faced a few problems:

1) Whenever I make a call, the screen goes blank (I couldn't get the logs using Getlogs, don't know from where to pick it) possibly because of the proximity sensor, the screen won't back even if I use power button, however if I slide out the keyboard, the screen comes back.

2) On some random calls, the sound simply gets disappear and doesn't come. Normally this doesn't happen on every call (trust me, I called more than 7-8 phone no. for more than 1 hours today itself) but suddenly, but on one call, the sound just vanished and I couldn't hear anything from the caller on the other side. The problem remained there until I rebooted my phone.
[Touch Pro2, Tilt 2 Android Development] detule:
GetLogs
[Touch Pro2, Tilt 2 Android Development] detule:
Also, since it seems this is an issue you can reproduce (which rhodium by the way?), can you try some of the other kernels .35, .39, 3.1 and try to reproduce it there as well.

Are you using 3.0 for its bluetooth capability - if so, how's that working for you?
[Touch Pro2, Tilt 2 Android Development] marcopolo:
Well, I tried pairing bluetooth with my laptop and a bluetooth headset, it takes forever however my laptop and the headset is always visible in the available device list. I have used .39 (wifi wasn't an issue on it but calls were problem) and .27 (provided with the bundle where voice issue was constant) and then used 3.0 (temporary provided by you), I am facing this problem on all of them. I have RHOD100, CSVs are attached with this post.

Also, I already have getlog installed on this build (it was provided in the Android App folder) but still, I cannot figure-out where exactly it is saving the file. Since you have provided the Getlog thread hence I will read it through and will provide you the same.

Update: Have attached logs taken from Getlogs. Thanks for the guidance.
[Touch Pro2, Tilt 2 Android Development] detule:
You instincts were right, it is proximity related. In the file you attached if you search for "proximity" you will see a few "proximity 0" and no "proximity 1" -> meaning the proximity sensor is always reporting "user is near" and consequently the screen stays off.

Here is a silly question, do you have a case on your device, one that might be obstructing the sensor?
[Touch Pro2, Tilt 2 Android Development] marcopolo:
Nope, I don't have one. In fact I have been facing this problem in the Windows Mobile ROM also... but used some tweak. This problem was not there in the FRX07.1 and the screen was good however I am now facing this with GBX0B which is not a new thing.

The screen comes back the moment I pull hardware keyboard but goes off if the call is on or I press power button (general practice to turn the screen on) and then it won't come even if I pull the keyboard.

I have one more question which may sound off topic but thought it's good to ask an expert rather suffering forever.

I am wondering which key should I use to disconnect the call since the end key doesn't work in this case and throw me back on the home screen.
[Touch Pro2, Tilt 2 Android Development] detule:
Yes, GBX0B is the first time (apart from NAND) that proximity-related functionality has been enabled.

If you are seeing the same problem in WinMo then you may be facing a hardware failure of your proximity sensor. On the other hand it could be that RHOD100 is somehow special, and we don't have the correct gpio setup in the kernel to handle your device. I just heard from a RHOD110 user saying that everything is fine, so I might be leaning towards the former.

Unfortunately I don't know of any quick tweaks to disable the sensor in Android.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm definitely leaning towards that myself. If it's busted in WinMo, chances of it working correctly in Android are slim-to-none.
[Touch Pro2, Tilt 2 Android Development] marcopolo:
I understand, though I will wait for a resolution in near future :) :D

Still, thanks for sparing your time answering me :)
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
For whatever reason, the link to the autobuild is opening like this

http://autobuild.wirelesstcp.net/<br />http://autobuild.wirelesstcp.net/<br />http://autobuild.wirelesstcp.net/

Not sure why (I know how to get to the page, I'm just pointing this out)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Works fine here... FF9/Chrome16.
[Touch Pro2, Tilt 2 Android Development] detule:
Thanks for the heads up i fixed it earlier today.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Now to legitimently post something...

3.1 does not funtion well on my RHOD500 GBX0B. Enabling wifi caused a soft reset that never seemed to clear up. 3.0 works alright. I will probably post the logs in a bit as I've switched to 3.0, however it is incredibly easy to replicate.
[Touch Pro2, Tilt 2 Android Development] detule:
Can't reproduce on RHOD400 with 3.1, wifi functions flawlessly for me. Since 400 and 500 are basically the same device, I would expect the same to be the case on your device as well.

This is where logs would have been useful.

Not sure what a "soft reset that never seemed to clear up" means. Reset to bootanimation? This is usually a user-land miscue.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Decided to create a new post rather than edit the previous one. Anyways I'm not familier with "user-land miscue" so you'll have to explain that one to me, and yes it is a reset to boot animation. Upon manually reseting the device nothing on the homescreen loads and under wifi in settings it says "error"

data.txt contains only one intersting line that I could see.

E/WifiService( 1325): Failed to load Wi-Fi driver.

In logcat.txt the first line related to wifi is

I/ActivityManager( 1324): Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.WirelessSettings } from pid 1457

It's late and adb shell is giving trouble with the whole cat /proc/kmesg > dmesg.txt. The included terminal emulator crashes whenever I run it, I have little to no cell signal where I now live, and the Market refuses to work over wifi. I'll dig up an apk after I get some sleep.
[Touch Pro2, Tilt 2 Android Development] detule:
Critical kernel errors (so called panics) end in a full blown reset to win-mo. When the device resets to bootanimation, this is Android (userland) freaking out for whatever reason.

Usually this is indicative of kernel/modules magic mismatch. Have you tried this http://xdaforums.com/showpost.php?p=20887127&postcount=20 ? If that doesn't work, what kind of output do you get if you type

insmod /lib/modules/bcm4329.ko

Use GetLogs.

Use GetLogs.

Use GetLogs.

Use GetLogs.

Use GetLogs.

Use GetLogs.

Use GetLogs.

...I feel like I am repeating myself.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
You are, rather unecisarily too. How do you think I got data.txt?

rm -rf /lib/modules

Did not solve the issue. Phone still goes to boot animation. Not sure what to do next, not sure why it's happening considering we basically have the same phone.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, that's really a shame, since other devices use 210. I guess we could set it to 240 since the lcd.density in startup.txt trumps it, and see if it breaks the older devices.