yashsingh1/xdaforums huggingface dataset:
[LG G Watch] RunNgun42:
Have a G Watch, plan to buy either the 360 or the R, whichever I can get my hands on first. I think 360 looks marginally better, but I imagine the R will get equal or better life than my G which is fantastic. 36% @ 18 hours ambient mode on heavy usage including firmware update tonight. Plus I like the pixel density since I can see some jaggies in the 360 photos. We'll see though, I've polled 3 hot chicks on which they like best and they all say the 360 hands down.
[LG G Watch] HuStLaZ:
I'm leaning towards the R. the 360 does look nice and classy, but the better battery (since i have my G Watch always on) will win me over. Just waiting for an Australian release now.
[LG G Watch] Rayan:
I had the chance of playing with a Moto360 and quite honestly, I found it very nice and comfortable. However, even though it feels premium, once I took some photos with it, I noticed that its design looks kinda cheap and uninspiring. I don't know how to explain it. It looks like a small aluminum can strapped to your wrist.

However while browsing some photos of the LGGWR, I found one particular photo that resembles a photo that I took while wearing the Moto360 right next to my Pulsar dumbwatch and I couldn't stop noticing how small the LGGWR screen really is. Just compare both photos below showing the exact same content. You can see the woman's face is chopped off even more on the LGGWR.

On the Moto360 we can see her face all the way down to her mouth, and on the LGGWR can can see her face not even reaching the tip of her nose.

Isn't the LGGWR supposed to be 320x320? If so, then even if the screen is smaller, it's supposed to scale the image accordingly to show the same content as the Moto360 even if it has the black strip.

Take a close look!

Cheers!
[LG G Watch] HuStLaZ:
Interesting pics!

I'm curious as to why the LG doesn't display text to the edges? So much unused white space around the text that it makes the box bigger (thereby hiding more the background image).
[LG G Watch] Rayan:
Yes, I only hope they were using a different AndroidWare version (older perhaps) than the one on the Moto360.

Cheers!
[LG G Watch] RunNgun42:
It scaled the image, what they didnt do was scale the text. It looks like they still wanted a 10pt font to look like 10pt so if you notice, the same text messages takes up 3 lines instead of 2 on the 360. Both devices place the margin at the lowest line of text, and since the 360 is clearly larger they can fit more text using the same font size. The only thing LG could do would be to let the font scale down with the higher resolution, but that might make it harder to read.

Honestly I dont think it really matters too much, since the watch's purpose is really just to get your attention to the phone. It's not like we're going to be surfing the internet and watching movies on these things. Notification arrives, you have the option to kinda look at it, and if it requires more than 2 seconds of your attention then you pull out your phone anyway. This is how it's going to be for ANY watch.
[LG G Watch] Rayan:
But physical screen size does not have anything to do with image scaling. Both watches have basically the same resolution, 320x320 on the Round and 320x290 on the Moto360. The 30 pixel difference comes from the black bar at the bottom of the Moto360, so in theory they should look the same, and if we add the fact that AW cannot be modded by OEMs, then I don't see why there's such difference in scaling.

But yes, I don't consider this a dealbreaker at all... I just brought it up to the table for discussion purposes. I am more concerned about the Round's P-OLED screen than anything.

Cheers!
[LG G Watch] RunNgun42:
Consider it like this, if you have a 1080p desktop monitor that is 24" wide and a 1080p flatscreen TV that is 60" wide, does the font appear bigger on the larger screen?
[LG G Watch] Rayan:
Precisely my point... The fonts (and everything else) should appear larger. However those photos display a different scenario, the text paragraph (not the font size) and the white background are not formatted the same, there are larger gaps on the sides of the text on the Round.

But again, I really hope they were only using an earlier version of AW for that particular LG G Watch Round smartwatch.
[LG G Watch] RunNgun42:
Well what I think they did is that to avoid the G watch making the fonts look smaller since the screen is smaller, they actually made the fonts BIGGER thus they run out of room on the screen and end up taking 3 rows instead of 2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ltindi32:
Hi guys. someone has been achieved with a free method to unlock a sgh-i747 galaxy s3 in kik kat FNE4 4.4.2? if someone has done it, I appreciate your help. thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
There is no free unlock method once you install a stock Samsung 4.3 ROM or higher.
[General Questions and Answers] PoconKG:
please help !! how to fix camera?:crying:
[General Questions and Answers] ILIVE4HEAD:
Be more specific... What exactly is the problem?
[General Questions and Answers] PoconKG:
i'm tap a camera and this : unfortunately camera has stopped

