yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] Failrunner:
I love the new device. However I agree about the screen. It's honestly not that much better looking to me as far as the resolution goes. I have also noticed the keyboard issue. I had the same issue on the old n7. I'm not sure how one more camera is an issue. I don't notice the charging issue because I charge overnight. I personally like the thinner feel. I don't why. The thicker feel is easier to hold but I like it i guess because it adds to portability. My expectations were exceeded. I wasn't even gonna get the new one but I'm glad I did. Mirroring, better gaming, better portability. Less stutters. Best of all.. No stupid Tegra processors! I've grown to hate them!
[Nexus 7 (2013) General] rmkilc:
Complain to the developers of flipboard. It's not the devices fault. The Android SDK has all the tools available to make a good layout on all screen sizes. This is a huge advantage over the iOS SDK, which only has two sizes (3 if you count short and tall phone). Remember, the iPad Mini displays full sized iPad apps, and just like Steve Jobs said, you have to use sandpaper to sand down your fingers in order to use it. Android's method is far superior, and Apple is even trying to move in that direction by making the OS scalable in the future. As for apps developed poorly, please contact their developers and don't fault the device.
[Nexus 7 (2013) General] chiikko561:
I had the n7 og since it came out and i have n4 and I'm excited to buy n7 2013 tomorrow
[Nexus 7 (2013) General] Solutions Etcetera:
But there IS an issue with the Nexus 7 where it is not always treated as a tablet with tablet optimized apps. You even occasionally see tablet apps not being available for the Nexus 7. I don't know who's fault it is, but it is present on the device, so it is an issue with the device.

One reason I upgraded was the hope that the higher rez might help with this, but so far I haven't noticed any improvement.
[Nexus 7 (2013) General] Nebucatnetzer:
7-8" Tablets are IIRC a separate category so it's still an app problem.
[Nexus 7 (2013) General] Cubfan99:
Can't do words with friends in landscape like on the Nexus 10. But that has to be the buggiest app in history, so no surprise.
[Galaxy S III Accessories] kazuki1:
Hey all, I'm trying to look for a new housing+lcd for my tmobile galaxy s3. Just wondering are all housings and lcd interchangeable for this phone? Or do I need to make sure it's for the tmobile variant? Thanks
[Galaxy S III Accessories] zolo185:
Ur fine buying a normal housing . No need for a tmobile "specific" housing
[General Questions and Answers] dukeofducks:
How important is it match the voltages in replacement batteries? I thought it would need to be exactly the same?

I'm replacing a battery in my friends Huawei Ascend P1 U9200. It's current battery specs are:

HB4Q1 Battery, 3.7v / 1670 mAh

However, there is also listed by many resellers another battery which they say is also for U9200:

HB4Q1HV Battery, 3.8v / 1800 mAh.

The HV model seems better for capacity but I'm worried the different spec (voltage) may damage the phone. I'm being a bit paranoid because it's not my phone and I'd feel bad if I fried it :silly:
[General Topics] KingVidal93:
Thanks!!! i will follow these tips :good:
[One (M7) Q&A, Help & Troubleshooting] Grooov3:
Hi Guys,

is it possible to import the s health app from a samsung smartphone to the htc one ?

when not anyone knows a good alternative app ?

greeetings
[Nexus 4 Q&A, Help & Troubleshooting] nickslg:
Running 4.3 stock and every time I try a different kernel I get horrible screen flicker how do It to run smoothly like stock kernel
[Nexus 4 Q&A, Help & Troubleshooting] szucsgf:
What kernel are you using, including version number? For now it might help to disable hw overlays in developer options.
[Nexus 4 Q&A, Help & Troubleshooting] nickslg:
I just downloaded semaphore kernel v1.5 for jb 4.3
[Nexus 4 Q&A, Help & Troubleshooting] nickslg:
Thanks .....I checked HW overlays now runs smooth
[Nexus 4 Q&A, Help & Troubleshooting] szucsgf:
From semaphore kernel op:

1.5.0 (26/07/2013)

- Rebased on JB 4.3 (JWR66V) kernel. It should be used only on stock JWR66V.

Are you using a JSS15J build of 4.3? If so, that is your problem. Check Settings - About phone.
[Nexus 4 Q&A, Help & Troubleshooting] nickslg:
JWR66V
[One (M7) Q&A, Help & Troubleshooting] hpsauce37:
Is this service already activated on all htc ones?

On my previous gs4, purchased sim free and not from specific networks that support this there was a code that you can enter into the dial pad to get to a menu where you can activate it by default.

