yashsingh1/xdaforums huggingface dataset:
[Nexus S Q&A, Help & Troubleshooting] nexuspb:
Hey,

Thanks for the reply. Nothing lights up at all, its like a rock. Nothing works.
[Nexus S Q&A, Help & Troubleshooting] RemeCA:
You could try a new battery, they're like $5 on ebay. With a new battery, and if it doesn't enter fastboot after charging (hold power and volume up) then it would seem to be truly bricked.

---------- Post added at 02:34 PM ---------- Previous post was at 02:28 PM ----------

You may also want to try a different cable, if the battery is dead and the cable isn't carrying a charge it would have the same effect as being totally bricked.
[Nexus S Q&A, Help & Troubleshooting] nexuspb:
I'm certain the battery works. I heard jtaging it will unbrick it, but it cost like $40 to jtag it which isn't worth it since phone isn't even worth $40
[Nexus S Q&A, Help & Troubleshooting] ej8989:
JTAG is the only way to check if it will still work. The only other option is the resurrector mod which involves desoldering and soldering microcomponents on the main board.
[Nexus S Q&A, Help & Troubleshooting] nexuspb:
I want to try resurrection mod, however, a few of the images are gone from the thread
[Sony Xperia M] SharpnShiny:
Hi,

I 'dropped' my phone hard on a table and now the screen doesn't show anything. I can hear the phone clicks so that works. I've tried turning it on and off etc. but no luck.

Might it be loose wire or other part?

Thanks
[Sony Xperia M] gamer649:
If the screen remains fully black when you attempt to switch it on then its likely to be a loose wire. If there is a backlight then it could be either a loose wire or a damaged LCD screen.
[Sony Xperia M] SharpnShiny:
There is a backlight indeed. I wonder how much I can take apart myself to find out. I can't see any obvious dents or cracks etc. on the screen or casing etc. so maybe something is loose?
[Sony Xperia M] Farsiris:
Flash stock kernel. . you can see the sony logo right? then after that just black with backlight? its just like PC without windows .meaning its just BIOS without windows .its just the same with Phone ,no kernel no boot .So just flash the stock kernel
[Sony Xperia M] gamer649:
There is nothing wrong with the software. The OP dropped the phone onto a table, that would have caused a hardware problem.
[Sony Xperia M] Farsiris:
Did he tried it?just a suggestion.maybe it will solve.y not try?right?
[Sony Xperia M] gamer649:
There is no point in trying it because it is a hardware issue. The OP can hear the clicks it makes when it unlocks and they try to hear it, meaning that it boots fine and there is a working kernel. Its a hardware issue, possibly caused by the ribbon cable to the screen coming loose.
[Sony Xperia M] Farsiris:
are you a technician?i think your so perfect .as if you know everything
[Sony Xperia M] gamer649:
No I'm not, I'm attempting for a job as a technician though as I know how to diagnose faults and what faults are hardware and software.

I don't know everything and I'm far from perfect, I'll admit that. But with what I do know, I know it well.

Now I'm gonna leave it here cause there is no point carrying it on.
[Sony Xperia M] SharpnShiny:
Thanks for the tips guys.

Nope, I can't see the Sony/Xperia logo.

Yeah I wondered would a cable be loose. Is it easy to take this phone apart? If not I might try claim the warranty. There is no physical damage at all.
[Sony Xperia M] gamer649:
I haven't disassembled the phone myself (I have had no need for it), however I have just watched a YouTube video and it seemed to be easy enough to disassemble and reassemble. If you look it up yourself and judge whether you wish to try yourself or not. If you have warranty from the store you bought your phone at it will more than likely cover accidental drop damage so if you don't wish to risk your phone then that would be your best option in all fairness.
[Sony Xperia M] mbc07:
Try the service manuals...
[Sony Xperia M] SharpnShiny:
OK I opened it up and I couldn't see what the problem was. Nothing appears damanged, as expected. There are three main ribbon cables, none of them appeared loose. However, when disconnecting the mainboard from the phone case, the middle cable, which lights the LCD screen, has become fully detatched. It seems that unlike the other two cables, it connects via adhesive. I don't have thermal adhesive. When the phone turns on, now there is no backlight in addition to nothing being visible on the screen. PC Companion picks up the phone so all of that seems to be working. But no LCD and now no backlight. Unfortunately, there is evidence of me opening the phone. I doubt the warranty would be accepted now...?

