yashsingh1/xdaforums huggingface dataset:
[T-Mobile myTouch 4G Slide] gtmaster303:
I noticed my problem is only in specific places. Like at home or at my apartment at school. No I don't live in the basement. I actually get dropped call from the second floor of my house
[Asus  Eee Pad Transformer Prime] Fireplug:
Is anyone else having any issues with jpg pictures not completely loading in browsers while on JB? Not quite sure when this started happening, but I made a quick video to demonstrate below.

First off, I am unlocked and I made this video while on Craig's Stock JB ROM with the original data location. I added the init.d, EXT4, and CtlSys mods as well as the JB Build prop from the other build.prop thread at that time and was having the issue so not sure what was causing it.

Now, I just did a fresh clean install of a brand new Hairy Bean 1.3 JB ROM with the data2sd kernel and typical install and before doing any titanium restores or anything else I went and tested the browser and found out the SAME thing is happening on this ROM??? Much less frequently, but I've had it still happen. Weird thing is if it DOES happen, if I rotate the screen then the whole picture loads and will be there if I rotate back.

Is this a JB glitch and is anybody on Stock JB having this issue?

If someone can go to post 383 on Craig's thread to test it:

http://xdaforums.com/showpost.php?p=32345358&postcount=383

and click on the pictures as I did in the video can someone tell me if the pictures are fully loading in whatever browser you are using or sometimes does only the part actually showing on the screen load, and the bottom is white when you scroll? I've had this same issue on both the standard and data2microsd configurations.

Please check this video to see what I mean.

http://videobam.com/RUfqj

Thank you for your time.
[Asus  Eee Pad Transformer Prime] Fireplug:
157 views and nobody has this problem or is curious enough to check it themselves? ;)
[Asus  Eee Pad Transformer Prime] agentdonald:
You are not alone :) I experience the same problem. When you change from landscape to portrait and back then the image is fine again. So it seems a landscape rendering problem.
[Asus  Eee Pad Transformer Prime] Fireplug:
Thanks for confirming with me that at least someone else is having the issue. Found that it happens much less often with Chrome (but overall Chrome is much slower) and seems to never happen at all with Dolphin Beta.
[Android Software/Hacking General [Developers Only]] bob5731:
Hi

I just bought a next book next3. Looking for honeycomb for tablet or ice cream sandwich rom?
[Android Software/Hacking General [Developers Only]] bob5731:
Please help me update my nextbook next3
[Xoom Q&A, Help & Troubleshooting] Echo113:
I'm guessing it is stuck. As I'm typing this, the volume panel keeps popping up. If I try to adjust the volume slider down, it goes right back up. If it hit the down button, it will go away for a minute or two. It also keeps me from being able to put it to sleep. Could it be a software issue?
[Xoom Q&A, Help & Troubleshooting] Echo113:
So I just found out my xoom is the Verizon 3/4G + wifi one but I unlocked and rooted it as the wifi only version. Could that be why I'm getting weird malfunctions with my up volume?
[Asus Transformer TF700] iisniperzzz:
Any help is appreciated.
[Asus Transformer TF700] SuperSonicRob:
Settings> about tablet> build number.
[Asus Transformer TF700] iisniperzzz:
What if your running a custom ROM and want see what version bootloader u have?
[Asus Transformer TF700] lafester:
bootloader does not change with custom rom.
[Asus Transformer TF700] jtrosky:
If you want to see your bootloader version, you can see it when booting with "VolDown + Power" - it's in tiny text in the upper left hand corned of the screen.
[Sprint Samsung Galaxy S III] IsaacRCCL:
Can someone suggest a good Recovery Image?

I use Team Win Recovery Project TWRP and its pretty horrible.
[Sprint Samsung Galaxy S III] epic4GEE:
Really, your using this one http:// http://xdaforums.com/showthread.php?t=1809307&highlight=twrp and it's horrible? I like it, best option we have imo
[Sprint Samsung Galaxy S III] mnhertz26:
I agree, TWRP is the best by far. Your only other option is CWM and I think 4ext

Sent from my Jelly Bombed SGS3
[Sprint Samsung Galaxy S III] m20120:
I gotta go with TWRP. If that does not work for you then the only other real option is CWM.
[Sprint Samsung Galaxy S III] JBakey:
What's not to like about twrp? Its fast and easy to use, has a file manager, can rename backups right in recovery. So many more features than cwm, the only other viable alternative.
[Sprint Samsung Galaxy S III] jbadboy2007:
Twrp is the best
[Galaxy S III Q&A, Help & Troubleshooting] krellian20:
can someone tell me which is newer or better?