gallery is work but camera has stopped
[General Questions and Answers] ILIVE4HEAD:
I had this problem too... First of all reboot into recovery then go to wipe>advanced wipe and check cache and dalvik cache. Reboot and see if the camera opens. If this doesn't work (it didn't for me) just reflash the latest cm11 nightly.
[General Questions and Answers] PoconKG:
doesn't work for me, this is logcat camera [IMG="logcat"]https://imageshack.us/i/kn2iaHmMp[/IMG] i'm not understand a logcat.

my device not supported cyanogenmod. i'm porting a cyanogenmod :(

sorry my bad english
[General Questions and Answers] ILIVE4HEAD:
what phone do you have?
[General Questions and Answers] PoconKG:
my phone a brands local but same spec a k-touch u86 :(
[General Questions and Answers] ILIVE4HEAD:
I really don't know what to say if reflashing a new nightly did not work for you then I have no other solution... Sorry try to bring this question to a help thred
[General Questions and Answers] PoconKG:
ok it's okay no problem , thanks to answer ;)

you're devices htc one? almost same spec . i'm port to my device i'm flash eror status 7 set perm some changes failed :confused:
[General Questions and Answers] OMOMM:
sam problem for me :crying:
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] David_R711:
I need help, I've installed Alliance rom on my Verizon s5 and now when I perform a shutdown / reboot the phone will not shut down completely, for example, the LED light and buttons stay on. I have to pull the battery in order to restart the phone. Does anyone know how to fix this?
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] David_R711:
Just read another review with the same problem. Thanks guys!
[JASJAR, XDA Exec, MDA Pro General] monkeyleader:
Hi,

Just got TomTom6 with UK maps and tried to sync my XDA and bluetooth GPS

- firstly under the bluetooth settings the GPS device appears but with a ? beside it. When I hold down on it I get edit / delete but no connect option

- within the TomTom software I dont see any option to pair via bluetooth?

Any thoughts?

Nigel
[JASJAR, XDA Exec, MDA Pro General] monkeyleader:
Fixed it - just needed to add an outgoing port (0) to the BT device.

:)
[Android Software/Hacking General [Developers Only]] bovirus:
Busybox compilation on Linux

reserved
[Android Software/Hacking General [Developers Only]] E:V:A:
Great Info here!

But I would be interested to know how well this method works on Samsung Stock devices running AOS 4.2 and above? Any experience?
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Awesome info, this thread came up #1 while googling busybox 1.23 :p

I made a flashable zip of the attached binary in the op to clean the old one(if any) and install the new busybox in xbin, just in case if anyone needs it. :good:
[Android Software/Hacking General [Developers Only]] Hamidreza2010:
Is it work on xperia sp on 4.3 fw yes ?
[Android Software/Hacking General [Developers Only]] -CALIBAN666-:
Thanx,worx fine with Carbon 4.4.4 on my LG.

GREETZ FROM TEAM-OPTIMA!!!
[Android Software/Hacking General [Developers Only]] 7175:
Thanks man. I've been compiling tons of stuff with Debian and Ubuntu chroot no problem on top of 4.3.1 Vanir and also 4.4.4 Carbon, both are my daily drivers. "Complete Linux Installer" is pretty fast compared to some other chroot apps like GNUroot (no offense to GNUroot, it works but is way too slow). It runs real-time compared to non-chroot. When compared to my dual-core 2007 Pentium M laptop, it's about 2-3 times as slow which isn't too bad for compiling something like mksh or even busybox which takes up to 5 mins I'd say.

In terms of binary size, compiling natively is better than cross-compiling it seems. I used gcc with no size optimizations here, so 1.37MB is pretty nice compared to some others around 2MB with full configs. With this method and klcc (gcc wrapper) I got mksh compiled to 192KB. I'm currently trying to build a uclibc toolchain on my laptop that will give me a mksh binary under 300KB..

Cool thanks man! That is really useful, glad to hear from CALIBAN that it works. Could I add this to the OP with credit to you?

Yes, xperia sp uses armv7 so you should be good to go.
[Android Software/Hacking General [Developers Only]] YashdSaraf:
Sure bro go ahead

Edit: Went ahead and made one for selinux enabled busybox :silly: , you can add this one in the op too.
[Android Software/Hacking General [Developers Only]] 7175:
Hey guys I was able to get an entire uClibc toolchain built the other day (using buildroot). I tested it and it makes some nice small binaries with about 20%+ smaller size than the standard glibc. Man that took hours to compile but was well worth it. It really put the stability of Android OS to the test as well. Kitkat absolutely couldn't finish compiling with multiple oom's and oops's, but Vanir 4.3.1 stuck it out real nice. Once I had the huge amount of required buildroot packages downloaded, I was able to compile in TWRP as well with good stability. (I have the "Complete Linux Installer" startup chroot script aliased in my mkshrc so I can pull up an ubuntu terminal without starting the app. :) )