In the reassembly video in document 1277-1354_Rev1 , it shows the three connectors just snapping/connecting....no glue situation.

If there is anything else I can do via home repair, what could I do? I can't be that far off, surely? :eek:
[Sony Xperia M] Dickey Kid'deviel:
even if you don't open it, you can't file a warranty on SONY Service Centre if the damage is LCD, just buy a new LCD and replace it
[Sony Xperia M] SharpnShiny:
Would that be the case even if I bought it locked on a network? How would they know it's the LCD if I don't say? Once before, with another smartphone, instead of listing everything I understood to the manufacturer, I told them almost nothing and got a full replacement.
[Nexus 5 Q&A, Help & Troubleshooting] Shibazeet:
Hi guys,

I have recently rooted my device and flashed a custom ROM (CyanogenMod), after 2 days there was an update for CM. Update was installed perfectly but then after the reboot "settings" on the phone stopped working. closed unfortunately. I went into recovery mode to flash the previous ROM. I am using "TWRP" recovery tool. This where I have done the blunder, I have wiped the system data and all of it. At the moment phone doesnt have any ROM to boot on. Please suggest me to how to flash the factory ROM or any other ROM. Can't really do anything as the phone wont boot up in regular mode (GOOGLE) thats all.

HELP HELP HELP HELP HELP HELP HELP HELP HELP
[Nexus 5 Q&A, Help & Troubleshooting] doctor_droid:
Jz flash any cm rom zip :p just a soft brick easily recoverable
[Nexus 5 Q&A, Help & Troubleshooting] jd1639:
adb push a rom zip onto your sdcard and flash it in recovery
[Nexus 5 Q&A, Help & Troubleshooting] theesotericone:
Can you sideload in TWRP?' It's even faster than pushing for the unpatient folk like me. lol

And yeah jd I still have the Rocket.
[Nexus 5 Q&A, Help & Troubleshooting] simms22:
that was his first and only post, i bet he wont be back. sounds like a root toolkit child.
[Nexus 5 Q&A, Help & Troubleshooting] Shibazeet:
How?

Having said that I cannot detect the phone in the PC, how can i put the ROM in a folder?
[Nexus 5 Q&A, Help & Troubleshooting] vin4yak:
Guess what? He's back! :D

[MENTION=5939092]Shibazeet[/MENTION]

You need to follow this thread to setup adb/fastboot: http://xdaforums.com/showthread.php?t=2588979
[Nexus 5 Q&A, Help & Troubleshooting] kingspeed:
Use NRT nexus root toolkit 1.8.4

& recommend to install stock image nexus from official google website , just search " stock image nexus 5 "

SORRY FOR MY BAD EN !!
[Nexus 5 Q&A, Help & Troubleshooting] Lokke9191:
http://xdaforums.com/showthread.php?t=2277112

Use this guide to setup fastboot. Then download the factory image to your computer. Use fastboot to install it and any other future roms.
[Nexus 5 Q&A, Help & Troubleshooting] Darth:
My friend, you don't use fastboot to flash "ROMs". ;)
[Nexus 5 Q&A, Help & Troubleshooting] Lokke9191:
Sorry woke up 5min before writing that. Running on 4hrs sleep now. Meant use fastboot to install stock image, flash a recovery. Then use custom recovery to flash future roms. Just pointing him in the right direction. With a little reading, he'll figure it out. :)
[Nexus 7 (2013) Q&A] patel4prez:
Hello all,

I would like to know if any of the many available bluetooth styli for the iPad(s) can be used on the Nexus 7/other Android devices?

A couple examples...

The Intuos Creative Stylus

The Jot Script Evernote Edition

My main reason for finding out about this is because I want a stylus to work with palm rejection. As far as I understand, a bluetooth stylus is an active stylus and therefore enables you to use many of the apps with palm rejection capabilities built in.