1.7.2 - > found this version without the need of rooting my phone.

1.6h - > is this a lower version? since there's an "h" I have no idea.

thanks.
[Galaxy S III Q&A, Help & Troubleshooting] chrismast:
1.7.4 is the most up to date one.
[Galaxy S III Q&A, Help & Troubleshooting] krellian20:
thanks
[Android Apps and Games] Super2cool:
Hey guys...

I just wanted to tell you guys about Real Widget. It lets you put a windows phone's tiles on your android home screen. It is not like Launcher7 which replaces your entire launcher. It is just a widget on your home screen.

Smart tiles such as Gmail which show information require you to buy the PRO Version for $1 which I feel is reasonable.

Unfortunately, its only available for android phones with ICS and higher.

Learn more about the app here:

http://www.appdigy.com/blog/entry/real-widget-brings-wp-tiles-to-android
[Android Apps and Games] DayDreamin24:
WP+Android? Me gusta.
[Android Apps and Games] Super2cool:
Yeah but unfortunately...

Its only on ICS and higher so it actually leaves out a huge chunk of people...

its worth buying though if you can !
[Android Apps and Games] duongtunglam:
If your app show tiles on 4 columns as WP8 is better :)
[Galaxy S II Q&A, Help & Troubleshooting] sawserlauz48:
so i formated my phone for some reason and all i see is black screen

and i cant get to the bootloader but i can get to download mode...

but my computer and odin cant recognize my phone

i updated all the drivers i need and still cant recognize

is there a way that i can fix this?

can i install the cwm to the sd card and how?

10x for the help!
[Galaxy S II Q&A, Help & Troubleshooting] Jokesy:
bootloader?

Can you still get to recovery mode?

You can try another cable and another USB port
[Galaxy S II Q&A, Help & Troubleshooting] tarek369:
reply

Try another computer, with a good known working cable :)
[Galaxy S II Q&A, Help & Troubleshooting] sawserlauz48:
i tried another cable and computer didnt work

that's the problem i can't get to the recovery mode

also tried another usb port didnt work
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
I''ve apparently broken my Galaxy Tab.

It's a GT-P7510. Galaxy Tab 10.1 WiFi only.

It doesn't respond to any screen input. I've done a bunch of things to try to resolve this with no solution.

The relevant info from the startup ("dmesg" output) is:

<7>[ 1.706171] maXTouch driver

<7>[ 1.706409] "sec_touch"

<7>[ 1.706571] addr: 0x004c

<7>[ 1.706735] irq: 220

<7>[ 1.706895] flags: 0x0000

<7>[ 1.707125] adapter:"Tegra I2C adapter"

<7>[ 1.707290] device: "(null)"

<4>[ 1.707677] tegra-i2c tegra-i2c.1: I2c error status 0x00000008

<4>[ 1.707913] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c

<4>[ 1.708080] tegra-i2c tegra-i2c.1: Packet status 0x00010009

<7>[ 1.709363] Warning: To wake up touch-ic in deep sleep, retry i2c communication!

<4>[ 1.748037] tegra-i2c tegra-i2c.1: I2c error status 0x00000008

<4>[ 1.748355] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c

<4>[ 1.748523] tegra-i2c tegra-i2c.1: Packet status 0x00010009

<3>[ 1.749788] sec_touch 1-004c: Failure accessing maXTouch device

<3>[ 1.750031] sec_touch 1-004c: Chip could not be identified

<6>[ 1.750199] p3_touch_exit_hw

So, it can't see the touchscreen driver, so no screen input. Can't unlock, can't do much of anything.

I've factory reset. Cleared everything. Installed CM10. Opened it up and disconnected the battery for 15 minutes. Nothing works.

Something (probably triggered from reading every file on the device due to a "find" shell command), has wedged the touchscreen interface.

Are there any tools I can use to probe the Tegra/i2c interface to find out what's happened? Or reset everything?

It's almost bricked,but not quite. Will an older or newer kernel wake up the touchscreen?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] wtgserpant:
U can try to go back to stock using Odin and in the mean while also whipping all data this way it should make sure that no corrupt data is left

---------- Post added at 10:23 PM ---------- Previous post was at 10:22 PM ----------

U can try to go back to stock using Odin and in the mean while also whipping all data this way it should make sure that no corrupt data is left
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
I've tried that - wiped data/cache/dalvik and re-installed using Odin with no improvement. I'm currently trying to restore a nandroid made under Honeycomb but I doubt that's going to fix it either. :(

