yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] mauricio teles:
fix touch foston fs-m787s

I managed to install this rom on my tablet which is a Foston FS-M787S, it worked ok but the touch does not work and I just can use with a USB mouse

someone could make a drive / script to work the touch on this tablet, case also want the GSensor and the camera also, thanks

SORRY FOR BAD ENGLISH I'M BRAZILIAN :good:

Tablet Specs:

Chipset: Allwinner A13

CPU: ARM Cortex-A8 1.2GHz

GPU: ARM Mali-400MP

Screen: 854x480 7.0" LCD with 5 point Multitouch

Camera: VGA Camera, 5.0MPx Camera with VGA Recording

Factory Operating System Android 4.0.4

Touchscreen: GT811

G-sensor: mma7660

Camera: sp0838
[Android Q&A, Help & Troubleshooting] mauricio teles:
fix touch foston fs-m787s

I managed to install this rom on my tablet which is a Foston FS-M787S, it worked ok but the touch does not work and I just can use with a USB mouse

someone could make a drive / script to work the touch on this tablet, case also want the GSensor and the camera also, thanks

SORRY FOR BAD ENGLISH I'M BRAZILIAN

Tablet Specs:

Chipset: Allwinner A13

CPU: ARM Cortex-A8 1.2GHz

GPU: ARM Mali-400MP

Screen: 854x480 7.0" LCD with 5 point Multitouch

Camera: VGA Camera, 5.0MPx Camera with VGA Recording

Factory Operating System Android 4.0.4

Touchscreen: GT811

G-sensor: mma7660

Camera: sp0838
[Android Q&A, Help & Troubleshooting] Insanefish:
A13 Cyanogenmod no wifi, works in faaastJB 2.5

Hey all. Really hope for some help here.

Cyanogenmod is working really well for me, only thing is that wifi wont turn on. Stuck on the "wifi turning on".

I tried faaastJB 2.5 where I cant get things to work, it hangs and whatnot, only things that did work there was the wifi....

lsmod of FaastJB 2.5

device 26862 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 34042 0 - Live 0x00000000
sp0838 19927 1 - Live 0x00000000
camera 53105 1 sun5i_csi0, Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 200007 29 - Live 0x00000000
ump 34213 11 mali, Live 0x00000000
nand 225000 8 - Live 0x00000000

lsmod of Cyanogenmod

8188eu 581006 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
cedarx 11869 0 - Live 0x00000000
videobuf_dma_contig 6251 0 - Live 0x00000000
videobuf_core 20242 1 videobuf_dma_contig, Live 0x00000000
mali 150572 10 - Live 0x00000000
ump 48978 13 mali, Live 0x00000000
mxc622x 6088 0 - Live 0x00000000
mecs 4078 0 - Live 0x00000000
sp0838 20079 0 - Live 0x00000000
gc0329 18016 0 - Live 0x00000000
gc0308 18408 0 - Live 0x00000000
gsl1680 51394 0 - Live 0x00000000
hid_sony 2377 0 - Live 0x00000000
hid_gaff 2817 0 - Live 0x00000000
xpad 9358 0 - Live 0x00000000

Would it be possible to pull the wifi driver from FaaastJB? Any help would be greatly appreciated.
[G3 Q&A, Help & Troubleshooting] exeterer:
I dont even get to the log in page on the netflix app. Anyone else habe this problem and maybe knows a solution?

Im having a LG G3 D855 unofficial cm12
[G3 Q&A, Help & Troubleshooting] iBolski:
It has to do with the DRM libraries. On my previous phone, there were issues and dhacker, who is working on the ROM for that particular phone, stated he had to find the correct libraries for it.

This also affected Google Play Movies & TV on the other phone, but eventually, dhacker got it working.

Just give the devs time. They should get it worked out eventually.
[G3 Q&A, Help & Troubleshooting] exeterer:
OK, thank you fornthe answer!
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] hungry4cheese:
Hey y'all,