If this is the case, shouldn't it be possible to simply pair the stylus with an Android device and just move on?

Thanks for replies in advance :) .
[Fire TV Q&A, Help & Troubleshooting] Khord:
I have a Rii i8 Mini keyboard from Amazon, and I have been having trouble with it in both in FTV and XBMC. The keys erratically repeat for many characters like thissssssssssssss and even the arrow keys occasionally get stuck scrolling down in menus. Also, some key presses are randomly not detected. I googled a bit, and saw that this was a problem for many android users (couldn't find anything KFTV specific) involving 2.4ghz / bluetooth mice and keyboards.

I came across a discussion that suggests to install the app "External Keyboard Helper Pro", which I tried via sideloading, but wouldn't launch after install. This would not fix the keys randomly not registering either. I tested another 2.4ghz keyboard mouse combo and it worked perfectly fine. I also tested the problem keyboard on my Windows PC, and I was able to type out an entire paragraph without errors, whereas on the Fire TV, I can barely type my email or password without 10 typos.

Does anyone have any experience with this problem?

TLDR; Does anyone know how to disable sticky keys on the FTV or force an app that wont launch to launch?

Or, any other mini keyboard suggestions for the FTV
[Fire TV Q&A, Help & Troubleshooting] goto35:
I have the same problem with the same keyboard. I thought it was my keyboard and was about to return to amazon.
[Fire TV Q&A, Help & Troubleshooting] sam143569:
I have the same problem
[Fire TV Q&A, Help & Troubleshooting] toe-rag:
I would guess it's the keyboard itself. I bought a Hausbell ® Mini H7 2.4GHz Wireless Entertainment Keyboard with Touchpad for PC, Pad, Andriod TV Box, Google TV Box, Xbox360, PS3 & HTPC/IPTV (Black) to use on my G-Box -- and I had very similar issues that you describe. It even wouldn't produce character that was 'shifted'. Never did get it to work correctly. It does the same thing on my FTV. I have since purchased a iClever IC-RF01 2.4G Ultra Mini Wireless Keyboard with Mouse Touchpad all the problems disapeared no more repeating key presses...
[Fire TV Q&A, Help & Troubleshooting] Khord:
Thanks, I'm gonna give that one a try.
[Fire TV Q&A, Help & Troubleshooting] codeshane:
*snip*

before replying to threads, one should beware the longevity of cached tabs .. how many times .. lol
[Fire TV Q&A, Help & Troubleshooting] noplan:
Damn, same issues here with the same keyboard. Is there still no solution except of buying another keyboard?
[Fire TV Q&A, Help & Troubleshooting] Khord:
I haven't found any solution yet. I've heard the Logitech K400 has no problems on the FTV but it's so much bigger and pricier. I might just cave it and get it soon though, cause it's frustrating to type with the dpad.
[Fire TV Q&A, Help & Troubleshooting] noplan:
I bought this one yesterday:

http://www.amazon.de/Rapoo-schnurlo...&ie=UTF8&qid=1412875796&sr=1-5&keywords=rapoo

It works much better but from time to time it has the same problem with the repeating characters. That would mean it is not a Rii-specific problem. But since it works now most of the time it is ok for me.

Maybe the problem is related to the firetv-input method (the onscreen keyboard for the remote controls dpad). Sometimes that keyboard appears, disappears, appears, disappears and so on when I try to enter some text using a physical keyboard.
[Fire TV Q&A, Help & Troubleshooting] bilbo6209:
I use a Lenovo N905 (I think) keyboard and have the same issue from time to time.
[Fire TV Q&A, Help & Troubleshooting] asastovall:
Same problem here. I'm going to try turning my Amazon box around so the the little key piece is facing forward to see if that makes a difference. Wish me luck. If it works I'll reply back. Maybe a USB adapter that will allow the key to face toward the front of the box might also work. I don't think the keys are getting stuck I think it's an interference issue.
[Fire TV Q&A, Help & Troubleshooting] tedrogers61:
I've got this same problem with the Rii, but prior to that I had an iPazz Port which was fine (although felt like junk in the hand). I might just get another one of them again and have done with it.

https://www.amazon.co.uk/iPazzPort-Wireless-Keyboard-Raspberry-KP-810-21S/dp/B00UBTTZ6A/ref=sr_1_1?ie=UTF8&qid=1465814865&sr=8-1&keywords=ipazzport

Apologies if the link eventually dies, which it might / will. ;)
[Fire TV Q&A, Help & Troubleshooting] hansly1985:
[IMG="Chinese program to fix Rii I8 Mini KeyBoard"]https://cdn1.imggmi.com/uploads/2018/4/30/8342dad16bcf02fbaca35c4330cab619-full.png[/IMG]