(edit: yep. still no touchscreen input. Nice HC lockscreen, can't enter the PIN.)
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
Searching using mxt1386 finds the cause of this problem. http://xdaforums.com/showthread.php?t=1252829

If you read certain files in the /sys/devices directory tree, you corrupt the state of the touchscreen controller. Until you write the configuration to reset it, the touchscreen controller will be stuck in a state where the kernel refuses to initialize it. Based on the thread above, it's likely a fix to the maXTouch driver can recover from this problem. I'm going to have to learn how to build kernels and do some testing.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
Sorry to keep replying to myself on this, but I have it figured out and have a fix. My gtab is now happily accepting touchpad input.

I'll post details over in the thread mentioned above, but it's a modification to the kernel that repairs the wayward touchscreen controller.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] jamracer:
can u do this kernel package fo a i957?

do u think changing the touch screen would solve the prob
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
If the i957 uses the same tegra chip as the Tab 10.1 it's very likely fixable. The way to tell is to look at the dmesg output immediately after startup adb shell dmesg >dmes.txt

then edit dmesg.txt. If you see the "no acknowledge" error, then the same fix is likely to work:

As far as changing the touch screen: no, that won't help. The touchscreen controller chip is on the main board, which means that changing the touchscreen itself won't help. You've got to kick the chip back to life by feeding it the proper firmware.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] jamracer:
I get what

u say but, I tried s freezer method n after 5 mins in d touch started to work but just for a few mins
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] jamracer:
how or where can i get the proper firmware to fix this prob?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
Ok, so you've got a hardware problem. The fix I've come up with is to recover the touchscreen controller when it gets stuck in firmware update mode, which is clearly not what you're seeing. Time to return the tablet to Samsung for repair, I suspect.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
The firmware binary is distributed with the Linux kernel. For the Tegra, it's in drivers/input/touchscreen/mxt1386_fw_ver10.h - the prior release is mxt1386_fw_ver09.h.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] tofeek1:
my gtab gt-p7500 touch screen not responding

please need help my gtab gt-p7500 touch screen stop working, l have change the digitizer and everything i cant get it to work, please if anyone has a solution kindly post it and help me
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
The kernel that I posted in the other thread *should* work for your 7500, at least to fix the touchscreen. You'll need to re-flash a stock kernel to get 3G back afterwards.

Also, The A1 kernel already has the fix incorporated. Go to the Galaxy Tab 8.9 Android Development forum, find the A1 kernel, and install it on your tab. That should fix it for you.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] tofeek1:
my p7500 screen touch not working

i downloaded the A1 kernel for p7500 3G tab since the tab is not functioning i tried flashing the kernel with odin but seems odin could not recognize the files since the files is not md5,tar, img please i need a help
[Raspberry Pi Development] AdamOutler:
Update: trevd has managed to make a proper adb 1.0.29 frm source. For those who wish to simply use the binary, you can download it here http://xdaforums.com/attachment.php?attachmentid=1392336&d=1349930509

From trevd:

more here http://xdaforums.com/showpost.php?p=32632468&postcount=41

--- OLD ----

I'm trying to build ADB 1.0.28 or higher for the Raspberry Pi. I found a guide here: http://lackingrhoticity.blogspot.com/2010/02/how-to-build-adb-android-debugger.html but it's out of date since we can no longer access kernel.org directly. So, I'm trying to find a new way.

I spoke to Entropy512 and he suggested using the Cyanogenmod repository. So, here's what I have so far.

sudo apt-get install build-essential libncurses5-dev openjdk-7-jre openjdk-7-jdk bison
mkdir adb
cd adb
git clone git://github.com/CyanogenMod/android_system_core.git system/core
git clone git://github.com/CyanogenMod/android_build.git build
git clone git://github.com/CyanogenMod/android_external_zlib.git external/zlib
git clone git://github.com/CyanogenMod/android_bionic.git bionic
echo "include build/core/main.mk" >Makefile

I edited the adb/build/core/main.mk to reflect the version of JDK and JRE I have on my system. I'm not sure if they are even required at this point... Anyway, I modified the grep statements to find OpenJDK IcedTea instead of Oracle's version. Here's some snippits from the build/core/main.mk file.. make these match the values for your system's "java -version" and "javac -version"

build/core/main.mk

.
.
.
# Check for the correct version of java
java_version := $(shell java -version 2>&1 | head -n 1 | grep '[ "]1\.7[\. "$$]')
#Removed the next 3 lines

.

# Check for the correct version of javac
javac_version := $(shell javac -version 2>&1 | head -n 1 | grep '[ "]1\.7[\. "$$]')

So this puts me here:

pi@raspberrypi ~/adb $ make out/host/linux-x86/bin/adb
^[[A^[[B============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.4
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=IMM76L
============================================
build/core/tasks/kernel.mk:68: **********************************************************
build/core/tasks/kernel.mk:69: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:70: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:71: * BoardConfig.mk file *
build/core/tasks/kernel.mk:72: **********************************************************
host C: adb <= system/core/adb/adb.c
cc1: error: unrecognized command line option ‘-m32’
make: *** [out/host/linux-x86/obj/EXECUTABLES/adb_intermediates/adb.o] Error 1
pi@raspberrypi ~/adb $

I'm still working on the rest. help would be appreciated. I can't get it to build on my desktop either. I really need help with this.
[Raspberry Pi Development] AdamOutler:
I found a build of Android4.0 for the Raspberry pi. I know that Android ICS and higher come with adb installed on the device for use with USB Host Mode on the device. So I yanked a copy and installed to an sdcard. Then I pulled the binary from /system/bin/adb. however when run it acts like it's not there even though it is.

pi@raspberrypi ~ $ sudo chmod 777 /usr/bin/adb
pi@raspberrypi ~ $ /usr/bin/adb
bash: /usr/bin/adb: No such file or directory
pi@raspberrypi ~ $ file /usr/bin/adb
/usr/bin/adb: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), stripped
pi@raspberrypi ~ $ readelf -d /usr/bin/adb

Dynamic section at offset 0x1708c contains 24 entries:
Tag Type Name/Value
0x00000003 (PLTGOT) 0x1f198
0x00000002 (PLTRELSZ) 768 (bytes)
0x00000017 (JMPREL) 0x9048
0x00000014 (PLTREL) REL
0x00000011 (REL) 0x9348
0x00000012 (RELSZ) 16 (bytes)
0x00000013 (RELENT) 8 (bytes)
0x00000015 (DEBUG) 0x0
0x00000006 (SYMTAB) 0x8488
0x0000000b (SYMENT) 16 (bytes)
0x00000005 (STRTAB) 0x8bd8
0x0000000a (STRSZ) 1135 (bytes)
0x00000004 (HASH) 0x8128
0x00000001 (NEEDED) Shared library: [libc.so]
0x00000001 (NEEDED) Shared library: [libstdc++.so]
0x00000001 (NEEDED) Shared library: [libm.so]
0x00000020 (PREINIT_ARRAY) 0x1f000
0x00000021 (PREINIT_ARRAYSZ) 0x8
0x00000019 (INIT_ARRAY) 0x1f008
0x0000001b (INIT_ARRAYSZ) 8 (bytes)
0x0000001a (FINI_ARRAY) 0x1f010
0x0000001c (FINI_ARRAYSZ) 8 (bytes)
0x0000001e (FLAGS)
0x00000000 (NULL) 0x0

I can see there are shared libraries required (libc.so, libstdc++.so and libm.so) , so I added those to /usr/lib/ chmod'd 777 and still nothing changed. What is required for a non-statically compiled binary to run? Did I install those libs properly? Why is that file saying it's not found?

I usually deal with hardware and java. these system binaries are like greek to me.
[Raspberry Pi Development] bhundven:
I find dynamic dependencies this way (sgh-i717 rild for instance):

bryan@minime:~/build/vendor/samsung/quincyatt/proprietary/bin$ ~/arm-2009q3/bin/arm-none-linux-gnueabi-objdump -x rild | grep NEEDED
NEEDED liblog.so
NEEDED libcutils.so
NEEDED libril.so
NEEDED libdl.so
NEEDED libc.so
NEEDED libstdc++.so
NEEDED libm.so

EDIT: I just re-read about you finding NEEDED. At that point you have to do the same thing to each of those libraries, and find out what they depend on.

EDIT2: Do you have prebuilt/ ?
[Raspberry Pi Development] cdesai:
You can try compiling it statically, sync the AOSP master to get the latest code, then you'll have to edit system/core/*something*(probably adb)/Android.mk and tell it to link the target binary statically.

I'll link the exact file when on a pc.

Sent from my GT-P1000
[Raspberry Pi Development] bhundven:
Right:

LOCAL_FORCE_STATIC_EXECUTABLE := true

where host adb is defined in system/core/adb/Android.mk
[Raspberry Pi Development] AdamOutler:
That would be great! How do you compile statically for arm? I put in about 12 hours trying to do this today.
[Raspberry Pi Development] bhundven:
It was my assumption from the original link you posted that this was being built on the r-pi.

Without the prebuilts being part of the environment, linux-x86 directory would be the host gcc. In this case on r-pi debian, arm gcc.

Edit: From the original build you had a problem with -m32 not being a valid argument.

You could comment out lines 48 and 49 of: build/core/combo/HOST_linux-x86.mk

and see what happens.

irc?
[Raspberry Pi Development] trevd:
Seems like your fighting a losing battle there, for that length of time you might as well have sync'd the full lot and done a full build to begin with, It really is the path of least resistance when It comes to android. Otherwise you end up chasing shadows as you get deeper into the build system.

What are you trying to achieve with this? do you want to connect to other devices from the RaspPi or is the Rasp meant to be on the receiving end?

because obviously you'll need to build the daemonized version if the Rasp is your target, that lives in /sbin/adbd normally on the device.

I had a quick look at that guide. Googles sources now live at android.googlesource.com which can be used instead of the old kernel.org address

i.e

[B]git clone git://android.git.kernel.org/platform/system/core.git system/core[/B]

becomes

[B]git clone https://android.googlesource.com/platform/system/core.git system/core[/B]
[Raspberry Pi Development] AdamOutler:
Are you sure that will compile on ARM host? I don't want to spend 24 hours downloading and compiling on a 700 MHz processor. The resulting adb binary must run on an arm linux host.
[Raspberry Pi Development] E:V:A:
Looks to me as you forgot to add your /usr/bin to your PATH variable (which also need to be exported to shell.)

Until you do that you need to use the source operator ".":

$ [B].[/B]/usr/bin/adb
[Raspberry Pi Development] AdamOutler:
good thinking.. but it didn't work.. cannot execute binary file.

pi@raspberrypi ~ $ export PATH=/usr/bin:$PATH
pi@raspberrypi ~ $ adb
bash: /usr/bin/adb: No such file or directory
pi@raspberrypi ~ $ /usr/bin/adb
bash: /usr/bin/adb: No such file or directory
pi@raspberrypi ~ $ . /usr/bin/adb
bash: .: /usr/bin/adb: cannot execute binary file
pi@raspberrypi ~ $

I have an older copy of ADB 1.0.26, but I need 1.0.28. What is the difference here aside from the shared objects which I've already put into /usr/lib.

pi@raspberrypi ~ $ file /usr/bin/adb #new version
/usr/bin/adb: setuid setgid ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), stripped
pi@raspberrypi ~ $ file /bin/adb #old version
/bin/adb: setuid setgid ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, for GNU/Linux 2.6.26, BuildID[sha1]=0x8ffd8c80a0705dc113149612e3067931208bfd70, not stripped
[Raspberry Pi Development] AdamOutler:
ok, so i've been hacking around on this quite a bit... I don't know how to work through this final linking part. here's a pastebin...

http://pastebin.com/pb8F7raB

how do i fix undefined references? I've been hacking it up by linking files where they should be linkd. I don't know how to fix this. Like I said before... I don't work at this level usually. I work on Java, shell, and hardware. C and middle-ware is not my thing.
[Raspberry Pi Development] bhundven:
Try adding:

--with-float=soft

to LOCAL_CFLAGS

EDIT: You might also need to add

-lgcc

to the LOCAL_LDFLAGS
[Raspberry Pi Development] bhundven:
Try build/core/combo/TARGET_linux-arm.mk
[Raspberry Pi Development] AdamOutler:
I added

LOCAL_CFLAGS += --with-float=soft
LOCAL_LDFLAGS += -lgcc

to both the TARGET you suggested and HOST_linux_x86. I got the same error.

I'm compiling this on the Raspberry Pi itself because i need the statically linked host binary. I'm using the x86 host because there is no arm host available. this should be irrelevant because i'm using the native build tools. Anyway.. I convinced it to use x86 and now the linking seems to be the final challenge.
[Raspberry Pi Development] AdamOutler:
I did the changes above, then a full make clean then rebuilt the source. the following pastebin shows the entire build log.

http://pastebin.com/XtH1MWVE
[Raspberry Pi Development] AdamOutler:
Rebellos did some work and posted his source here. I modified it to link to my own source and compile directly on the device without a cross-compiler. He got farther than I did. His actually searches for a device, but there is no real server output and its not sending commands to the device.

http://dl.dropbox.com/u/32145655/adb_armv6_src.zip
[Raspberry Pi Development] trevd:
Hi Adam.

I've built you a adb, version 1.0.29 which is based off the linaro Jellybean 4.1.1 JRO03R sources, It is a totally self contained statically linked binary which has a target arch of armv5te, which should be just fine. I don't have a PI to test it on but I did the next best thing [ link: qemu-emulating-raspberry-pi-the-easy-way ] It seems to function OK but the proof will be in the testing. If it has trouble listing devices or making connection then run the following command line to give an idea of what's going wrong.

ADB_TRACE=all ./adb

Hope That Helps!

Trev