My network (3 uk) offers the hd voice service but because my device was not purchased direct from them i dont know if it has been enabled on this device.

Anyone know a way to check or enter the AMR-WB (think thats what its called) menu.

thanks
[One (M7) Q&A, Help & Troubleshooting] hpsauce37:
No one else thought about this?
[Nexus 7 (2013) General] chris.wueste:
This is in no way the only way to go about getting your Nexus 7 back to stock. In my opinion however, it is the most tried and true and reliable method of getting it done. This is the way I like to do things and I know there are others that feel the same. This guide is for those people. If you would rather use the flash-all.bin script then be my guest. There are also toolkits that will get the job done. I hope this can help some of you.

First of all, I am in no way responsible for anything you do to your tablet period.

I have seen a couple of people asking how to return the Nexus 7 to stock after it has been unlocked, rooted and so on, so I figured I would write a quick guide as its super easy to do. Also, please make sure you make a backup of anything you don't want to lose. This is important.

Before you begin, please make sure you have ADB and Fastboot drivers installed and working.

1) Download the factory image for the Nexus 7 at here.

2) Extract the factory image into the same directory as your ADB and Fastboot executibles (e.g. "\android-sdk\platform-tools")

3) Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type

adb reboot bootloader

If your device is powered off, press and hold the volume down key and the power button simultaneously. After holding both buttons for a couple of seconds, your bootloader should launch.

4) Type

fastboot flash bootloader bootloader-flo-flo-03.14.img

5) Next type

fastboot reboot-bootloader

6) Now type

fastboot -w update image-razor-jss15j.zip

7) Optional: If you would like to relock your bootloader for warranty or security purpouses, make sure you are in your bootloader screen again and type

fastboot oem lock

8) If your tablet hasn't already rebooted automatically, type

fastboot reboot

That should do it. You should now be on stock Android 4.3 and ready to send in your tablet for warranty purposes if you so desire.
[Nexus 7 (2013) General] miou:
There already has a post that can do this

http://xdaforums.com/showthread.php?t=2381582

:good:
[Nexus 7 (2013) General] chris.wueste:
This is a different way of doing things. This is the way that Google themselves provide to get your tablet back to stock. This is the way I prefer to do things as I like to be responsible for the code that is entered in my tablet. Maybe I'm just the weird one here and I am not saying they are wrong, just not a fan of the toolkits.
[Nexus 7 (2013) General] sfhub:
The only difference between this and flash-all.bat in the Google-provided factory restore is the optional fastboot oem lock

Not sure about your system, but (unless fastboot -w come back with error) on successful

fastboot -w update image-razor-jss15j.zip

My tablet reboots automatically, so the subsequent

fastboot oem lock

fastboot reboot

won't be run while the tablet is in fastboot mode.
[Nexus 7 (2013) General] geckocavemen:
In step three it says to press both volume keys and power to get into the bootloader but on our Nexus 7 I thought it was only volume down and power to get into the boot loader.
[Nexus 7 (2013) General] di3cbl:
Just reboot back into the bootloader and lock it then
[Nexus 7 (2013) General] sfhub:
Yes, I understand what to do if I want to lock the bootloader.

What I was pointing out is the only difference between the instructions provided and what the flash-all.bat script (included by google in the factory image restore) does already is the "optional" step of locking the bootloader.

So the only difference actually doesn't work using the instructions here, you have to reboot the bootloader, which is exactly the same you would have done if you ran the flash-all.bat script and wanted to lock.

So this whole post could have been written:

1) adb reboot bootloader

2) run flash-all.bat script

3) optional - relock bootloader

adb reboot bootloader

fastboot oem lock

fastboot reboot​
[Nexus 7 (2013) General] chris.wueste:
You are correct. About to correct this in the OP.
[Nexus 7 (2013) General] chris.wueste:
I have had trouble in the past with the flash-all.bat script. My Nexus S never would work right with it and so ever since, I have always used the manual entry of the code. Takes 20 seconds to run all of it. Not too inconvenient for something I know will work.
[Nexus 7 (2013) General] cobyman7035:
ot: what should i tell the store when i go back to 'exchange' the tablet, once i do OP's procedure, will the store test it out and find no faults to exchange it?

tell them, wifi keeps dropping?

random reboots

can't update apps via googleplay store?
[Nexus 7 (2013) General] danvee:
The second one is the hardest to reproduce, and they're not going to stand around and wait for it....
[Nexus 7 (2013) General] gleggie:
Does this guide still apply to the latest Android 6.0 Factory image? :D
[Nexus 7 (2013) General] yosmokinman:
^Yes.