Hi Guys,

I know it's late but this program can help fixing Keyboard problem, if you find it please share it.
[Fire TV Q&A, Help & Troubleshooting] Keror0:
but this seems a Windows program, how can that help on keyboard use with Android?
[Nexus 7 (2013) Android Development] zaclimon:
Simple, Powerful, Stable. Here's Quanta for the Nexus 7 2013 (Flo/Deb)

Disclaimer: Your warranty is now void, use at your own risk. Don't blame me for anything because YOU decided to make these changes.

Note: This kernel is made for Android 5.1 (Lollipop) up to Android 7.x (Nougat) For earlier versions, please refer to Sabermod franco.Kernel on post 3.

Features:

- Based upon the official franco.Kernel source

- Compiled with the latest Cortex-A15 optimized UberTC 5.x with some kernel based optimizations + Graphite

- Linux 3.4.109 (3.4.0 from V5 onwards)

- AOSP/CM compatible

- Deb compatible (From V5 onwards)

- F2FS compatible

- DT2W/S2W support

- Wake Gestures Support

- Faux Sound

- Ability to force the touchscreen driver (if there's one you like for some reason)

- XPad support

- Support for android-keyboard-gadget (You can use your device as a keyboard/mouse for your PC)​

Download:

AOSP: AOSP Download Folder

CM: CM Download Folder

Mirror​

Installation:

1. Install using CWM/TWRP

2. Profit​

Sources:

Kernel Source (quanta-7.x)

Anykernel2 Source (flo-7.x)​

Thanks:

[MENTION=3292224]franciscofranco[/MENTION] [MENTION=4974050]TheMrcool212[/MENTION] [MENTION=2002216]jolinnard[/MENTION] [MENTION=4684315]flar2[/MENTION] [MENTION=3847629]Tk-Glitch[/MENTION] [MENTION=4559618]CTCaer[/MENTION] [MENTION=3332811]faux123[/MENTION] [MENTION=4544860]osm0sis[/MENTION]​

​
[Nexus 7 (2013) Android Development] zaclimon:
Changelog

V14: (03/01/17)
- Updated for Android 7.x support (Nougat)
- Merged security updates up to December

V13 (18/09/16)
- Merged security updates for September (Includes CVE-2016-2059 and CVE-2016-5340)

V12 (21/08/16)
- Merged security updates for August
- Patched Quadrooter exploit (CVE-2016-5340)
- Updated F2FS

V11 (16/07/16)
- Merged security updates for July
- Performance improvements (From Franco's release)
- Faster boot up time (From Franco's release)

V10 (11/06/16)
- Merged June security patches (Important)
- Updated F2FS

V9 (23/05/16)
- Reverted CPU-Boost to use mako_hotplug instead
- Interactive should be more power-efficient when the display is off
- Updated F2FS
- Made Software CRC toggable
- Misc security fixes

V8 (09/03/16)
- Reverted faulty commits that was causing the device to do panics
- Updated values for Interactive and cpu_boost
- Updated F2FS
- Misc Fixes/improvements

V7 (16/01/16)
- Rebased from Franco's sources (alonside the ramdisk changes)
- Updated F2FS
- Tweaked the performances profiles for CPU Boost

V6.1 (27/12/15)
- Fixed flashing for Deb devices

V6 (24/12/15)
- Merged 6.0.1 kernel sources

V5 (12/11/15)
- Initial Android 6.0 (Marshmallow) release
- Rebased from Google's 3.4 kernel source
- Added official support for Deb (It was half-baked in Lollipop)
- Compiled using the latest UberTC optimized for Cortex-A15 chipsets

V4(25/09/15)
- Linux 3.4.109
- GPU drivers reverted to a 5.1.1 state (Fixes Chrome scrolling lag)
- Updated the F2FS drivers
- Updated XPad support for Xbox One controllers
- Battery power saving optimizations from Nvidia
- Misc optimizations/fixes

V3(15/05/15)
- Merged 5.1.1 kernel sources.

V2(14/05/15)
- Linux 3.4.107
- Fixes for CM related slowdowns
- Patches from Mako (Filesystem optmizations, optimised LMK from Motorola, etc)

V1(18/04/15)
- Linux 3.4.106
- Support for Wake Gestures
- Support for USB Host Mode Charging
- Tweaked the performances profiles from FKU
- Support for android-keyboard-gadget
- Removed the 192 MHZ CPU freq.
[Nexus 7 (2013) Android Development] zaclimon:
Quanta Tweaks

All your tweaks are now regrouped into the app I've developped. No more hassle in tweaking 10 files/5 different apps togheter. It also has a franco.Kernel shortcut so your tweaking experience won't be stopped when trying to reach it.

https://play.google.com/store/apps/details?id=com.zaclimon.quantatweaks

It includes various tools and a beautiful user interface to enhance your experience even further!

Forced touchscreen

I've implemented CTCaer's forced touchscreen update in case you have some issues with your touchscreens. More info on his implementation here:

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

If you have some suggestions, please request them in the thread or send me a PM. :)

Sabermod franco.Kernel information (For 4.4 up to 5.0, Deprecated)

- Note: r17.2 is a Kitkat (4.4) build, r20 is a Lollipop (5.0) build.

- Compiled with SaberMod GCC 4.9.3 with Ofast optmisations + Graphite + other optimisations

- Linux 3.4.104

- Supports the LTE-enabled Nexus 7 2013 (Deb) (Kitkat builds)

- AOSP/CM compatible

- F2FS compatible

- DT2W/S2W support (Wake gestures support for Kitkat builds)

- Faux Sound

- Ability to force the touchscreen driver (if there's one you like for some reason)

Download:

AOSP: AOSP Download Folder

CM: CM Download Folder

Installation:

1. Install using CWM/TWRP

2. Profit

Sources:

Kernel Source (sm-5.0 and sm-5.0-cm)

Anykernel Source (flo-5.0)

Changelog

R20:
Rebased off Franco's Lollipop source
Touch control script is now situated in /system/etc/touchcontrols.sh (init.d compatibility reasons)
Compiled using the latest 4.9.3 SM toolchain

R17.2:
Merged the latest patches from the franco flo repository (Interactive stuff mostly)
Merged all the latest patches from Mako (Hotplug, Interactive, misc)
Merged some patches from Hammerhead (Including the Nvidia's power efficiency patches)
Deb Support
Linux 3.4.104
Added support for Wake Gestures, be sure to use the xposed module as well. (Also added their values in the 91touchcontrols init.d script)
Added support for FauxSound alongside with the franco sound patches (Please don't use both at the same time...)
Merged f2fs patches up to 10/10/14 (Shouldn't have any problems with fsck right now)
Compiled with the latest SaberMod toolchain.

R17:
Initial release
[Nexus 7 (2013) Android Development] 0l1v3rof:
Looks good! Just flashing now. How much is gained performence wise compared to the original kernel?
[Nexus 7 (2013) Android Development] rebretz000:
So far loving the kernel. Thank you for providing it.

I was trying to enable double tab to wake but the setting wouldn't stick using trickster mod. And I can't locate it I'm Franco control
[Nexus 7 (2013) Android Development] 0l1v3rof:
Franco kernel updater as far as I know does not change screen wake settings. Trickster mod works for me
[Nexus 7 (2013) Android Development] zaclimon:
Well this is why I've provided an init.d script in which you can enable/disable dt2w and s2w and their advanced options. :p

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Android Development] habylab:
Thank you so much for this. Do I just flash and get the updated touchscreen drivers, or do I have to enable them?

Sent from my Nexus 8 (2015). Running a custom ROM and kernel. My phone is currently a Galaxy S3! Tapatalk'd
[Nexus 7 (2013) Android Development] DMF1977:
Is this kernel from the future? If so, I must try it!! Thank u.
[Nexus 7 (2013) Android Development] zaclimon:
Well you have to find the touchscreen driver you need. Then you need to find its path and write it down into /sys/devices/i2c-3/3-0010/update_fw. It would have been easier make to make some script that would overwrite or maybe the value gets saved up. I would need to check further myself.

Envoyé de mon Nexus 7 en utilisant Tapatalk

Nope you aren't dreaming, it's from the present and you'll won't regret it! :)
[Nexus 7 (2013) Android Development] morbidj:
Thank you man I run liquid ROM which is built with saber mod optimizations..
[Nexus 7 (2013) Android Development] habylab:
Ah okay, interesting! I'll have a look at some point.

Sent from my Nexus 8 (2015). Running a custom ROM and kernel. My phone is currently a Galaxy S3! Tapatalk'd
[Nexus 7 (2013) Android Development] coffeehandle:
They right things the opposite way across the seas
[Nexus 7 (2013) Android Development] 0l1v3rof:
[MENTION=4217103]zaclimon[/MENTION]

... DtW is random and works 90% of the time, I dont know if you can improve this but of ElementalX is works all the time. I have edited the config file and disabled all the stuff like Dtw in a certain angle (Landscape and portrait etc). I don't know if this will have any effect on the reliability so I have added it in.
[Nexus 7 (2013) Android Development] DMF1977:
I was talking about the date of the kernel in the op... Just being stupid.:p
[Nexus 7 (2013) Android Development] zaclimon:
Hmm that's strange, it's been working flawlessly for me. Have you tried to disable the pwrkey_suspend? Maybe it can resolve your problem because the code is the exact same one as of elementalx.

Yeah I think this is what he was referring to.

US (and maybe GB) way of writing dates : MM/DD/YY

The rest of the world way of writing dates: DD/MM/YY

Its a bit confusing at first maybe for you guys but it looks more logic that way. (in my perspective anyway)

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Android Development] 0l1v3rof:
Yes I have already disabled pwrkey_suspend... I have been testing a little more and sometimes it needs 4 taps to turn the display on. When it does this it works perfectly for a short while and then the problem arises again.

GB uses DD/MM/YY. As far as I know only the US has the month first.
[Nexus 7 (2013) Android Development] zaclimon:
Hmm this really is weird. And you said it was working fine with elementalx right? In that case, I'll check something then.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Android Development] 0l1v3rof:
ElementalX was working perfectly fine. It's really strange and I can't see any reason why. If you can't do anything about it then that's perfectly fine ( just in case you think I'm nagging you to find a fix)
[Nexus 7 (2013) Android Development] habylab:
I always thought linaro added to file size, how is this less?! Works well!

Sent from my Nexus 8 (2015). Running a custom ROM and kernel. My phone is currently a Galaxy S3, end of August an HTC One M8! Tapatalk'd
[Nexus 7 (2013) Android Development] SHABBYLEA:
For me, apart from some strange behaviour with YT, everything is running fine...

Cheers....
[Nexus 7 (2013) Android Development] quickdraw86:
Since you were looking for feedback,

I spread quantum particles through my device, unlocked the future, and rated your app five stars, as it works well and is aesthetically pleasing. File system converter is a nice feature, beats the other PITA conversion methods. BTW, I've been running quantum v3 CM for weeks on the two CM ROMs I like, no unusable lag or YouTube issues at all here. Nice work!
[Nexus 7 (2013) Android Development] SHABBYLEA:
About the YT issues... I think it depends on the ROM. I'm running Tesla ATM and have no YT problems whatsoever...on some ROMs I do....
[Nexus 7 (2013) Android Development] quickdraw86:
Hmm yeah. There's quite a few potential variables that could affect YT as well. Use of alternative GPU settings, custom kernels, or DPI settings could all cause strange playback issues on YT. Not sure if that's your problem, but remember you saint something about issues with some resolutions before.