I've had my note 4 for a couple of weeks now and am decently satisfied with the phone (don't get me started on how laggy touchwiz is - waiting on L update). Anyway I'm having an issue with bluetooth that is driving me insane. My previous phone was a nexus 5 that I always paired with my car and my sony bluetooth headset. I had no audio quality issues and the sound was clean enough for bluetooth. I only play decently high quality music and have the ears to hear the difference in sound so after paring my note 4 to the same devices, the highs are very crackly and come through with ear piercing noise and the lows are mostly gone as I cannot hear the punchy bass anymore in songs. I then proceeded to turn off bluetooth then plugged in the device with an aux cable and to no surprise the sound quality increased tremendously. The bass of the song came through and the highs were perfectly clear.

I tried various songs of various quality, various music players (current is poweramp - always have had best quality music from it), but to no avail. Sound is still really bad quality. Other issues I've had is my plantronics bluetooth headset randomly transmitting white noise to my ears and to the person on the other end. This does not happen with an LG G3. And also my LG G watch tends to randomly disconnect for a minute or two when the phone is playing audio in the car over bluetooth (this doesn't change sound quality).

I've done some research about this issue and I've found some forums and people talking about the Note 3 having bad quality audio and that switching to an aosp rom fixed it since that switched the bluetooth stack from samsung to android/google. I've also seen someone noticing that the bitpool on the note 3 dropped significantly when playing music and having another device connected, however with or without my watch I still get low quality sound. So I've come to you guys. My phone is not rooted, knox counter is at 0x0 and I don't know what to do. I feel like this is a universal issue with the note 4 and the samsung bluetooth stack and am not sure how to tackle this problem. Let me know what you guys think or if you have a similar experience!
[Fire TV Q&A, Help & Troubleshooting] Velvis:
Hi All,

I have a Fire TV stick and side loaded the Verizon FIOS app on to it. I managed to get my username/password by using the settings.apk and a bluetooth keyboard. I can scroll using the up/down arrows on the keyboard, but I can't select any channels.

I have a Fire tablet and an Iphone and I am willing to buy a controller.

What are the options for simulating a screen touch? or is that even possible?
[Fire TV Q&A, Help & Troubleshooting] ItsMeSri:
I am also having same problem. Are able to solve this? or any solution found?
[Fire TV Q&A, Help & Troubleshooting] Sizzlechest:
Yes, use a mouse.
[Sprint HTC One (M8)] Sinistertensai:
Okay so Im seeing a lot of threads along the lines of sunshine doesnt work for me or w.e. it will youre just missing some points about what they mean by "stock" rom...

theres two ways this is fixed, one involves a RUU (Rom Update Utility) and the other involves a fastboot command.

if youre gonna RUU then this thread isnt intended for you, imho ruuing takes more time than booting into fastboot and flashing a proper boot.img(kernel)

So you downloaded a stock rom from the sprint section and cant get sunshine to work, youre prompted with an error message along the lines of "flash a stock rom"

but you just did? why is this happening?!?! heres the reason. the stock rom most likely has a modified boot.img for r/w permission or a modified ramdisk for another plethora of reasons.

relax though the fix is simple! all you need to do is flash a proper kernel/boot.img. but where can I get this? well there is a firmware zip with the boot.img in there along with other img's for the sprint device's which can be found in omjs thread, and no im not gonna extract those files for you. if you want s-off so badly you can put in a little work.

so this guide is for those on the latest rom version (sense) 4.4.4 as of 12/9/14

:1) youre on the latest rom version and you downloaded a stock rooted rom from this thread http://xdaforums.com/showthread.php?t=2729173 (the stock roms there have modified boot.imgs)

:2) download the appropriate firmware zip you need for your device, e.g. H/K or None H/k (found in this thread http://xdaforums.com/showthread.php?t=2729173 read carefully and find the right firmware.zip)

:3) go into the firmware zip you downloaded and take out the boot.img

:4) place the boot.img in your fastboot path (not covering how to do that here, there's many a guide on how to get that working, use search)

:5) reboot into fastboot

