yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] wwsummersjr:
I used a Sony BDPS2200 Blu-Ray player to screen mirror Netflix from my S4 to BR/TV using T-Mobile unlimited data plan. I recently thought I could continue to do so with my Nexus 6 (S4 shot craps), but only to find out not only do I need a Chromecast, but also need cable/WiFi (found that out after buying a CCast). Cannot use phone unlimited data now. Google suckered me. Contemplating going back to Samsung.

:(

---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------

I used a Sony BDPS2200 Blu-Ray player to screen mirror Netflix (Netflix did not block) from my S4 to BR/TV using T-Mobile unlimited data plan. I recently thought I could continue to do so with my Nexus 6 (S4 shot craps), but only to find out not only do I need a Chromecast, but also need cable/WiFi (found that out after buying a CCast). Cannot use phone unlimited data now. Google suckered me. Contemplating going back to Samsung.
[Google Chromecast] bhiga:
If you could screen-mirror to your Blu-ray player, why can't you screen-mirror from your Nexus 6? Does the Nexus 6 no longer support Miracast? It's been built-in since late (4.2/4.3) Jellybean.

You *might* be able to use your phone's hotspot, but it depends on whether you can talk to Chromecast while simultaneously using the hotspot (ie, does your phone also look like a device on its hotspot LAN). Sometimes it requires a third device to control Chromecast.

Also, your Blu-ray player doesn't support Netflix natively??
[Google Chromecast] wwsummersjr:
The whole point is I was able to use unlimited data from Samsung Galaxy S4 phone (not hot-spot which is limited) with Netflix app on phone. Each (S4 phone and Sony BR player) had screen mirroring mode that would enable connection to my TV. If I use Netflix embedded on a blu-ray player or TV, it must have separate broadband. This is also the problem with the Google Nexus 6 and Chromecast. Must have stand alone broadband wifi (not the unlimited data on my phone).
[Google Chromecast] bhiga:
I see on the data access part, I'm a bit confused on the BR player's involvement.

Were you screen mirroring from the S4 to the BR player?
[Google Chromecast] wwsummersjr:
Yes, I was screen mirroring from S4 to Sony BR player.
[Google Chromecast] bhiga:
I see.

I read [Q] Nexus 6 Miracast? to find (surprisingly) that Miracast is not available on the Nexus 6, though it does seem you can work around that. But certain apps that requires HDCP (Netflix, Hulu, etc) may be problematic.

It would work on a Chromecast, but then you can't use your phone's data connection.

If your phone can be tethered, I would try a mobile router that can share a cellular data connection like the ones from Cradlepoint and TP-Link. That assumes your provider doesn't charge you for tethering.
[Google Chromecast] joeyakaspce1130:
Turn on hotspot, connect Chromecast to hotspot, start screen casting, turn off data but leave on hotspot and it will STILL be casting without internet! Good luck!
[Nexus 4 Q&A, Help & Troubleshooting] BMXJeff:
When I plug my Nexus 4 into a PC (only tried Win7 so far but multiple systems) Windows reports 'The USB device has failed, please remove device'. It repeatedly tries to communicate with the Nexus 4 while plugged in and connects and disconnects every few seconds but at no point is recognized as a Nexus 4 or do I get a chance to install drivers. This occurs with USB debugging on/off, MTP on/off, CWM/TWRP USB mounted or not. I have tried various ROMs all with the same result. It still charges though.

I recently changed the USB daughterboard as the socket was becoming temperamental while charging. I can't remember the last time I transferred data with a cable as I normally use bluetooth, wireless FTP etc so I can't be sure the problem has only been occurring since installing the new USB board.

Interestingly enough, I discovered after not being able to boot a ROM, that I could still push data to the device via fastboot. To me it seems if the hardware was faulty then it would not allow data to pass in any mode. Correct me if I'm wrong but as far as I know USB always uses pins 3+4 for data and 1 + 4 for +5V and ground respectively so it's not like the hardware is being used differently.

I have ordered another LG USB daughterboard along with a new battery as mine is on deaths door, so I'm hoping this new USB board will solve my problem...

Do you know why can I only pass data over the USB and get the device recognized in bootloader using fastboot?
[Nexus 4 Q&A, Help & Troubleshooting] jd1639:
Have you checked your usb in device manager when you're normally booted or in recovery? It uses different usb drivers than when you're in the bootloader. Check to see if its a driver issue.
[Nexus 4 Q&A, Help & Troubleshooting] BMXJeff:
This is half the problem. Because Windows enters a sort of loop where it keeps trying to recognize the device, it does not show up for more than a split second in device manager and when it does, it is recognized as unknown device. If I am fast enough to right click on the unknown device and try to manually point drivers at it, Windows tells me the best drivers are already installed. Obviously Windows has no idea what my Nexus is at this point.

I have connected in bootloader and the phone shows up normally in device manager as Android Device etc. I have updated the drivers manually pointing Windows to C:\android-sdk\sdk\extras\google\usb_driver but this does not help trying to connect in fully booted MTP mode when the recognition loop starts again.

I have been working my way through this thread with no luck so far. Other people appear to have had the same problem and just given up.

I am going to try my Nexus on an XP machine tomorrow and see what happens.
[Nexus 4 Q&A, Help & Troubleshooting] aRe-dUb:
I recommend using the nexus root toolkit and following the driver installation guide. I've had similar problems in the past but reverting to this program and following the basics has always led to working results.
[Nexus 4 Q&A, Help & Troubleshooting] BMXJeff:
Solved!

Ok, so I know this may not help many people apart from simply reiterating the fact USB sockets do fail so if you get stuck with Windows recognizing the device bear this in mind. Although one thing I have learned is that it is possible for such a failure to occur which allows data to still be passed in boot loader but not in MTP mode. I would still be interested to hear if anybody knows why/how this is possible?

After hours of trying different combinations of peoples methods of installing drivers It turns out the USB socket/daughterboard was to blame.

I replaced both the USB board/socket and battery and my Nexus is like a brand new phone. As soon as I plugged it in to my PC (using an old non LG cable) Windows recognized it, installed drivers and mounted it ready for me to browse. No manual driver installation required. Data can be transferred normally. It just works as I expect an Android phone to.

Thank f**k for that
[LG Optimus L3 II, L5 II, L7 II, L9 II] lallo29:
Hi guys, I have a problem with my ''GhostRom'' and the CWM recovery.

I have installed the last version, 31/07/2014, after wipe data, cache partition and dalvik cache I flash the rom, but after ''installing update'' the installation crashes and tells me installation aborted without error.

Thanks in advance.
[LG Optimus L3 II, L5 II, L7 II, L9 II] BlackAsMySoul:
Did you try this way? (P710)

Everything on page 5 [MENTION=2544369]ghostrom[/MENTION] post. :)