So I got 3 new attachments to OP:

- arm-linux-uclibc toolchain for anyone who wants to compile stuff with it (host=arm AND target=arm)

- busybox (374 fcns, non-selinux) 1116KB

- lzip binary (in case you need it to unzip the toolchain, which is highly compressed from 64MB to 14MB with lzip's lzma)

**As I mentioned in the updated OP, I wasn't able to get selinux-enabled busybox compiled with uclibc. This may be something unsupported, or there may be a patch fix. I'll check it out. I'll try with musl libc and musl-gcc as well.
[Android Software/Hacking General [Developers Only]] ndrancs:
I have another approach, I try aboriginal cross compiler toolchain in archLinux it produced small binary, but I can't compile busybox for android. For Linux it work. Maybe need bionic lib?
[Android Software/Hacking General [Developers Only]] 7175:
Sounds interesting. I honestly haven't given this a try yet, but I'm very interested in taking a look at it. At this point I'm pretty much addicted to making the smallest binaries I can and testing out different toolchains. I'll give it a good search on duckduckgo, and if you have any insightful links that would be great.

Edit: Alright cool I found the source for Aboriginal Linux at landley.net/aboriginal and am building on Android now. I'm also trying this on my x86_64 laptop so that I can compare the differences like I have with glibc, uclibc, musl, klibc binary builds in a native environment and a cross-compile environment.

I see from my laptop's build that a busybox was generated, but it was dynamic and has a libc.so.6 dependency. [MENTION=5359154]ndrancs[/MENTION] : this might be what you were talking about. Did you try compiling static? Also see if "make allnoconfig && make clean && make LDFLAGS=-static" works for compiling busybox with Aboriginal Linux.
[Android Software/Hacking General [Developers Only]] ndrancs:
I preferred to use uclibc I think it easy to setup and produced small binary.. Aboriginal cross-compiler use uclibc as default. Btw I don't use cmd : LDFLAGS=-static instead I set it in .config.. Maybe I try this later.. ;)
[Android Software/Hacking General [Developers Only]] 7175:
Ok yeah I like how aboriginal set up with uclibc, and it has scripts for each build stage, so you can stop at the toolchain. I'll be interested to see their future releases with the musl libc as well.

Also for anyone interested, I figured out how to run dynamic binaries in android:

- make the directories "/lib" and "/lib/arm-linux-gnueabihf"

mkdir -p /lib/arm-linux-gnueabihf

- copy the linker "ld-linux-armhf.so.3" to "/lib"

- find a specific binary's dependencies: e.g. for dynamic mksh do:

strings mksh | grep \\.so

- copy the listed libs to "/lib/arm-linux-gnueabihf": e.g. for mksh that would be libc.so.6. The libs/linker you copy over will come from the mounted ubuntu/debian/... image you have mounted like with "Complete Linux Installer".

- adjust your LD_LIBRARY_PATH:

LD_LIBRARY_PATH=/lib:/lib/arm-linux-gnueabihf:$LD_LIBRARY_PATH
[Android Software/Hacking General [Developers Only]] ndrancs:
Any plan to update the busybox to current version. Thanks.
[Android Software/Hacking General [Developers Only]] exodius48:
[MENTION=5109059]7175[/MENTION] can you update flashable zip to 1.23.0 stable ?
[Android Software/Hacking General [Developers Only]] 7175:
[MENTION=5359154]ndrancs[/MENTION] [MENTION=5210243]exodius48[/MENTION] : Thanks for notifying me guys, I needed to get around to updating to 1.23.0 stable. I updated the original post with no-edify installers for busybox 1.23.0 stable. There's a non-SELinux uclibc compiled version and a full 386-applet SELinux glibc compiled version. They're included in this post too for ease.
[Android Software/Hacking General [Developers Only]] exodius48:
Great..been waiting for this release.. :good:

Btw, can i use busybox_full_selinux.zip on android 4.2.2 MIUI rom?
[Android Software/Hacking General [Developers Only]] 7175:
Yeah that should work just fine. I'm pretty sure any SELinux tools or applet flags should work since 4.2 introduced SELinux to its filesystem. Let me know if there are any issues. :)
[Android Software/Hacking General [Developers Only]] exodius48:
Great release..busybox_full_selinux.zip working fine so far on MIUI rom V5 android 4.2.2. :victory:
[Android Software/Hacking General [Developers Only]] amit.bagaria:
Hey [MENTION=5109059]7175[/MENTION]

Great guide. I am able to compile just fine on my device using your guide. However, is there any way to compile the selinux applets support using a Linux PC (or NDK)? I am not able to find a selinux supported toolchain. May be you can help.
[Android Software/Hacking General [Developers Only]] 7175:
Thanks, glad it was helpful.

Yeah, definitely. You can cross-compile busybox with SELinux support using a glibc toolchain. You can build a glibc toolchain using "buildroot." Here's a mini-guide to cross-compile busybox with SELinux support on a linux pc:

cross-compile busybox with SELinux support on a linux pc (on Debian or Ubuntu)

- Download buildroot

- Uncompress and change to its source directory. Then run "make menuconfig". Configure it to build a glibc toolchain for arm OR download and unzip the attached config file to the buildroot source directory.

- Run "make" and let the toolchain compile (10 mins - 1 hour). The toolchain will be located from the source directory in "./output/host/usr". Let's copy the toolchain to "~/arm-glibc" for convenience in the next steps.

- Now we need to get a few extra SELinux library files and cross-compile them to use with busybox. Change to your home directory and run "apt-get source libselinux libsepol". This will download the source for libselinux and libsepol.

- Change to the ~/libselinux* directory and run:

export PATH=~/arm-glibc/bin:"$PATH"
export LD_LIBRARY_PATH=~/arm-glibc/lib:"$LD_LIBRARY_PATH"
make CC=arm-buildroot-linux-gnueabi-gcc CFLAGS='-I ~/arm-glibc/include'

- Change to the ~/libsepol* directory and run:

export PATH=~/arm-glibc/bin:"$PATH"
export LD_LIBRARY_PATH=~/arm-glibc/lib:"$LD_LIBRARY_PATH"
make CC=arm-buildroot-linux-gnueabi-gcc CFLAGS='-I ~/arm-glibc/include'

- Now that we got libselinux and libsepol cross-compiled, we are ready to cross-compile busybox with selinux support. Change to your source busybox directory. I'm gonna assume you have it configured or are using the .config file I attached in the OP. Now run:

export PATH=~/arm-glibc/bin:"$PATH"
export LD_LIBRARY_PATH=~/arm-glibc/lib:"$LD_LIBRARY_PATH"
make CC=arm-buildroot-linux-gnueabi-gcc CFLAGS='-Os -I ~/arm-glibc/include -I ~/libselinux*/include -I ~/libsepol*/include' LDFLAGS='-static -L ~/libselinux*/src -L ~/libsepol*/src -lselinux -lsepol'

So what we're doing with the make command is setting the cross-compiler with CC, including the header files for selinux with CFLAGS, and including library files for selinux and compiling in the libselinux and libsepol libraries with LDFLAGS.

- After this is done, you will have a busybox_unstripped file. Use

cp busybox_unstripped busybox
~/arm-glibc/bin/arm-buildroot-linux-gnueabi-strip -s busybox

to strip your busybox executable.

I'm uploading my glibc cross-compiler at the moment. I'll post a link as soon as it's finished. :)

If you use it and want to follow the directions above, just extract it to your home directory and rename the folder to arm-glibc

cd
tar xf arm-buildroot-linux-gnueabi.tgz
mv arm-buildroot-linux-gnueabi arm-glibc

EDIT: Here's a couple download links for the arm-glibc-cross-compiler(to run on x86-64 linux): rapidgator, mediafire
[Android Software/Hacking General [Developers Only]] amit.bagaria:
Awesome. This is exactly what I was looking for. Actually, while you were replying, I got started with building the buildroot toolchain, but was not confident on the config I did using the 'make menuconfig'.

I will soon try the steps listed by you and let you know how it goes.

Again, thanks a lot for putting up this guide. I really appreciate the effort and the preciseness in your guides.
[Android Software/Hacking General [Developers Only]] amit.bagaria:
[MENTION=5109059]7175[/MENTION]

I followed your guide on cross compiling and was also able to compile the selinux applets using the cross-compiler version provided by you. However, the generated filesize of busybox binary (after stripping) is around 2.3 MB (which is very big, as I want to use this in my ramdisk limited to 8MB, including the kernel :) ).