:6) connect your phone to your pc with the data cable, and open a terminal or cmd window. terminal for unix like environments cmd for windows.

:7) type fastboot flash boot boot.img in the terminal window

:8) wait for the after text, saying sent and success.

:9) reboot your device run sunshine, be happy.

Do note this is written under the assumption you have updated everything and are stuck on a snag with sunshine.apk if this is too confusing or you cannot understand do not try it, simply RUU!
[Sprint HTC One (M8)] Sinistertensai:
reserved for super dumb'd down version which I haven't written yet...
[Sprint HTC One (M8)] Magnum_Enforcer:
Here's hoping someone finds this useful:thumbup:

Maybe this will cut down on some redundant posts both here & in the Sunshine thread.
[Sprint HTC One (M8)] jamieg71:
You'll never be able to dumb it down enough. Maybe release a picture book with pop outs..
[Sprint HTC One (M8)] Captain_Throwback:
[GUIDE]Sunshine S-OFF [NOOB PROOF] <---- This is quite a bold claim, sir. Hopefully you're right (but I highly doubt it, lol).
[Sprint HTC One (M8)] AarSyl:
Looking for a noob loophole....

But in other news, Flashify works for those who don't have access to fastboot, or just can't seem to understand how to flash a boot.img.

Granted, they still need working fastboot to use Sunshine...but whatever. Just putting it out there.

____________________________

Please remember to:

Check Q & A forums before asking!

Search forum for similar post before creating!

Hit "thanks" to everyone who may have helped you (it costs nothing)!

Read the OP!!!!
[Sprint HTC One (M8)] Sinistertensai:
They can ruu or follow the very simple instructions I posted. If my eleven year old cousin can understand the simple steps then I expect people to be able to too. But you're right cap, nothing is noob proof when it comes to xda noobs...
[One (M7) Q&A, Help & Troubleshooting] alray:
isn't ambient display a feature designed for AMOLED screen? Not sure it will worth it vs the battery consumption.

And btw why not trying yourself instead of asking everywhere? Try it and then tell us if it works ;)
[One (M7) Q&A, Help & Troubleshooting] monacoo:
I will, but I asked if someone already did this on M7,
[Galaxy Note 4 Accessories] Misterjunky:
error post
[Galaxy Tab 3 Q&A, Help & Troubleshooting] Panlew:
I just used the app "quick boot" and now I can't boot into my tablet (T110 Samsung Galaxy Tab 3 Lite)..

I can only boot into odin and recovery.

How do I fix it?
[Galaxy Tab 3 Q&A, Help & Troubleshooting] ph.miki:
Hi,

did u try to wipe all?
[Galaxy Tab 3 Q&A, Help & Troubleshooting] gr8nole:
You need to restore the stock recovery. This is a known issue.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] ph.miki:
Or via odin just install a stosk kernel:good:
[Galaxy Tab 3 Q&A, Help & Troubleshooting] gr8nole:
Kernel has nothing to do with this problem. Recovery and kernel are separate partitions on this device.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] ph.miki:
I had the same problem, an i was install just stock kernel, and was fine.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] Panlew:
I reinstalled 4.2.2 using a sam-mobile rom and it works. (I have stock recovery now.)

Thanks guys.

Anyway, do I need the file android-armeabi-universal-root-signed.zip to root this tablet?
[Galaxy S 5 Themes and Apps] marcinsi15:
Hi did anyone know maybe that someone port Lockscren from Note 4 Abstract Title effects? And it's that gonna work on Lollipop. Thanks
[Galaxy S 5 Themes and Apps] Sock12345:
You can give it a try with SQ Lite editor
[P3600 General] aZooZa:
I was playing with Resco Explorer and Resco Picture Viewer yesterday, and in what must be a culmination of circumstances, I ended up with a completely 'dead' 4MB mini SD. I looked around the net for some recovery software, but could only find stuff that could resurrect media files.

Than I found this:

http://www.datadoctor.biz/bak-c.htm