1) Go into CWM Recovery

2) Wipe data/factory reset

3) Wipe cache partition

4) Go to advanced and wipe dalvik cache

5) Install ZIP

6) Choose ZIP from sdcard

7) Select Ghost-ThunderCloud ROM P710 by lallo29(v1.0).zip

8) Wipe data/factory reset

9) Wipe cache partition

10) Go to advanced and wipe dalvik cache

11) Reboot (this can take up to 10 minutes for the first time)

---------- Post added at 02:48 PM ---------- Previous post was at 02:45 PM ----------

Oh well I see this is an older post, sorry for that
[HTC Desire C] KovaL1990:
I and My girlfriend have the same phones (HTC Desire C) And we have diffrend problems.

My battery fast it discharges, and second lives longer, but causes restarts 7 - 8 per day.

what is the problem? we need to buy new batteries?

P.S. sorry fom my bad English ;p
[HTC Desire C] Quasar:
Non rooted? If so, then go to the service center.
[HTC Desire C] KovaL1990:
both rooted
[HTC Desire C] Quasar:
Then, try recalibrating the battery
[HTC Desire C] KovaL1990:
I tried to calibrate the battery, and it did not work, I'm worried about restarts caused by the second battery
[HTC Desire C] Quasar:
Surprising. Go the a service centre.
[G2 Q&A, Help & Troubleshooting] bharatbharija:
Hi,