I tried building the uClib toolchain on the device (which built fine), but using this I am not able to build busybox binary (it's giving some "ld" issues)

/home/test/autobuild/instance-2/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libc.a(setregid.os): In function `setregid': setregid.c:(.text+0x0): multiple definition of `setregid' /home/test/autobuild/instance-2/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libpthread.a(pthread_setregid.os):pthread_setregid.c:(.text+0x0): first defined here /home/test/autobuild/instance-2/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libc.a(setresgid.os): In function `setresgid': setresgid.c:(.text+0x0): multiple definition of `setresgid' /home/test/autobuild/instance-2/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libpthread.a(pthread_setresgid.os):pthread_setresgid.c:(.text+0x0): first defined here /home/test/autobuild/instance-2/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libc.a(setresuid.os): In function `setresuid': setresuid.c:(.text+0x0): multiple definition of `setresuid' /home/test/autobuild/instance-2/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libpthread.a(pthread_setresuid.os):pthread_setresuid.c:(.text+0x0): first defined here /home/test/autobuild/instance-2/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libc.a(setreuid.os): In function `setreuid': setreuid.c:(.text+0x0): multiple definition of `setreuid' /home/test/autobuild/instance-2/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libpthread.a(pthread_setreuid.os):pthread_setreuid.c:(.text+0x0): first defined here

Do you have a working version of uClib toolchain, to produce a smaller busybox selinux binary?

Thanks again for all the support and helpful guides.
[Android Software/Hacking General [Developers Only]] 7175:
Thanks. Yeah, unfortunately I ran into the same problem and haven't been able to get around it yet. We might consider emailing a uclibc mailing list and see if we can get an answer there. EDIT: I signed up for the uclibc mailing list and sent them a post with this error message we're getting. Hopefully we'll hear some good news. :fingers-crossed:

I do have some partially good news though. A musl-libc toolchain will compile busybox with SELinux support. This will make a smaller binary like uclibc. The reason it's partially good news is that there are some issues with usng musl-libc to compile certain applets in busybox. The compilation process gets

complicated because you gotta hunt down which applets are causing compilation errors, see if each problem can be fixed by including extra header files, and otherwise discard the applet from the compilation. On the positive side, all SELinux tools for busybox will compile with musl-libc, so you could make a separate busybox with just SELinux tools if you wanted to. That does sound cumbersome to use though.

EDIT: Got some great news!! The mailing list got back to me and pointed out the problem. It turns out that we need to compile the libselinux and libsepol libraries with uClibc before including them in the compilation of busybox. So if you go back to the libselinux* and libsepol* directories from the previous instructions I had on compiling SELinux busybox, just redo those steps using the uClibc toolchain instead. Busybox with SELinux enabled compiles just fine after that! :)
[Android Software/Hacking General [Developers Only]] amit.bagaria:
In fact, I actually did exactly what the mailing list guys has recommended. But still got into issues during ld. Have you tried these? Is it compiling fine for you? It also seems that libselinux also requires pcre libs.