Completely read and backed up my card including ALL non-media files, and then I was able to reformat the card and copy all the stuff back. Perfect first time.

Hint: Move all the files you have that in the root directory into a subdirectory. Recovery software like this only recovers subdirectories.

I have no connection with this company, but I was very glad to find them.

Hope this helps others like me who don't back up their cards regularly.
[Galaxy Grand 2 Q&A, Help & Troubleshooting] android_smater:
after some day of rooting of phone my phobe dailer is not working there no icon of phone dailer in touchwiz luncher when i try to open it through contact the msg appear unfortunately contact has stop plz help

samsung galaxy grand 2 (kikate 4.4.2)
[Galaxy Grand 2 Q&A, Help & Troubleshooting] salimtn:
i suggest format it throw recovery
[LG G Watch] posedatull:
Hello. I have just purchased today a LG G Watch after my Gear 1 died, and I really wanted to use the Swear O'Clock watch face (the one copied from Pebble, seen it on 9gag, looks awesome), but I am unable to find it. Can someone please point it out? I've been able to find something similar as a watch face regarding weather, but the clock itself was far more important to me than the weather. Please help guys, I don't mind if the app is not free, I'll buy it, I just really wanna have it :D
[LG G Watch] Milimbar:
I made a Facer face ill post later

---------- Post added at 06:53 PM ---------- Previous post was at 06:40 PM ----------

http://facerepo.com/app/faces/details/swear-face-14a369bf661

The white text is the only thing that shows when the display is dim, rest appears when it is awake.

Time shows when cards come up on the screen if you have preview enabled, and charge/cloud icons appear above the time and do not get jumbled in it.

Single digit minutes show up as "o' six" so it dont look odd.
[LG G Watch] posedatull:
Thank youuuuuuuuu :D :D
[LG G Watch] Antonis427:
I'm also currently making a standalone watchface for Android Wear with the same concept. I'll let you know as soon as it's released on Google Play.
[T-Mobile Samsung Galaxy S 4] shaqto:
My T-Mobile S4 was having WIFI / LTE connectivity issues on Rogers so having successfully flashed ROM's before I started going through different jfltetmo ROM's but at some point flashed the wrong ROM. The last working ROM on my phone was CyanogenMod cm-11-20140217-NIGHTLY-jfltetmo.zip coupled with openrecovery-twrp-2.8.1.0-jfltetmo.tar but now my phone can only enter download mode and that too only when connected to a USB cable. If I turn my phone ON or try to enter Recovery mode it goes into a vibrate loop (no logo displayed) - does this make my phone soft bricked? Here is the screen output for my phone when in Download mode:

ODIN MODE

PRODUCT NAME: SGH-M919

CUSTOM BINARY DOWNLOAD: Yes (80 counts)

CURRENT BINARY: Custom

SYSTEM STATUS: Custom

QUALCOMM SECUREBOOT: ENABLE

Things I have tried so far:

-followed AndroidRootz Unroot / Unbrick Galaxy S4 tutorial step by step

-connect using Kies 3 with Samsung USB drivers v1.5.45.0 but Kies won't detect my phone

-flashed M919 stock Kitkat 4.4.2 (M919UVUFNB4_M919TMBFNB4_TMB.zip) using ODIN v3.10, v3.09, v3.07, and v1.85 which fails with ODIN showing:

<ID:0/006> aboot.mbn

<ID:0/006> NAND Write Start!!

<ID:0/006> FAIL! (Auth)

<ID:0/006>

<ID:0/006> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

and phone screen showing:

START [224, 1448]

SECURE CHECK FAIL: aboot

-flashed TWRP v2.8.1.0 ODIN tar which resulted in ODIN showing a PASS but there still was no Recovery Mode

-flashed TWRP v2.8.1.0 recovery img and CWM v6.0.4.3 recovery img to RECOVERY partition using Heimdall v1.4.0 which were both successful but there was still no Recovery Mode

