yashsingh1/xdaforums huggingface dataset:
[Android Stick & Console AllWinner based Computers] apollostees:
My goal here is to make an EASY to use display for people be able to read DOC, PDF, XLS files.

Here is what I want to use:

1. Rikomagic MK802 III

2. Logitech T650 touchpad

3. 1080P 52" LG TV. (We already own this)

4. Office/PDF app such as: Kingsoft Office, or Easy PDF reader

I plan to connect the MK802 to the tv then install the touch pad (in the available USB slot) and have people use the touchpad to "flip" through files.

In my mind it seems simple enough but some questions I have are:

A. Does anyone know a way to lock android into a "demo mode" of sorts. Where only one app is accessible and the screen stays on?

B. Has anyone used the logitech touchpad T650?

C. Any better app suggestions? Keeping in mind easy is the key.
[Android Stick & Console AllWinner based Computers] apollostees:
Just found a cool app that will take care of the demo mode that I want:

KioWare Kiosk Mode Software
[Android Stick & Console AllWinner based Computers] player911:
On the MK808 custom software, you can disable the navigation keys... essentially keeping from anyone escaping. It is possible to bring back the navigation and exit but not at first glance...

Not sure how you could do this. Maybe a tasker sequence to check if XYZ app is running else launch XYZ. So even if someone did exit, it would relaunch.

Combination of both?
[Android Stick & Console AllWinner based Computers] hudis602:
did it work?

Hi, did the Logitech Touchpad work?

I tried the newest MK 802 (8G, bluetooth) with Apple Magic Trackpad and it did not work - no mouse movements, no clicks.
[Android Stick & Console AllWinner based Computers] Timbermill:
This might be of use to you, Smart Protector. I've used it in conjunction with launchers that can hide icons to stop anyone from messing about with the setup.
[HTC One X] HelloMyNamesTom:
I was an idiot and didn't do a backup when the post I followed told me to and I really need to get my phone back to stock. I have done A LOT of searching for this bloody file and if someone could send me a download link that would be amazing.

I actually managed to find a stock ota update zip but it wouldn't install, any help would be very much appreciated.
[HTC One X] requiem11:
I haven't looked myself, and I'm sure you were diligent enough in your own searches, but have you considered that maybe there isn't one yet? This was the case for me when I had a failed OTA update to jellybean. The solution I found was to flash the boot.img from the OTA zip file that I had just installed. That stopped my boot loop issue. Alternatively, you could search for a nandroid backup of the stock ROM that someone may have very generously provided for your particular CID. Look for it here:

http://xdaforums.com/showthread.php?t=1975140
[HTC One X] Bram89:
RUU for 3.16.61.6 is not in existence yet. Download and restore a nandroid backup from the link above seems like the only way to go.

OT: I searched @ www.htcruu.com but the RUU's for HOX seems to be missing, What's the deal here :confused:
[HTC One X] Mr Hofs:
http://xdaforums.com/showthread.php?t=2104672

;)
[RAZR HD Q&A, Help & Troubleshooting] rickt1152:
I have been a big fan of Swype for quite some time, however the pre-installed version just does not seem the same. Has anyone tried to uninstall the version that came on the phone and reinstalled Swype beta?
[RAZR HD Q&A, Help & Troubleshooting] SEANDROID:
I have! Are you rooted?

---------- Post added at 02:43 AM ---------- Previous post was at 02:41 AM ----------

I uninstalled using Titanium, then just installed the beta. It works like a dream!
[RAZR HD Q&A, Help & Troubleshooting] rickt1152:
Yes I am rooted. Any issue with future ota upgrades as this is pre-installed. I didn't know if I needed to do this a certain way.
[RAZR HD Q&A, Help & Troubleshooting] SEANDROID:
No I issues, I just deleted the baked in version again. Do a nand backup of your current system for piece of mind!
[HTC Incredible S] bildou:
Helllo !

My phone come back to A.S.S. Changed mainboard, usb port, LCD Screen .... but i'm S ON.

It was not my first time to get S OFF.I already had S-OFF via HTC-DEV or revolutionary but today it's impossible!

I have already use many tuto but it's impossible to get S Off or unlocked