The bootloader name as well as the image is obviously different so change that. The bootloader didn't change since at least 5.1 (04.05) so if you're running that you don't need to flash it the md5's are the same.
[Micromax A116] Rishav_91:
I am facing an unusual issue with my CHD. WiFi works perfectly but when I switch to GPRS, i am not able to access internet.As a result whenever i am outside my home i end up being unable to use any internet based services like whatsapp and navigation. My phone is not rooted. I have upgraded JB4.2.1 feom miceomax sercicw centre.Please Help
[About XDA developers] snapper245:
I know it is no big deal, but maybe we should add the Cingular logo as a valid carrier for the USA.

Also, how about adding the label Siemens SX66 as a model number so my ROM versions could be filled out there (instead of on my signature)...

System admins, can I assist in this effort?
[About XDA developers] Bubisch:
Yeah, and we could also add Blue Angel, Alpine and Magician to the used Devices.
[Nexus 4 General] sicto:
So guys this is thread about benchmark scores on android 4.3. Here are some of them

http://www.youtube.com/watch?v=95O8C8NGp5k - Antutu, weird score, don't know why

http://www.youtube.com/watch?v=q5E5PdyHdXo - Quadrant, not really good

http://www.youtube.com/watch?v=akNLFOUqAFQ - Geekbench 2

Feel free to post your screenshots or videos ! :)
[Nexus 4 General] simms22:
use this thread for benchmarks http://xdaforums.com/showthread.php?t=1967843

there are other "4.3 benchmark" threads started too, but they all eventually posted in the original benchmarks thread. keep it there, instead of having many benchmark threads.
[One (M7) Q&A, Help & Troubleshooting] Fatelord:
Here are some Bootloader unlocking issues I ran into, if you would share plz to know if they were specific to my experience ..

- HTC weather app unable to contact the location the service to update my location ... turning off wifi and turning on mobile data seems to solve the problem temporarily on my Blinkfeed page it shows "my location" not the actual city I live in as it used to when the bootloader was locked, this one in particular is quite annoying ..

- Powersaver mode doesn't reliably turn off vibration function on the keyboard, not a biggie but weird enough .

- Many HTC apps disappeared, I assume this happens to everyone ?
[One (M7) Q&A, Help & Troubleshooting] Root-Maniac:
Sorry my friend, Unlocking the bootloader does not do any of this, it simply unlocks the device allowing us to flash custom recovery and root the device.....
[One (M7) Q&A, Help & Troubleshooting] Fatelord:
So calculator and HTC flash didn't disappear after unlocking and rooting the device ?

I am talking about an unbranded version of course ..
[One (M7) Q&A, Help & Troubleshooting] gunnyman:
Yes. Apps disappear but your other problems are not bootloader related
[Xperia Tablet Z General] themikem:
Thanks to mamenyaka's efforts, we now have a running version of Ubuntu Touch on the Xperia Tablet Z. I'm attempting to do some customization of this kernel (such as add btusb support), but I'm not all the familiar with the Cyanogen build process. So looking for a little help here.

I've been following these instructions:

http://wiki.cyanogenmod.org/w/Build_for_pollux_windy

Now, I think the process is as follows:

Setup environment according to the wiki, up through the "repo init" step.

Add the "local_manifest.xml" from https://github.com/mamenyaka/android/ to ~/android/system/.repo/local_manifests

Run a repo sync in ~/android/system.

and this is where I get a bit confused. I _think_ the next step is then to run source build/envsetup.sh and breakfast pollux_windy, and then proceed according to the instructions as usual, excepting extracting the blobs. I think those are already included.

However, can someone confirm this? Or is there a step/steps I'm leaving out?

Thanks.

PS - yes, this should probably be in the dev forum, but the post count rules are forcing me to post it here...
[Xperia Tablet Z General] mamenyaka:
If you want to build Ubuntu Touch, you should follow the porting guide.