How do i voice dial using a bluetooth handset on this device. (LG G2 - D802). THe same button when used on nexus opens the google now application and i can do a voice dial. While on lG G2 it doesnt do anything. Even on s4 it opens voice dialing.

Other then this, on LG G2 google now is deaf to my bluetooth mic. I have checked that bluetooth flag (checkbox) on my google now.. but its still not hearing anything from my bluetooth mic.
[MDA, XDA, 1010 General] adahash:
I have an i-mate Pocket PC with windows 2005 OS

A friend of mine has a Qtek 1010

Rom V. 3.18.04 ENG

ROM Date 05/22/03

Radio V. 3.25.01

Protocol V. 32554

He liked my 2005 ROM and asked me to upgrade his PPC to the 2005 ROM

Could this be done, and if yes please could someone tell me how.​
[MDA, XDA, 1010 General] dinkodimov:
no you don't
[MDA, XDA, 1010 General] Rudegar:
if he does he sure dont have access to much storage :P
[MDA, XDA, 1010 General] mmy44:
u can

yes

http://wiki.xda-developers.com/index.php?pagename=Himalaya_2005
[Android General] wladimir_tm:
ERROR: failed to mmap framebuffer

maybe its help some;

when you boot "ported CWM" and look (via ADB) at file /tmp/recovery.log

you'll find main ERROR "failed to mmap framebuffer: Invalid argument" (graphics.c - or frame buffer driver is needed :( )

ps: I'm trying to port CWM to c230w too..

& additional (maybe interesting) about c230w at Russian board 4pda.ru

/forum/index.php?showtopic=592797
[Android General] wladimir_tm:
compare this with "native" c230w stock recovery log

(located /cache/recovery/last_log)

fd 6 vs fd 4 :(

& resolution of cause; but last maybe not so important as fd

command: cat /cache/recovery/last_log

__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Thu Jan 1 19:29:44 1970
recovery filesystem table
=========================
0 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system 0
1 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache 0
2 /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata -16384
3 /sdcard1 vfat /dev/block/mmcblk1p1 0
4 /sdcard0 vfat /dev/block/mmcblk0p21 0
5 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot 0
6 /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery 0
7 /misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc 0
8 /tmp ramdisk ramdisk 0

locale is [zh_CN]
framebuffer: fd 4 (480 x 800)
installing_text: zh_CN (240 x 38 @ 1818)
erasing_text: zh_CN (128 x 38 @ 1521)
no_command_text: zh_CN (92 x 38 @ 1521)
error_text: zh_CN (98 x 38 @ 1521)
Command: "/sbin/recovery"

ro.boot.console=ttyHSL0

& additionally - maybe useful info from shell:

command: cat /proc/fb
0 mdssfb_80000
---------------------------
command: cat /proc/fdv_info
LCD apex 0x00209806 0 lcd_apex_ili9806c_video 0x00209806
LCD feixun 0x00101080 1 lcd_feixun_fl10801a_video 0x00101080
LCD feixun 0x00105510 0 lcd_feixun_NT35510_cmd 0x00105510
G_sensor KIONIX 0x0520000f 0 Konix 0x0520000f
G_sensor bosch 0x05400018 1 Bosch 0x05400018
L_Psensor Taos 0x03200039 1 taos_alsprox_sensor 0x03200039
Camera_main SAMSUNG 0x04100020 0 S5K4E1_camera 0x04100020
Camera_main OmniVision 0x06c0006c 0 OV5648_camera 0x06c0006c
Camera_main GALAXYCORE 0x04a00078 1 GC2235_camera 0x04a00078
EMMC Hynix 0x9000014a 1 H4G1d 0x9000014a
TP Goodix 0x0242814a 1 GT950 0x0242814a
Camera_second GALAXYCORE 0x04300042 1 GC0339_camera 0x04300042
---------------------------
[Android General] arvinquilao:
I suggest you stick with your original build first. Can you post your Boardconfig.mk? You might want to try changing your recovery pixel format. Also try adding this flag: TARGET_RECOVERY_LCD_BACKLIGHT_PATH := \"/sys/class/leds/lcd-backlight/brightness\" in your Boardconfig.mk file. That line fixed the black screen issue in my recent build (for another msm8610 phone.)
[Android General] crazytiti:
Thank for the update.

I'm currently compiling it with option TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"

as before i try option TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"

and get an "fb0 invalid argument" in the recovery.log.

Do you know other format that i can test if theses doesn't work ?

My BoardConfig.mk is attached to this post with adding pixel format and

TARGET_RECOVERY_LCD_BACKLIGHT_PATH := \"/sys/class/leds/lcd-backlight/brightness\"

EDIT : with "RGBX_8888" i get the same error as before ("invalid argument" without "fb0")

I conclude that RGBX_8888 is the default format.

I'got this list from developper.android.com

nt	RGBA_4444

int	RGBA_5551

int	RGBA_8888

int	RGBX_8888

int	RGB_332

int	RGB_565

int	RGB_888

let's try it.... (20min build time for each test, need to find something faster than my Ph X4 965, maybe it's the VM anyway if i don't make clobber the change aren't taken)
[Android General] crazytiti:
I try all these unsuccessfully

TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"

TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"

TARGET_RECOVERY_PIXEL_FORMAT := "RGB_888"

TARGET_RECOVERY_PIXEL_FORMAT := "RGBA_8888"

TARGET_RECOVERY_PIXEL_FORMAT := "RGBA_4444"

TARGET_RECOVERY_PIXEL_FORMAT := "RGB_565"

TARGET_RECOVERY_PIXEL_FORMAT := "RGBA_5551"

maybe i miss something else ?

in graphics.c

mmap(0, fi.smem_len, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0);

man page for mmap say that EINVAL (the error code returned) is for addr, length, or offset invalid in

void *mmap(void *addr, size_t lengthint " prot ", int " flags, int fd, off_t offset);int munmap(void *addr, size_t length);

In graphics.c i see :

if (!has_overlay) {
vi.bits_per_pixel = PIXEL_SIZE * 8;
if (PIXEL_FORMAT == GGL_PIXEL_FORMAT_BGRA_8888) {
vi.red.offset = 8;
vi.red.length = 8;
vi.green.offset = 16;
vi.green.length = 8;
vi.blue.offset = 24;
vi.blue.length = 8;
vi.transp.offset = 0;
vi.transp.length = 8;
} else if (PIXEL_FORMAT == GGL_PIXEL_FORMAT_RGBX_8888) {
vi.red.offset = 24;
vi.red.length = 8;
vi.green.offset = 16;
vi.green.length = 8;
vi.blue.offset = 8;
vi.blue.length = 8;
vi.transp.offset = 0;
vi.transp.length = 8;
} else { /* RGB565*/
vi.red.offset = 11;
vi.red.length = 5;
vi.green.offset = 5;
vi.green.length = 6;
vi.blue.offset = 0;
vi.blue.length = 5;
vi.transp.offset = 0;
vi.transp.length = 0;

So only 3 pixel format are supported ?

maybe i have to add other formats here...
[Android General] crazytiti:
I only see know that KonstaT is giving it's source for building its CWM recovery for Kis3 :

github.com/KonstaT/android_device_zte_kis3

I will dig in...
[Android General] crazytiti:
After extending tests with several combinations :

it seems that something in my kernel and/or dtd prevent cwm recovery to get framebuffer.

even when i'm including all of the msm8610 board specifics lines from BoardConfig.mk from kis3 i still can't get mmap

I even try to put my compiled recovery with the dtd and zimage from kis3 => same result as using directly kis3 recovery : recovery working but screen is blury. (although in recovery.log i get fd4 480x800)
[Android General] koylaaa:
I have same device but no cwm recovery, mine is msm8210, I am not a developer and I also need your help to port cwm recovery on this device, thank you.
[Android General] crazytiti:
the 8210 is almost the same as 8610 (somewhere they say that 8610 is the quad core version and 8210 dual-core but mine is 8610 dual core)

Currently i'm out of idea.

I understand that the kernel and dtd file have something "special" preventing "classical" build of CWM recovery to get the framebuffer.

As the source of the phicomm kernel isn't available i don't know what to do.
[Android General] koylaaa:
Very sad to know this,as a newbie, I thought cwm recovery works on different devices with similar specs,really sad though I got this device 12days ago,am not impressed with the ram management same as the stock launcher.
[Android General] crazytiti:
Indeed it should, i think that phicomm is doing some nasty thing to the kernel...

By the way you can change the launcher without changing recovery or rom (and for the ram uninstall all useless apps + with some "process manager" select which one have to be launch at startup + enable memory cleaning every 2 hours)

If you don't know how to do all of this, make a search or a new topic in appropriate sub-forum.
[Android General] arvinquilao:
Please add these flags:

TARGET_QCOM_DISPLAY_VARIANT := caf
TARGET_USES_QCOM_BSP := true
BOARD_USES_QCOM_HARDWARE := true

and use "RGBX_8888" for the recovery pixel format, then check again the recovery.log.

You can also refer to my Boardconfig.mk for additional flags to use.
[Android General] crazytiti:
Hello,

funny facts : i get 90% of konstaT boardconfig.mk but i didn't get this particular flags :

TARGET_USES_QCOM_BSP := true

So i went to add it just now and my recovery won't build : msm_mdp.h not found

I get the file (and many others) from https://android.googlesource.com/ke...9d16c2d44364e905996fe32bbfe747/include/linux/

but for now my build isn't working, i think that some other parts linking to msm_mdp are missing,

Indeed big thank i keep on trying ;)
[Android General] arvinquilao:
What other header files are missing? Can you post the build error message? msm_mdp.h header is needed by graphics_overlay.c, which in turn gets used when TARGET_USES_QCOM_BSP flag is set to true. You may check the proper path to these header files; some headers may already be existing but the paths to their particular folders are not correctly declared.
[Android General] crazytiti:
I think i have put the header files in the wrong directory : i made a new "linux" folder under /bootable/recovery/minui/

and when i tried to build i get :

target thumb C: libminui <= bootable/recovery/minui/graphics_overlay.c
target arm C++: libpixelflinger_static <= system/core/libpixelflinger/scanline.cpp
target thumb C++: libpixelflinger_static <= system/core/libpixelflinger/codeflinger/ARMAssemblerInterface.cpp
In file included from bionic/libc/include/sys/types.h:37:0,
from bionic/libc/include/strings.h:42,
from bionic/libc/include/stdlib.h:36,
from bootable/recovery/minui/graphics_overlay.c:31:
bootable/recovery/minui/linux/types.h:13:2: warning: #warning "Attempt to use kernel headers from user space, see http://kernelnewbies.org/KernelHeaders" [-Wcpp]
target thumb C++: libpixelflinger_static <= system/core/libpixelflinger/codeflinger/ARMAssemblerProxy.cpp
bootable/recovery/minui/graphics_overlay.c: In function 'alloc_ion_mem':
bootable/recovery/minui/graphics_overlay.c:166:13: error: 'ION_SYSTEM_CONTIG_HEAP_ID' undeclared (first use in this function)
bootable/recovery/minui/graphics_overlay.c:166:13: note: each undeclared identifier is reported only once for each function it appears in
bootable/recovery/minui/graphics_overlay.c: In function 'free_overlay':
bootable/recovery/minui/graphics_overlay.c:336:24: error: 'MDP_DISPLAY_COMMIT_OVERLAY' undeclared (first use in this function)
bootable/recovery/minui/graphics_overlay.c: In function 'overlay_display_frame':
bootable/recovery/minui/graphics_overlay.c:417:24: error: 'MDP_DISPLAY_COMMIT_OVERLAY' undeclared (first use in this function)
make: *** [/media/cyanogen/android-cm11/system/out/target/product/msm8610/obj/STATIC_LIBRARIES/libminui_intermediates/graphics_overlay.o] Erreur 1
make: *** Attente des tâches non terminées....

ps : i build with "make -j4 recoveryimage"

thank for help :good:
[Android General] arvinquilao:
Please check if those are declared in the msm_ion.h and msm_mdp.h files. Compare these to the attached.
[Android General] crazytiti:
I just check and the file i'm using differ from the ones you provide.

MDP_DISPLAY_COMMIT_OVERLAY and ION_SYSTEM_CONTIG_HEAP_ID are defined in your files.

I will try to build with your file tonight (tonight in france UTC+1)

:highfive:
[Android General] arvinquilao:
Great, let me know how it turns out. :good:
[Android General] trol_sg:
Really what I did is just translate the T30 version that has been uploaded here in CWM format, so maybe the problem is that ROM itself. Or...I removed some chinese apk that might control this sensor, anyhow is strange, because I was carefully on removing only chinese crap...Or Jbart translation software modified something that control this sensor...

If you can try this T30 rom (http://lameserver.de/phicomm/C230w_T30.zip), because atm I don't have phone at hand again, and we will see.

If this one works, you can try this one: https://mega.co.nz/#!A9cnTQpb!Vr3wICbIWO_YdKAseHjQiFZ-Tnsa9y4RO86PLkP7fuE

If this can't work, it's Jbart software which damaged the rom.

If can work, then it's my failure removing something that it's needed, in last case, I'll rebuild it from 0.

By the way, if crazytiti or pandrzej2 can build better rom, I can use this base to translate.

But really, it's better to end with something as most stable and good as possible, and after that, I can make translation.

Regards
[Android General] camot:
I tried the C230w_T30.zip ROM and, as you expected, the proximity sensor does not work. I was saying that it was working with the original multilingual crap software that came with the phone (probably it is the one called T27 here).
[Android General] crazytiti:
If i understand correctly you have the quad-core version, The T27 rom is for dual core, it seems that the quad core version need some change in the rom to have the camera AND the proximity sensors working.

I suggest you to find the differences between your original rom ("T27-quad") and the T27 available for dl in the first post.

Then apply same modification to the T30 rom, and you should get a working T30 rom.

Be aware that some modifications could be inside the kernel (zimage.img inside boot.img), this one is difficult to extract/modify/repack, maybe you're stuck with the kernel that was ship with your phone.

Unless someone with the quad core has the last kernel and make it available.

Good modding ;)
[Android General] pandrzej2:
I fixed rom multilanguage, not only EN and CH.
[Android General] trol_sg:
If you can share it. We cant test maybe its more stable than this one that i mod. Regards
[Android General] pandrzej2:
https://www.dropbox.com/s/xp6ssabyh3k8fjn/C230W_T27_with_calcluator_V5 - data_on_sd.7z?dl=0
[Android General] Thousandwings:
Wow

That is impressive!
[Android General] pandrzej2:
When playing Apollo with equalizer sound sometimes breaks. But in original is sometimes is the same. Maybe is bad kernel.
[Android General] camot:
Thanks, I will try to compare the two roms when I have a bit of time. Probably the differences are in the kernel since the libraries that came with the quad-core version are also msm8610 libraries. I did not find any special library for msm8612. Fortunately the camera seems to work well under the T30 rom and the only problem is the proximity sensor which can be disabled.
[Android General] kriska:
If you have the original quadcore ROM or another ROM which works with quadcore, please share.

I have this phone in quadcore version and after flashing ROM's available in this thread I experience the following problems:

- 3G does not work at all

- screen is off during calls

- camera app and flashlight app does not work - work if you change boot.img.

T30 ROM has changed firmware in my phone. Maybe we need to revert firmware to old version? Could someone please make backup of his quadcore ROM and firmware?
[Android General] DhaniBaho:
I have a request for you guys... this phone will be awesome if it has OTG function... ?

Sent from D-Clue™