Via HTC-DEV -> Error 173 :(

via tacoroot and zergRush -> did'nt work ( not the # and su not found)

via revolutionary -> not compatible

Sorry for my English, I'm French ^^

Android 4.04

HTC SENSE 3.6

Numero logiciel 4.10.405.1

VIVO PVT SHIP S-ON RL

HBOOT- 2.02.0002

RADIO 3831.18.00.11_M

eMMC-boot

May 22 2012, 14:22:08
[HTC Incredible S] poondog:
Bonjour!

Did you try nonverbose's script?
[HTC Incredible S] bildou:
hi!

did'nt Work ! ( Failed)
[HTC Incredible S] tpbklake:
You need to unlock the bootloader at HTCDEV.com and then when you run the script, answer YES that ou have the official ICS rom and then it will work.
[HTC Incredible S] bildou:
I say but HTCDEV return a error 173 when i give my device identifier token :confused:
[HTC Incredible S] srv.abhishek:
On the HTC DEV site, does it say to update the HBOOT?

I had helped one of my friends, HTC Desire HD though, and the site mandated updating the HBOOT before proceeding
[HTC Incredible S] bildou:
It look like a server error....

Answer from HTC :

"we work on identify and remove the issue, please be patient and try to use the site again in few days"

EDIT : HTC DEV work fine today ! Go custom roms!
[HTC Incredible S] zulmajdi:
If you want to s-off just reloock the bootloader and then run the ruu and you done
[HTC Incredible S] 072665995:
U need to first unlock the bootloader. Flash CWM (or 4ext or TWRP whicever u want), flash superuser 3.1.3, then test it using adb.exe shell, su. And you should get #. Then run Nonverbose's scriptfound here. If the script doesnt seem to work, then u can find alternative instructions on page 4 on how to do it manually in adb. Run the RUU found in here (select whichever applicable). If you do that without error, then run Revolutionary (and Blackrose if youd like). Ive made a guide and Its in my signature.
[HTC Incredible S] zulmajdi:
Relock the bootloader and then run the ruu
[HTC Incredible S] 072665995:
This error is, I believe an error received when unlocking the bootloader from HTC-Dev.

Unlock the bootloader from htcdev.com first then follow what i said before.
[HTC Incredible S] shmetal:
excuse me guys how can i install ruu on my device and which ruu i should install???
[HTC Incredible S] 072665995:
http://xdaforums.com/showthread.php?t=1373697

Run the script in here. If everything runs successfully, run the RUU. If you still get error 173, relock the bootloader and run the RUU again. MAKE SURE THE SCRIPT RAN WITHOUT ERROR. THIS IS ESSENTIAL OTHERWISE THE RUU WONT WORK.
[HTC Incredible S] zulmajdi:
No need for run the script. Just run the ruu. Last time im s-off my device i just relock the bootloader and run the ruu
[HTC One X+] Kelex24:
My hox+ will not connect to ADB on my Windows 7 machine. It works fine in OSX, so it shouldn't be a hardware issue. I have tried installing HTC Sync, uninstalling the driver manually, browsing for drivers on the file system, and pretty much anything else I could find online for the hox and hox+.

The only thing I can get to install for the device is the default Microsoft MTP driver. Even if I uninstall it, restart my machine and plug the phone back in, it just comes back with that same driver. It never gives me the chance to choose my own before it shows up as an MTP device.

Does anyone have any suggestions to get this working?

EDIT: More info

I have flashed the AT&T CWM recovery to my device, and it is NOT rooted.
[HTC One X+] nespid:
Try another usb port.

Is usb debugging turned on in settings?
[HTC One X+] AndroHero:
Don't worry about the MTP driver, it's irrelevant. As the poster above me said, first try a diffrent usb port, one that connects directly to the mobo. ADB does not play nice with usb hubs.
[HTC One X+] Kelex24:
This is on a laptop, I am not connecting to a USB hub. I've tried each USB port with the same result.

I have also tried every combination of turning debugging on and off, each time the device will just reconnect as an MTP device. ADB still does not detect anything. I am an app developer, and I have a bunch of other devices that work fine.

Has anyone got this to connect to adb on a Windows machine successfully?

EDIT: Would having a custom recovery installed affect ADB on my stock rom? I have the AT&T CWM recovery installed.
[HTC One X+] Kelex24:
bump, I really would like to get this resolved. I am going to try and call HTC today to see what they say about this issue.
[HTC One X+] nespid:
Let us know how much support HTC offered, since it is AT&T branded. And how you worked around telling them you installed custom recovery?
[HTC One X+] kingofnice:
USB debugging enabled?

Sent from my HTC One X+
[HTC One X+] jtrue:
This might help, I had a similar issue. I installed HTC Sync which installs the drivers, then I uninstalled just the HTC Sync app leaving the drivers.

http://xdaforums.com/showpost.php?p=36541164&postcount=44
[HTC One X+] Kelex24:
No need to "work around" having a custom recovery installed. This has nothing to do with the device not being detected properly in Windows 7 while booted into the OS.

Spoke with tier 1 support and he didn't really know what ADB was, but still tried all the usual troubleshooting. The support request was escalated and I got a call back yesterday where the tech was more knowledgeable. He tried all the install/uninstall driver stuff that I did, which still did not work (uninstall/reinstall driver, force install in device manager, remove all htc drivers using USBDeview). After that did not work he had another idea that ended up being the solution. I'll put that below for anyone that has the same problem.

How to solve HTC One X+ not detected by ADB:

Download and use USBDeview to remove all instances of HTC drivers.

Open the androidusb.inf file in your HTC drivers folder (you are going to need admin privs to write to this part of the filesystem, open Notepad as Administrator and then open the file). Modify the ClassGuid=XXXXXXXXX... with the Device class guid of your HOX+ including the { }. It is found under Details in Device Manager properties for your device. Save the file back to its original location.

Now open Device Manager. Find the device (mine was under Portable Devices), Right-click -> Update Driver Software -> Browse my computer for driver software -> Let me pick from a list of device drivers on my computer -> Have Disk... -> Browse for androidusb.inf (x64 Windows 7 it is in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64) -> HTC, Corporation -> MY HTC -> Ok. Congratulations, your device should now be detected by ADB.
[Eee Pad Transformer Q&A, Help & Troubleshooting] YayYouFixedIt:
Where are the best resources on rom development?
[Nexus 4 Accessories] robrob777:
Excellent Case IMO

$8-9 Ebay US shipped

$8-9 Ebay China Shipped

More colors available.

I Like:

Everything, Looks, Quality, Grip, Fit, Barely there

Con?:

Top and bottom are not protected.

View attachment 1665681. View attachment 1665682 . View attachment 1665683. View attachment 1665684

View attachment 1665685. View attachment 1665686. View attachment 1665687. View attachment 1665688

View attachment 1665689. View attachment 1665690. View attachment 1665747
[Nexus 4 Accessories] phon00b:
Digging the texture. Might have to nab one.
[Nexus 4 Accessories] ma678:
I have this one since day 1. It fits N4 precisely.

The only con is like OP said. The top and bottom open too wide to protect the phone properly.
[Nexus 4 Accessories] blade_:
nice and looks very slim
[Nexus 4 Accessories] robrob777:
Guys I bought the Red version.

I notice that there are some sellers on Ebay that ships the case from the US for just 9 dollars, I updated the OP, there is no more reason to buy from China.

The Red color is not a deep red(example: ipod touch red), it is like a washed out red, I bought it for a girl friend so it is OK bc IMO and her opinion looks a bit girly.
[Nexus 4 Accessories] Zenzic:
I bought this but with the leather cover which doubles up as a stand. It looks identical to this but with the leather bit so it's good to know OP is happy with it.

Shipping is over a month though which is a complete joke, if anyone finds a similar one for similar price (UK) quickly let me know as I can't see one.
[LG Optimus 3D] jkusmc:
How many are there that use the 3d max in the US? What carrier are you on? What data speeds are you getting?
[Asus  Eee Pad Transformer Prime] blanktree:
I recently got a Logitech K810 keyboard.

If I use cm-10.1-20130109-UNOFFICIAL-tf201.zip everything works fine. Pair and connection. However if I flash to anything above this such as cm-10.1-20130116-UNOFFICIAL-tf201.zip or cm-10.1-20130119-UNOFFICIAL-tf201.zip I can pair with no problem but it will not connect. If I try a bluetooth headset on all 3 it works fine.

Any suggestions?

Thanks
[Thunderbolt Q&A, Help & Troubleshooting] jblack248:
Hello everyone! I have been a lurker for nearly two years and have recently decided to try my best at compiling CM9 for the Thunderbolt. I know we have TwistedUmbrella's excellent ICS build based on work from liquid, jester, AOSP, AOKP, and CM, but I'm mainly wanting to do this for the learning experience. If I develop a working, usable build then that's all the better!

So far I have done the following:

Setup a build environment on Xubuntu 12.10 64-bit

Installed dependencies

Installed Android SDK

Installed Java

Synced CyanogenMod repo

Ran build/envsetup.sh

Ran vendor/cm/get-prebuilts

Compiled CM10.1 for my Nexus 7

Learned build process (breakfast, lunch, brunch, mka, make clobber, repo, etc.)

Learned how the different pieces come together for a device

Ensured that my system was setup correctly by building without errors

Ensured that build worked by flashing it to device

Switched repo to ICS branch

Modified local_manifest.xml to pull in sources from Twisted's github "ThePlayground"

Ran extract-files.sh with phone running Twisted's ICS build

Script might be out of date or for gingerbread, as rild_ims, spkamp, and qcrild do not exist on Twisted's, Liquid's or the ICS leak's builds in system/bin

Renamed rild_ims to rild

Added spkamp and qcrild from a gingerbread build to prevent build errors (assuming if it compiled it would be unstable)

Modified device/htc/mecha/BoardConfig.mk to not use Twisted's "lean_aosp_defconfig" kernel

Changed to TARGET_KERNEL_CONFIG := mecha_defconfig

Selected mecha-userdebug from lunch and hoped I could mka some bacon

The build process ran for fifteen minutes and stopped with these errors:

To temporarily bypass these errors, I disabled anything related to QCOM_AUDIO in device/htc/msm7x30-common/BoardConfigCommon.mk. The build then fails on a display overlay issue, so I re-enabled QCOM_AUDIO and have come here to ask for help. Any ideas?

Note: As you can see, I am using some of Twisted's sources on github. I have tried asking permission to use his sources in a public manner by emailing him but he hasn't responded. He doesn't accept private messages on XDA so maybe this will get his attention. I'm assuming there's nothing wrong with me using his sources privately since they're available on github, but if something usable comes of this I would want his good graces before sharing it.
[Thunderbolt Q&A, Help & Troubleshooting] disconnecktie:
Maybe it had something to do with the fact that you changed the defconfig. I would leave it alone and try again. If you get the same error then you know it wasn't that at least.
[Thunderbolt Q&A, Help & Troubleshooting] jblack248:
I switched back to the lean kernel config and the build process stopped at exactly the same spot. Here is an expanded log if it helps anyone determine what's going on:

I also added the following repositories to local_manifest.xml but they did not help. Maybe I'm missing something else?

I'm thinking about using CyanogenMod's repository for android_device_htc_msm7x30-common and seeing what happens. There are a number of differences in the BoardConfigCommon.mk (things obviously specific to the Thunderbolt such as the lack of HDMI out). Also, this project is where Twisted placed his custom boot animation so that's different as well.
[Thunderbolt Q&A, Help & Troubleshooting] disconnecktie:
Worth a shot.
[Thunderbolt Q&A, Help & Troubleshooting] santod040:
Syntax error: LINK
[Thunderbolt Q&A, Help & Troubleshooting] jblack248:
The C++ warning for the comparison between signed and unsigned integers shouldn't stop the compiler. I noticed a number of them when compiling CM10.1 for the Nexus 7, so they're surprisingly common. Typically those warnings will compile with a worst-case scenario of unexpected behavior or crashing during execution. Thanks for the input though, I appreciate it.

The error seems to be that AudioHardware.cpp is trying to use variables within the AudioHardware class (defined in hardware/qcom/media/audio/msm7x30/AudioHardware.h under the android_audio_legacy namespace) that doesn't include them as members. I might try adding them in manually, but I'm skeptical since Twisted's build works so well and these are the sources he's using (I'm assuming).
[Thunderbolt Q&A, Help & Troubleshooting] jblack248:
Well I changed out Twisted's msm7x30-common with CM's repository and it compiled for about 30 minutes. It seems it got to compiling the kernel then stopped at a C++ library issue. My install script that I use on fresh installations accidentally referenced g++-4.5-multilib instead of g++-multilib, so that explains it. Regardless, this is encouraging!
[Thunderbolt Q&A, Help & Troubleshooting] jblack248:
It compiled! I'm going to flash it and report back.
[Thunderbolt Q&A, Help & Troubleshooting] jblack248:
System UI and com.android.phone keep crashing, not letting me get past them. For a brief moment the status bar was visible, and when I hold the power button I can see the power menu. Pressing the volume keys also shows the volume slider, although I can't use it. I'm not sure where to go from here, so I might get into modifying CM's msm7x30-common and comparing it with Twisted's to see what's missing.
[Thunderbolt Q&A, Help & Troubleshooting] rrrrrrredbelly:
If you want to reach Twisted, best way is probably through the forums of his website, think it's in his signature here on xda
[Thunderbolt Q&A, Help & Troubleshooting] jblack248:
Good idea! I just set up an account on his forum and will message him momentarily.

So far I've been diving into the differences with msm7x30-common and trying to find out precisely why Twisted's version won't compile for me. It's a time consuming process since I have to 'make clobber' and try to rebuild each time I change something.
[Thunderbolt Q&A, Help & Troubleshooting] jblack248:
I got busy doing other things and put this project away until a few days ago. I have since started rebuilding the device tree for mecha in order to sort things out. However, I haven't been able to get a build to compile due to an error with something entirely unrelated to mecha. I get a Java error code 41 as shown below. I have scoured the Internet for hours trying to find a solution but haven't had any luck.

So far I have done the following without success:

make clobber and clean multiple times (build gets to 14GB before this happens - still takes time even with ccache enabled)

uninstalled and reinstalled Oracle Sun JDK 6 and set to default for good measure (thinking about trying JDK 7, but JDK 6 is recommended)

'make update-api' as recommended from other threads on this subject

Modified development/samples/FmRadioTransmitter/src/com/example/android/fmradiotransmitter/FmRadioTransmitter.java

Changed 'import android.hardware.fm' to 'import com.stericsson.hardware.fm' (and later back again)

Code resides in frameworks/base/fmradio/java/com/stericsson/hardware/fm

So far the general concensus online seems to point ot this being a build environment issue, although I haven't had problems compiling CM before this. Any ideas?
[Thunderbolt Q&A, Help & Troubleshooting] disconnecktie:
Try skipping the fm radio altogether. What version of Linux are you running? I couldn't compile Cm10.1 on mint 12 but it works fine on Ubuntu 12.1.

Sent from my personally built from source CM10.1 N7.
[Thunderbolt Q&A, Help & Troubleshooting] jblack248:
Compiled but not booting

I'm running the same configuration from earlier on Xubuntu 12.10. I wanted to tackle what the problem was instead of disable things, but rolling back android/development by one commit bypassed the inclusion of the FM Radio and let me finish my build. Strangely, it didn't make a final flashable zip so I had to run 'make -j# otapackage' manually.

Anyways, I just flashed it to my Thunderbolt and it doesn't get past the boot animation. Judging from the logcat it seems that there's some audio problems with msm7x30-common that I need to tackle. The logcat posted below is the section that loops continuously.
[Thunderbolt Q&A, Help & Troubleshooting] santod040:
My guess based on your log, and past experience with building cm and logs I have seen, is this.

The problem appears to be a mismatch between SAP kernel libraries and database libraries.

It can rectified by only matching the patch levels of both.

But this is something I believe Twisted was fighting with as well, and although rectified enough to boot, it was what I believe was causing his reboot issues upon searching in text fields and other similar instances.

Not sure that any of that helps or is 100% accurate, but that's what I have to offer for now.

Good luck! :)
[Thunderbolt Q&A, Help & Troubleshooting] jblack248:
I'm not too familiar with kernel development so can you explain where I would "match the patch levels"? I have done some searching (related to errors with msm audio, I was fruitless with searches related to "SAP kernel patch level") and revealed that some people had issues with libraries such as libandroid_runtime.so, libandroid_servers.so, libmedia_jni.so, and others. I am currently pulling libs from Twisted's build so those are identical. I haven't tried using any libs from the stock ICS build because I'm assuming they won't work without HTC's kernel source. I'll give it a shot if it's a viable option, though. I am comparing the system folder from Twisted's to mine to see if there are any other glaring differences. I'm also thinking about using his kernel as a prebuilt even though mine compiled without issue.

I have nearly finished rewriting a new device_htc_mecha folder using a combination of Twisted's, liquid's, default CM, and other device trees (such as ace, pyramid and fat-tire's encore) that hasn't caused any issues thus far. I had to start over since many overlays caused issues with CM. However, I had to revert back to using CM's device_htc_msm7x30-common device tree with a few minor modifications due to complications in building Twisted's heavily modified version. His makes calls and sprawls out into his own other customized vendor folders to copy over gapps (I guess to integrate them into the ROM zip, I'd rather keep them separate for legal and debugging purposes) and other misc apps. It also makes a call to a vendor_qcom folder (supposedly form https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno) that has more proprietary files in it. As an aside, I chuckled when I saw in git he added himself to their copyright license.

I'll start work on making a new msm7x30-common device tree and judging whether or not additions belong in that common folder or in mecha (or a new makefile to keep the differences obvious). Obviously CM's device tree works for their supported devices, so I don't want to cause problems later on in case this ends up being officially supported (one can dream).

My github is https://github.com/jblack248.