I also extracted my device's PIT file using Heimdall (my-PIT.zip) then compared it with a stock PIT (JFLTE_USA_TMO_16G_PIT.zip) I had found somewhere online. It seems I have slightly corrupted my partition so I tried the following fixes:

-ODIN flash just the stock PIT (JFLTE_USA_TMO_16G.pit inside JFLTE_USA_TMO_16G_PIT.zip) which fails with ODIN showing:

<ID:0/006> Initialzation..

<ID:0/006> Set PIT file..

<ID:0/006> DO NOT TURN OFF TARGET!!

<ID:0/006> FAIL!

<ID:0/006>

<ID:0/006> Re-Partition operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

and phone screen showing:

START [224, 1448]

SECURE CHECK FAIL: PIT

Do I need to explicitly fix my PIT partition first?

-If yes, is there a way to use ODIN, Heimdall, or some other tool to fix my PIT?

-if no, am I missing some step or using wrong firmware/tools?

Is there anything else I can do to get my phone back up and running? I am guessing I just need to be able to get into Recovery and the rest should be straight forward.

Any help to fix this issue would be greatly appreciated, thanks in advance
[T-Mobile Samsung Galaxy S 4] ShinySide:
You said the last working rom, but you failed to mention the last thing you flashed before the issue....And that was?.....
[T-Mobile Samsung Galaxy S 4] shaqto:
I can't remember now which ROM caused the issues - it was either a Samsung S3 or S4 ROM.
[T-Mobile Samsung Galaxy S 4] ShinySide:
If you flashed an s3 rom or firmware, you're most likely screwed.

Best bet find a pit file for m919 that isn't your pit file.
[T-Mobile Samsung Galaxy S 4] shaqto:
I did find and flash a S4 ROM which I attached in my original thread
[T-Mobile Samsung Galaxy S 4] ShinySide:
Yeah just noticed it.

Quick look thru it, you fcuked your boot Partition. At least if not more stuff. Didn't really compare side by side. Just what stood out to me.

Here's what it should be.

Binary Type: 0 (AP)

Device Type: 2 (MMC)

Identifier: 20

Attributes: 5 (Read/Write)

Update Attributes: 1 (FOTA)

Partition Block Size/Offset: 10146376

Partition Block Count: 20480

File Offset (Obsolete): 0

File Size (Obsolete): 0

Partition Name: BOOT

Flash Filename: boot.img

FOTA Filename:

here's yours

Binary Type: 0 (AP)

Device Type: 2 (MMC)

Identifier: 8

Attributes: 5 (Read/Write)

Update Attributes: 1 (FOTA)

Partition Block Size/Offset: 146176

Partition Block Count: 20480

File Offset (Obsolete): 0

File Size (Obsolete): 0

Partition Name: BOOT

Flash Filename: boot.img

FOTA Filename:

notice the Identifier on the correct one is 20. dev/block/mmcblk0p20 is the boot.img Partition for us. You flashed a boot.img to the tz Partition.

Your most likely only hope is jtag.

But there's one more thing.... we're obviously not getting the full story. This wasn't a s3 or s4 rom you flashed. Because your identifier 8 aka /dev/block/mmcblk0p8 isn't even the boot Partition for the s3. mmcblk0p8 on the s3 is the cache.img.ext4 Partition.
[T-Mobile Samsung Galaxy S 4] shaqto:
Correct, the BOOT partition is messed up now which is why I was trying to fix the PIT (or at least I thought I was) by flashing the stock PIT file in ODIN with re-partition checked.. Is "partition block size/offset" the memory address for the start of a given partition? I guess the better question is, is there any way to replace the partition mappings using a modified PIT or any other method? Also I was curious, what is the "Partition Block Count"?

What if we approach this problem a different way - rather than changing the partition mapping to have BOOT entry point to the correct BOOT partition location, can we not just update the incorrect BOOT partition location with the actual BOOT img? ie. flash boot.img onto the device using my existing PIT file via Heimdall