However, I made some patches the uClibc source and built the toolchain. Now using this toolchain I am able to compile busybox with SELinux (the size is now 1.5MB). I guess it is now more manageable size. I think the size is still bigger than w/o SELinux, because of libpcre requirement.

For your reference, I have uploaded the toolchain here, that I compiled (after patching for multiple definitions of 'setresguid').
[Android Software/Hacking General [Developers Only]] 7175:
Oh nice. It's weird, I didn't run into any problems when recompiling libselinux and libsepol on my x86-64 laptop followed by busybox SELinux compilation, but when I try to do the same on my phone with arm, it throws some new errors related to this new libpcre requirement. I'd like to get this compiled on my phone cause it makes smaller binaries compared with my laptop. Could you post some instructions how you patched the uClibc source. That would be awesome!
[Android Software/Hacking General [Developers Only]] amit.bagaria:
I have added the libselinux, libsepol and libpcre in the toolchain itself, which can be found here. Using this, now I don't need to compile the libs separately.

Attached is the patch for uClibc.

PATH=~/arm-uclibc/bin:"$PATH"
LD_LIBRARY_PATH=~/arm-uclibc/lib:"$LD_LIBRARY_PATH"
make -j4 CC=arm-buildroot-linux-uclibcgnueabi-gcc CFLAGS='-Os -I /root/arm-uclibc/include' LDFLAGS='-static'
[Android Software/Hacking General [Developers Only]] bovirus:
Could you update busybox with latest 1.23.1 stable?

The busyboix is for arm device? Could create also for x86 (Atom) platform?

Can I propose to add as info in the first post the busybox version that you cpompiled (I believe that the current one availble on first post should be 1.2.30).

Thanks.