You can't mix the two. The CM repo init and ubuntu's phablet-dev-bootstrap (ubuntu's repo init) use very different manifest.xmls. And if you want to build CM (advised if you never built android from source), you don't need the repos from my github.

Next thing: breakfast. It is a good to use when you build CM, but it's not good for building Ubuntu Touch. Breakfast adds CM repos specific to your device in a file in .repo/local_manifest (roomservice.xml). For Ubuntu Touch you don't need all of the device specific repos and you also need to apply some modifications in these repos (which I already done), and to use them, you will need to add the repos manually (local_manifest/local_manifest.xml, similar to roomservice.xml, but I prefer this file, because roomservice.xml is related to breakfast), so no breakfast needed.

Then simply repo sync to get the new repos.

The extra blobs are included thanks to TheMuppets repos.

To start building, simply $ . build/envsetup.sh and $ brunch pollux_windy. But all of this can be found in the guide or on CM wiki.

For building Ubuntu Touch you need a few extra things mentioned in the guide, like the phablet tool, and you need to update the ubuntu/platform-api bzr repo (bzr pull) - this isn't done by repo sync because it isn't a git repo, it's ubuntu's bazaar.
[Xperia Tablet Z General] themikem:
Okay, thanks for pointing me in the right direction. Thought I had to use CM build instead to use your repos. That's why this thread is here. I'd like to get instructions out here that could decrease the learning curve on some of this.

Are you aware of the state of CM on pollux_windy? I notice that Ubuntu has breakfast in their official porting guide now. Would you expect that to work, or are there further changes in your repositories to enhance their work?

In other words, Ubuntu's guide suggests doing a "breakfast pollux_windy", "repo sync", some tweaks, and then a build, under the Automatic build section.

I think your repo would work with the process under the "Manual (deprecated)" section. Is there a reason to use one over the other? Have you already integrated the required modifications in your repos, for example?

Sorry if this is all a bit pedantic. Just trying to come up to speed on the build process for all of this. I've built many a linux kernel, but I'm not at all familiar with this build process.

Thanks again for your help.
[Xperia Tablet Z General] mamenyaka:
Don't worry, I am here to answer your questions.

So, breakfast in Ubuntu Touch is good when you want to start off a brand new port.

The advantage of using my repos and using the manual method is that I already integrated the required modifications and, most importatnly, the image builds. Simply using the CM repos, you would get build errors, which are fixed in my repos; for example, removing the android parts.

Also, if you are interested, you could join this group.
[Xperia Tablet Z General] themikem:
Thanks for the tip. It worked!

For the record, it turned out to be this simple:

(~/phablet is arbitrary)

mkdir ~/phablet && cd ~/phablet

phablet-dev-bootstrap ~/phablet

repo sync

Add ~/phablet/.repo/local_manifests/local_manifest.xml from: https://github.com/mamenyaka/android

repo sync

. build/envsetup.sh

brunch pollux_windy

...and then flash the files from $OUT (~/android/system/out/target/product/pollux_windy)

Also note that I had a terrible time making git work through my NAT. Tried both a hardware router (Cisco) and my standard Vyatta VM. Ultimately had to put my build machine directly on a publicly-routable IP to make it go. If you're having problems with Git on 13.04, it could be the same issue. I'm not aware of any other fix, other than finding some way to switch the build system to http:// instead of git://

Now off to reconfigure the kernel. This should be interesting...
[Xperia Tablet Z General] mamenyaka:
One thing, without this you won't be able too boot.

You need to replace boot.img from the .zip with ubuntu-boot.img from $OUT and rename, of course, to boot.img.

ubuntu-boot.img should be bigger in size.
[Xperia Tablet Z General] telx85:
Hope this is the right place, but am I correct to assume that its possible to run Ubuntu Touch on the Xperia Z Tablet?

If so are there any tutorials on this?

Tel'X
[Xperia Tablet Z General] mamenyaka:
You gotta be kidding, right?

http://xdaforums.com/showthread.php?t=2336018
[Xperia Tablet Z General] telx85:
Nope, but thanks for that.

Looks very promising.
[Xperia Tablet Z General] Trevor Chuah:
I have some questions, for example I want to try build the ubuntu touch to a new port (actually not new port, just the progress of development of my phone is held on), I just refer to your local manifest.xml file? Sure I know need to change to device specific repo, I have it on other developer github.

Just the question is, how do I recognise which part is belong to android parts and remove them? Or which part should be remained?
[Xperia Tablet Z General] mamenyaka:
You have a cm.dependencies file in your device's repo which tells what other repos it needs (for example kernel).

You can instantly remove any android app related repo (like android_packages_apps_FMRadio).

But if you tell me what phone, I can give you some hints.
[Xperia Tablet Z General] Trevor Chuah:
The phone I'm using is Xperia S. The developer has his github name OpenSEMC.

Thank you.
[Xperia Tablet Z General] mamenyaka:
You could start over from scratch. Just fork the CM repos. The OpenSEMC repos are not really ubuntu touch oriented.
[Xperia Tablet Z General] Trevor Chuah:
Okay. So basically the post #5 is applicable to every phone right?

I just follow it and modify the

1) local manifest to correct repo

