yashsingh1/xdaforums huggingface dataset:
[Xperia Tablet Z General] negrobembon:
Does it have white balance?
[Xperia Tablet Z General] mame3876:
wifi only

hi all

news regarding an update for wifi only or this new one is intended only for LTE version?
[Xperia Tablet Z General] Felimenta97:
Normally the WiFi version get it a bit later...
[Xperia Tablet Z General] mame3876:
ok, didn`t know that , i bought this device 2 weeks ago.

do you happen also to know if the delay in the rolling out among the various versions is weeks or months for example?

thanks
[Xperia Tablet Z General] venki5star:
Got the update for mine. I am from Australia.
[Xperia Tablet Z General] Felimenta97:
4.3 took less than a week, a 4.2.2 fw took almost a month between the models.
[Nexus 5 Q&A, Help & Troubleshooting] Tommmii:
Hi all,

the recent update to Maps (7.6.0) has broken Google Now, for me.

When I swipe to the Now screen and refresh it, I always get a message saying "Unfortunately maps has stopped."

Have uninstalled the update through Play Store, it's on 7.4.0 now, the error in Now has disappeared.

Any one else seeing this ???

Update :

Play Store is now offering Maps 7.6.1 which has solved the issue for me.
[Nexus 5 Q&A, Help & Troubleshooting] tfcdefoe:
I have the exact same issue and I get the error on both my Nexus 4 and Nexus 10. However, there's no error on my wife's Nexus 4 and also when I switch to her account on N10.
[Nexus 5 Q&A, Help & Troubleshooting] Ferfereh:
Unfortunately Maps has stopped

I am also experiencing the same thing on my Nexus 5. I think the problem started after updating to the latest Google search app.
[Nexus 5 Q&A, Help & Troubleshooting] jlevy73:
Yep, same except problem for me. Was on Purity decided to go back to Stock and confirmed the problem still exists.
[Nexus 5 Q&A, Help & Troubleshooting] tseangus:
As my experiencing, Maps (7.6.0) has broken in each minutes on both Galaxy Nexus and Samsung Note3. No error after uninstalled the map(7.6.0):eek:.
[Nexus 5 Q&A, Help & Troubleshooting] Tommmii:
I've updated to maps 7.6.1, issue is resolved.
[Samsung Galaxy Ace Plus S7500] L33TaS:
Hi, it happens alot for me when i try to install cwm and something, my odin stucks in half the way, i found out a trick

When adding to my one port it says:

<ID:0/008>

When adding to my another port it says:

<ID:0/009>

And the <ID:0/009> is the one that makes the odin don't stuck, i tried that. it worked for me thou.

WILL DELETE THIS THREAD IF IT'S NOT HELPFUL OR THERE IS ALREADY ONE

:cool:
[Samsung Galaxy Ace Plus S7500] j.posarekar70:
you don't have to do anything even if ODIN gets stuck for a while when adding .pda file at first port

its just get stucked for few around 5-10 second & then ready to flash rom...

so its just normal case where software loads a little bit, when add 500-1000mb file in it :)​
[Samsung Galaxy Ace Plus S7500] L33TaS:
No, i was holding the stucking around 1 hour, and the file was a cwm.tar...
[Samsung Galaxy Ace Plus S7500] vickyg.coolest:
you might have a driver issue
[JAM, MDA Compact, S100 General] mark buckle:
my friend has riecently bought the o2 Xda exec and it has a cool function on the camera, you can take a photo, and then it lets you connect another photo onto the end of that, meaning the picture is longer. does anybody know if this is pissible with the magician?
[G Pad 8.3 Q&A, Help & Troubleshooting] mike_1983:
I had stock installed, rooted and twrp install, I downloaded the update and now it only boots into twrp. So i tried factory reset and restoring a backup I had, still nothing. Just now I pressed advanced wipe everything except SD Card, now I have no OS :( And no backup to restore.

For some reason twrp doesn't recognise any micro sd card I put in, says it cant mount them.

I can't get adb working whilst in recovery. I just want to go back to stock.

Also holding down vol down and up to get into download mode doesn't work.

Thanks for any advice.
[G Pad 8.3 Q&A, Help & Troubleshooting] mike_1983:
Got it into download mode now somehow (rebooting from twrp instead of cold boot) and downloading the stock firmware from LG mobile support tool.
[G Pad 8.3 Q&A, Help & Troubleshooting] Trunkam:
same problem here.. how did you get to download mode? cannot find a way..
[G Pad 8.3 Q&A, Help & Troubleshooting] crissx:
1. Turn off the tablet. (from twrp menu )

2. Push vol+ and vol- same time.

3. Insert usb cable.

4. Release both buttons. Now you should be in download mode.
[G Pad 8.3 Q&A, Help & Troubleshooting] Palux:
hi mike_1983, but have you solved with this method?
[G Pad 8.3 Q&A, Help & Troubleshooting] crissx:
I was in same situation. And i solved installing stock room with LG Mobile Launcher.

Go in download mode, and then follow this method: http://xdaforums.com/showthread.php?t=2471370 is 100% working.
[G Pad 8.3 Q&A, Help & Troubleshooting] katsika:
dont update the official rom if you re rooted or you have a custom recovery, they ll brick your tablet. If you have access to recovery you can install a custom rom and there is no need to go back to full stock (unless ofc you want to keep the stock rom in which case you need to flash it using the lg mobile support tool)
[G Pad 8.3 Q&A, Help & Troubleshooting] mike_1983:
I think I did it by holding down vol up and vol down whilst in twrp, then pressing reboot, system (or perhaps pressing reboot system then holding them down). I'm not sure if the usb cable was plugged in or not. I tried holding down vol up and down from powered off, but it seemed to still always go into twrp.

Then you need B2CAppSetup.exe which is LGMobile Support Tool, you can then download the stock rom, it overwrites everything, like recovery and root.
[G Pad 8.3 Q&A, Help & Troubleshooting] Exoten:
Made the same mistake : said yes when the tablet proposed me to update. Booted in TWRP.

Tried to flash with support tool but it stops at 95% and tells me in german (!) to remove the battery and try again... I've tried many times (without removing the battery obviously), just the same.

And now I can't get out of the download mode. Everytime I plug the USB cable, it goes to download mode.

Any suggestion ?

EDIT :

I even tried this method : http://xdaforums.com/showthread.php?t=2622777

and it stops giving me a decompression error...

Edit 2 : it finally uncomressed corectly but i'm still stucked at 95% when installing : WPARAM_UPGRADE_ERROR

EDIT 3 :

Using the method http://xdaforums.com/showthread.php?t=2622777 and leaving default parameters : Korean language and country it finaly worked with the V50010A_00.kdz firmware.

My lg g pad is finally booting ! (the battery is totally drained)

Thanks to all !
[G Pad 8.3 Q&A, Help & Troubleshooting] Fbien:
Many Tanks to Exoten (and others) :highfive:

Same mistake... Same errors (no standard flash / method available)... Try method from Edit 3 and ... My wife is happy again (this is her tablet) :D

++ No Wipe data necessary - All data (SD and internal were kept)

+ the OTA upgrade was applied, even if I selected A version of KDZ (and not B version)

- I lost the root

F'bien
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] pmennen:
I'm getting ready to update my old ParanoidAndroid (with CWM v5.5.0.4) with the CarbonRom.

I've backed up all kinds of logs, settings, and data that I think I may want to restore with the new rom.

I've also made a CWM backup (although of course I hope not to use it).

My question is - should I format the system partition (from CWM, Mounts & Storage option) before flashing the new rom?

I've seen people say emphatically that to get a clean install you need to do this.

Yet I've seen other's write just as insistently that you should NOT format the system partition. Do they say this because it is too dangerous? If I format the system partition and then for some reason the new rom won't load, does that mean my CWM is wiped out, making it difficult to recover?

I think I do want the system format because I don't want a bunch of old files hanging around ... but I want to make sure this is not too dangerous.

I've also seen others who recommended also formating the boot partition. Is there any value in that? Sounds even more dangerous ... no?

~Paul
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] treacherous_hawk:
You can format system,data, internal storage and cache without any worries if you are on PA rom read install instructions in carbon rom thread after or before.
[Huawei Ascend P6, Mate] sisqoboy:
I am just about to fed up with my p6.

I had b111 and now I updated to b125.

Wi-Fi constantly drops...

Gps doesn't get fix just after restart the phone.

Front camera still doesn't work ("gallery has stopped ")

so I will return it.

does anyone have any experience about carphone warehouse warranty services or is there a huawei service in London?

thx!
[Huawei Ascend P6, Mate] sisqoboy:
And my phone doesn't get any b116 online update when I have the official b111 rom from Huawei site...
[Android Software/Hacking General [Developers Only]] daniel_hk:
[GUIDE] Porting Bluez to Marshmallow

Check the modified Bluez in my github.

It has been tested with Omni6 (Android-6.0.1_r3)

You have to remove system_bt in local_manifest.xml (similar to bluedroid, check post #1 for detail)

CM needs extra modifications. Will be available after testing.
[Android Software/Hacking General [Developers Only]] percy_g2:
Nice , Xperia Novathor devs also working on stable bluez :)
[MENTION=5265970]95A31[/MENTION]
[Android Software/Hacking General [Developers Only]] 95A31:
Nice guide :) In CM11 you need also revert this https://github.com/CyanogenMod/andr...mmit/763c68d048d268bd931dffa72000f52830ffe2d8 ;)
[Android Software/Hacking General [Developers Only]] daniel_hk:
Thanks! Patch in section 1.4 is another alternative for cm11. ;)
[Android Software/Hacking General [Developers Only]] 95A31:
Wops my fault :silly:, you have right :D
[Android Software/Hacking General [Developers Only]] k2wl:
although i dont have my previous device which has csr chip..but those still have csr will get greatly benefited ..your work is incredible......god bless u!!!

keep the good work!!!
[Android Software/Hacking General [Developers Only]] 95A31:
static void pin_request_cb is defined in external/bluetooth/bluez/android/client/if-bt.c
[Android Software/Hacking General [Developers Only]] daniel_hk:
yeah, it is also defined in if-bt.c but if you check android/Android.mk, only haltest use it. If you want to build haltest, you need to change if-bt.c too.

Take a look the file android/Android.mk which is the make file for android. bluetooth.default.so which cm11 refered to, use the definition in hal-bluetoth.c.
[Android Software/Hacking General [Developers Only]] 95A31:
Forgot my unknowledge/newbie but I can not find it in hal-bluetoth.c (In BLueZ git)
[Android Software/Hacking General [Developers Only]] daniel_hk:
It's in the android folder. In the same place as Android.mk. ;)

If you can't find inside the file, you might have the old version. Try include the project in manifest and sync again.

I have a suggested local_manifest in post #1.

Good luck!
[Android Software/Hacking General [Developers Only]] 95A31:
I mean in hal-bluetooth.c, can you tell me the line in this version ot the file? (I know that it is a retarded question but I really can find other occurences of pin_request_cb outside handle_pin_request function) I am working on BlueZ git so I am working on lastest version :confused:
[Android Software/Hacking General [Developers Only]] daniel_hk:
All the changes are listed in post#1.

In line 239 of you link, there is the line:

bt_hal_cbacks->pin_request_cb(addr, name, ev->class_of_dev);

It is a callback. The definition is in cm11 which had changed. That's why we have to add one more argument. (or revert the cm11 commit as you said)

The definition if-bt.c which is a client, is for testing. It has to define the callback which is required in int. Got it? ;)
[Android Software/Hacking General [Developers Only]] 95A31:
Get it :good:
[Android Software/Hacking General [Developers Only]] 95A31:
Ok, I have a nice bootloop: http://pastebin.com/QcZbEkfx Guys some ideas ?
[Android Software/Hacking General [Developers Only]] daniel_hk:
I have checked your logcat. There is no management interface log. The kernel backport on blietooth subsystem is probably failed.
[Android Software/Hacking General [Developers Only]] 95A31:
I foud this dependence in my case: WLAN init need that BT chip is initialized because WLAN ask clock to BT. The intoduction of import init.bluetooth.rc broke this dependence. Fu*king details :cyclops: I hope to save debug time to someone :D
[Android Software/Hacking General [Developers Only]] jjm34:
Thanks, very helpful guide. Following this I was able to get BlueZ working on MSM7x27a. However, instead of dropping the backport sources in the kernel tree I followed this documentation to build the backports as external modules, which looks like a cleaner way to me. This requires building the kernel without BT (and, in cases like this, patching the source to remove some dependencies on built-in BT). This leaves the kernel sources (mostly) untouched, and makes adapting the backport sources easier because you can separately build the modules without doing a full kernel build.

The modules can then be built like this:

# clean output files
make -C kernel/backports ARCH=arm CROSS_COMPILE="arm-eabi-" KLIB=$OUT/obj/KERNEL_OBJ KLIB_BUILD=$OUT/obj/KERNEL_OBJ mrproper

# configure
make -C kernel/backports ARCH=arm CROSS_COMPILE="arm-eabi-" KLIB=$OUT/obj/KERNEL_OBJ KLIB_BUILD=$OUT/obj/KERNEL_OBJ menuconfig

# build
make -C kernel/backports ARCH=arm CROSS_COMPILE="arm-eabi-" KLIB=$OUT/obj/KERNEL_OBJ KLIB_BUILD=$OUT/obj/KERNEL_OBJ
[Android Software/Hacking General [Developers Only]] daniel_hk:
Yeah! Yours seems better. I was messing with the kernel for a while before backport. Traditional backport kill my WiFi so I did what I knew. I will try yours later. ;)

Any other success would be cheerful.
[Android Software/Hacking General [Developers Only]] daniel_hk:
Nice!

There is another way. I only changed a few files in Bluetooth/jni. No need to change Settings, libhardware and frameworks.

This is my patched Bluetooth packages, View attachment Bluetooth.zip
[Android Software/Hacking General [Developers Only]] 95A31:
Thanks I will check :) (I done in this way because I am lazy to fix code so choose brute approach xD)
[Android Software/Hacking General [Developers Only]] daniel_hk:
New commits always come. It is better touching the source lesser. Dealing with conflicts are even annoying.
[Android Software/Hacking General [Developers Only]] Andrewasth:
This is aosp bluetooth package? Have you only changed jni files or something from src as well? Because there also changes in abstraction layer in bt service (just an example). Can you provide a diff or a patch?
[Android Software/Hacking General [Developers Only]] daniel_hk:
Yeah, this is base on the AOSP Bluetooth package. The one from CM cause crash loop. I start this first and if not working, I would start with the one from CM again. This is a seperate service and is the only change required. Just replace it with the CM package will do.

I followed the build errors and port the call backs required by CM. Only change 2 files in jni and another 2 in btservice. Further patching may requrired but there are only few functions left. Actually I have patched a little bit again for the new CM commits.

If you needed, I can attach the new patch when return home. I might upload it to my github when I have time. For the time being, you may clone the AOSP package to get the diff.

Edit: This is the new View attachment Bluetooth.zip. This Bluetooth patch is working on my cm11 and carbon builds since day one.

Good luck! ;)
[Android Software/Hacking General [Developers Only]] Andrewasth:
I have cloned aosp package but I want to implement it on cm. So I will wait for your patch :) But it won't work on cm yet right? Implementing your modifications to cm bt package is enough or it needs further modification?
[Android Software/Hacking General [Developers Only]] Codename13:
Do you know if there are any major Bluetooth differences between Android 4.3 and Android 4.4? I have an msm7x27a device for which I develop CM10.2, and I was wondering how I could get Bluetooth working. My device's stock ROM is ICS, so I came up with 3 potential solutions to get Bluetooth working on CM10.2 - port the Bluedroid driver and modify the kernel board files as necessary (which is proving to be tricky), port a 3.4 kernel (with help from some devs like TheWhisp who have ported 3.4 kernels for their devices. This one would probably be the hardest to do though), or port Bluez to CM10.2. It would be much appreciated if someone could help me out here. Would I have to change any steps to get this to work on CM10.2?
[Android Software/Hacking General [Developers Only]] daniel_hk:
There is already a successful port for msm7x27a on the last page: http://xdaforums.com/showpost.php?p=50634526&postcount=18

You may ask him for detail.

Good luck!;)
[Android Software/Hacking General [Developers Only]] Codename13:
I started with porting Bluez to CM10.2 by just doing step 1 (1.1 to 1.4) for now, just to see if I could get it to compile. Unfortunately, I'm getting this error

. I don't really care about the warnings, but how could I solve the error? I didn't change any code in the static 'config_hci_snoop_log', so what's causing the issue? Could the problem be caused as a result of using the latest BlueZ source (5.16)?
[Android Software/Hacking General [Developers Only]] alwaysadeel:
thnx for ur work.

i used this attachment to build carbon with latest bluez. i wanted to know which files u actually changed. running diff with aosp packages/apps/bluetooth gives a very long file. is it aosp based?

Sent from my Nexus 7
[Android Software/Hacking General [Developers Only]] daniel_hk:
I'm using 5.16 too. The error you got is not related to cm10.2. Check the definition of bt_interface_t (in android/hardware/bluetooth.h), config_hci_snoop_log is missing in the definition. You might have messed up your bluez source. It's there in the original source.

I started with the aosp packages/apps, only changed a few files. File in jni might change a lot. I have added a few changes since then. Just to pass cm11 build (I use the same codes for carbon too). New View attachment Bluetooth.zip

Good luck!
[Android Software/Hacking General [Developers Only]] Codename13:
What do you mean about config_hci_snoop_log missing in the definition? There are numerous search results for bt_interface_t in the bluetooth.h. Also, are any changes to the Bluetooth app or Settings app required?
[Android Software/Hacking General [Developers Only]] daniel_hk:
I have already listed all the changes required. You probably need to modify Bluetooth app but the error you got is in bluez (bluetoothd). The source from bluez has no problem. This is basic programming... bt_interface_t is a struct which should have the entryconfig_hci_snoop. The error message already told you that.

If you still don't know, I don't know how to help. You need to read some basic c programming first.

Good luck.
[Android Software/Hacking General [Developers Only]] alwaysadeel:
i was getting errors similar to these before using ur Bluetooth app. these r specific to CM

Sent from my Nexus 7
[Android Software/Hacking General [Developers Only]] Codename13:
Wait so are changes to the Bluetooth app (packages/app/Bluetooth) required? I see that there are no such changes in the OP, but some of the posts on the past few pages have been about the Bluetooth app and modified files. So are Bluetooth app changes required?
[Android Software/Hacking General [Developers Only]] brianmay27:
Hey Daniel,

Thank you so much for your post. This is exactly what I was looking for and it has helped me a great amount so far.

If anyone can help me currently, I am receiving an error on compile that sdp.h under bluez/lib is unable to find the import Bluetooth/Bluetooth.h I am unsure where it is trying to reference to and could use some help figuring out which Bluetooth.h it is trying to reference to.

Thanks in advance
[Android Software/Hacking General [Developers Only]] percy_g2:
link to your sources
[Android Software/Hacking General [Developers Only]] brianmay27:
Wow, Thanks for the quick reply and forgive my newbish reply. I just began Android development last week and although I though my C++ knowledge was advance, College never gives you projects of this magnitude.

Anyway I did a find and the results are

./external/bluetooth/bluez/lib/bluetooth.h

./external/bluetooth/bluez/android/hardware/bluetooth.h

./external/bluetooth/bluez/android/bluetooth.h

./external/bluetooth/bluez/obexd/client/bluetooth.h

./kernel/samsung/smdk4412/include/compat/net/bluetooth/bluetooth.h

./kernel/samsung/smdk4412/include/net/bluetooth/tizen/bluetooth.h

./kernel/samsung/smdk4412/include/net/bluetooth/bluetooth.h

./hardware/libhardware/include/hardware/bluetooth.h

In which I take it you are refering to the bluez/lib?

Oh and sorry, my source is Dirty Unicorns kitkat with device t0lteatt
[Android Software/Hacking General [Developers Only]] brianmay27:
I figured it out.

Now Im stuck with the kernel and backporting. I cherry picked the code and have compat files in the kernel but Im stuck trying to link them. IE I am getting an error that it can not find backport_alloc_workqueue which was defigned in the workqueue.h. I know backport_alloc_workqueue is defigned in compat-3.3 but it does not find it.

Thanks
[Android Software/Hacking General [Developers Only]] brianmay27:
Ok, Managed to learn through my failures. I now have working backported drivers however something weird is going on. My process is as follows:

modprobe hci_uart
modprobe Bluetooth
echo "1" > /sys/class/rfkill/frkill0/state
hciattach /dev/ttySAC0 bcm43xx 4000000
hciconfig hci0 up

But here is the weird part. If I do a hciconfig -a hci0 I get this

hciconfig -a hci0
hci0: Type: BR/EDR Bus: UART
BD Address: 43:34:B0:00:00:00 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:7419 acl:37 sco:0 events:151 errors:0
TX bytes:2834 acl:36 sco:0 commands:75 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: 'BCM4334B0 37.4MHz Class1.5 Samsung D2'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.0 (0x6) Revision: 0x40f
LMP Version: 4.0 (0x6) Subversion: 0x410d
Manufacturer: Broadcom Corporation (15)

Look at the BD address, its a default value. If I go any further to start bluez I get a Bluetooth address mismatch

I have no idea what is wrong with it, I am able to scan with the hcitool and get devices back and ping them with l2ping so the chip is working. Anyone have any ideas? Ive tried to set the address with hciattach with no luck
[Android Software/Hacking General [Developers Only]] daniel_hk:
Boardcom chips have bluedroid support. I assume you are trying to test bluez. I didn't try other chips before. Other than the material already posted, there would be little to help.I suppose you had followed the bluetooth.c in your device tree. The sequence should init your chip properly.

The example from Bluez for Nexus4 might be a place for you to look into.

I remember, there is the program (something like bdAddrLoader) starting in init.mako.rc. I think it read a file in /efs (or similar partition) for the bdadress. Most of the devices share the same mac address from WiFi.

Take a look at your old device tree's init.<>.rc. See if there is similar code.

Good luck!
[Android Software/Hacking General [Developers Only]] reekotubbs:
Hello daniel_hk, I hope you are still working on this. Can we just flash this via cwm?