You are also correct the S3 PIT file also does not match my PIT file - actually I did a search on Google for PIT file and I don't think any device has a PIT file identical to the PIT structure currently on my phone. I know it's stupid of me not being able to remember which ROM caused my phone to be in this state but it's also because I downloaded several M919 ROM's and immediately deleted the bad ROM after thinking I will never need it again. Anyways thanks again for helping out.
[Nexus 6 Themes and Apps] BzkLegend:
Hi, i can found the stock wallpaper on my device (the wallpaper of woman) you can give me please? Thnks
[Nexus 6 Themes and Apps] BzkLegend:
Nothing? :(
[Nexus 6 Themes and Apps] :
Same problem :(
[Nexus 6 Themes and Apps] :
I need it, too... I can't believe nobody doesn't have it.
[Nexus 6 Themes and Apps] ikslawlok:
Nobody can give you, because it exists only for the commercials.

Envoyé de mon Nexus 6 en utilisant Tapatalk
[Nexus 6 Themes and Apps] cell2011:
Go to Google type in flying kite nexus should be a box download
[Nexus 6 Themes and Apps] BzkLegend:
Thanks!!! My english is so bad but thanks for help :D
[One (M8) Q&A, Help & Troubleshooting] devights:
I have a GPe M8 that was previously rooted, had an unlocked bootloader, and was using the TWRP recovery. I had not yet received the OTA, but in reading around learned that this was likely due to the fact that I needed to unroot, have the stock recovery and, according to some sources, needed a locked bootloader. So here's what I did today:

Un-root via the SuperSU app

Install the stock recovery (Following steps 1 and 2 here: htc-one. wonderhowto .com/how-to/update-your-rooted-google-play-edition-htc-one-4-4-3-without-losing-any-data-0155404 (spaces for bloody spam filter))

Lock the bootloader (fastboot oem lock)

Factory reset (probably unnecessary)

After doing all this I can finally get the "System Update" notification to appear and start the OTA (although I can't reliably make this re-appear, sometimes clearing the cache or an additional factory reset will bring the update notification back).

However, when I run the OTA, the phone boots into recovery as expected, then I get this error message:

Finding update package....

Opening update package....

Verifying update package...

Installing update...

L50QCT.00.001.001

mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy

Package expects build fingerprint of htc/m8_google/htc_m8:4.4.4/KTU84P.H1/356549:user/release-keys or htc/m8_google/htc_m8:5.0.1/LRX22C.H5/434277:user/release-keys; this device has htc/m8_google/htc_m8:4.4.2/KOT49H.H16/326432:user/release-keys

Installation aborted.

So, if I'm understanding that error correctly, the OTA is expecting 4.4.4 or 5.0.1 installed and thinks I have 4.4.2 installed. But, according to the About phone page, I do have that version installed.

View attachment 3056213

Any thoughts on what I did wrong or how I could get the OTA to install?
[One (M8) Q&A, Help & Troubleshooting] Vigz:
Based on what you did, the stock recovery image you flashed is older than 4.4.4 and instead from 4.4.2. Head to http://www.graffixnyc.com/m8.php and look for 4.4.4 Stock Recovery from 2.12.1700.1. Flash that and repeat the OTA installation again.
[One (M8) Q&A, Help & Troubleshooting] devights:
Thanks for the quick reply. I did have to re-unlock my bootloader, but the OTA installed fine after I used the recovery you linked.

Thanks for helping me out!
[One (M8) Q&A, Help & Troubleshooting] DataSyncID:
Answer Confirmed! Thank you!

I was having this issue too and after flashing the 4.4.4 Recovery from your link I was able to update! Thanks for your help!!
[One (M8) Q&A, Help & Troubleshooting] zzzzesht:
Update your stock Recovery.img

This problem caused by Recovery.img file. your recovery mode is Old.

To solve problem and update OTA, just update your recovery with the latest Recovery.img file.

This file included in official ROMs in firmware.zip folder.

Download one Official Lollipop ROM and extract Recovery.img file, Use ADB to restore this recovery file.

then easily update OTA.