2) remove the android part

Right?

I will try it.

Thank you.
[Xperia Tablet Z General] Trevor Chuah:
May I ask?

If I use phablet-dev-bootstrap, it will follow the android.git in http://phablet.ubuntu.com/gitweb right?

I did it, and

I checked the default.xml inside the android repo, to roughly compare with the file synced into local.

I found that it has many thing missing, for example the following:

<project path="external/mockwebserver" name="CyanogenMod/android_external_mockwebserver" />
<project path="external/mp4parser" name="CyanogenMod/android_external_mp4parser" />
<project path="frameworks/opt/inputmethodcommon" name="CyanogenMod/android_frameworks_opt_inputmethodcommon" />
<project path="frameworks/opt/mailcommon" name="CyanogenMod/android_frameworks_opt_mailcommon" />

and many of them.

Is it ubuntu automatically not download these file since they are not important?
[Xperia Tablet Z General] mamenyaka:
Be sure to check out the phablet-saucy branch of default.xml, that's what phablet-dev-bootstrap pulls.

---------- Post added at 11:40 AM ---------- Previous post was at 11:30 AM ----------

Mostly right, but there is always something extra that needs to be done with every device.

Be sure to get the sony proprietary blobs from TheMuppets on github and post any questions, errors you need help with.
[Xperia Tablet Z General] Trevor Chuah:
The following is my local_manifest.xml file

<project path="device/sony/common" name="OpenSEMC/android_device_sony_common" remote="github" revision="cm-10.1" />
<project path="device/sony/nozomi" name="OpenSEMC/android_device_sony_nozomi" remote="github" revision="cm-10.1" />
<project path="device/sony/fuji-common" name="OpenSEMC/android_device_sony_fuji-common" remote="github" revision="cm-10.1" />
<project path="device/sony/qcom-common" name="OpenSEMC/android_device_sony_qcom-common" remote="github" revision="cm-10.1-legacy" />
<project path="kernel/sony/msm8x60" name="OpenSEMC/android_kernel_sony_msm8x60" remote="github" revision="cm-10.1-legacy" />
<project path="vendor/sony" name="OpenSEMC/proprietary_vendor_sony" remote="github" revision="cm-10.1-lagacy" />
<project path="hardware/sony/DASH" name="OpenSEMC/android_hardware_sony_DASH" remote="github" revision="cm-10.1" />
<project path="hardware/qcom/media" name="OpenSEMC/android_hardware_qcom_media-legacy" remote="github" revision="cm-10.1-legacy" />

I referred to your local_minifest.xml and the original author xml file and conclude this.

I do not know is it correct or not.

May I ask, will the recovery automatically add into the compile device image? What will it use? CWM?
[Xperia Tablet Z General] mamenyaka:
I think you should go with CyanogenMod for all repos except vendor, and TheMuppets for the vendor/sony (revision=cm-10.1 for all) if you want to start clean. Then just follow the porting guide.

It will use CWM.
[Xperia Tablet Z General] Trevor Chuah:
But CyanogenMod (FXP) did not publish CM10.1 for Xperia S, heard that they do not fix for the display.

Therefore I do not know whether if use the CM repo, what should I modify for the video to display.

Still newbie...:D
[Xperia Tablet Z General] mamenyaka:
I don't know much about nozomi. There exists the CM 10.1 repo for nozomi, but true, there is no cm-10.1 release.

You might have to experiment a little, stuff like common, qcom, DASH are available in CM, but if they have device specific fixes, than it may be the only route to use OpenSEMC repos.
[Galaxy Note 8.0 (Tablet) General] hertsjoatmon:
Just sat here adding some colour to a sketch and wondered if l was using the best methodology.

l sketch,

add a layer, draw the base colour

add a layer, add detail

add a layer, add shading / shadows

I adjust the opacity of the layers until I am happy with the result, or give up on the process half way through.

if I'm doing a comic style drawing, l will add a layer to do my ink outline before doing my colouring.

I'm struggling though. I've always been good with pencils and sketching, but I'm struggling to find a colouring technique I'm comfortable and happy with in the digital medium.

what process do you go though to build up a drawing?
[Galaxy Note 8.0 (Tablet) General] hertsjoatmon:
http://blog.spoongraphics.co.uk/articles/20-tutorials-for-learning-digital-painting-techniques
[Galaxy Note 8.0 (Tablet) General] Slipurson:
Always wanted to be able to draw, and after a few hundred games of Draw Something it just made me want to learn even more, will check out the link and see if i can learn anything :)

Might take a while before my work shows up on XDA tho :p