yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Incredible 2] echow2001:
Are you in fastboot mode? You may have to select fastboot from the HBOOT menu first.
[Verizon Droid Incredible 2] Sobek5150:
Did you ever find a fix? Just decided to break out my old Inc 2 to root and have EXACTLY the same problem. Will probably just forget it now, but thought id check first.
[Verizon Droid Incredible 2] echow2001:
you need to follow this guide if you are on win8 and above to get older fastboot htc devices to work. http://xdaforums.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
[Verizon Droid Incredible 2] Sobek5150:
Greatly appreciate that link. Thank you!
[Verizon Droid Incredible 2] echow2001:
no problem, glad to see people tinkering with older devices, even though I don't have these phones anymore I still enjoy stopping by the forums every once in a while. And hey, I also upgraded from the dinc2 to the ls990 :p
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Thorstenk:
Hi

my GPS stopped working, I can't fix satellites. I have the feeling that it is a hardware problem as factory resets / switching to older firmware versions didn't sole the problem.

Is there any way to replace the GPS module? Where is it located? Is there any cable or contact that could be loose?

Thanks in advance

Thorsten
[Android Q&A, Help & Troubleshooting] MaruMaxX:
Hello,

1) I’m looking for the official rom of kyros mid7014 (tcc8902) or clones akai mid7034c,

2) I already found the kyros mid7012 rom it’s pretty similar to mid7014 i install it, but the touch screen doesn't work i think because the mid7012 it’s a resistive and the mid7014 a capacitive is there a way to modify the mid7012 rom to work on a capacitive screen?
[Android Q&A, Help & Troubleshooting] coco1476:
Hi [MENTION=7266762]MaruMaxX[/MENTION], do you still have the rom for the mid7012 rom please? I really need it and cant find it anywhere
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
I am having an issue where the touch screen seems to be unresponsive for a short time after unlock. For instance, if I unlock the phone via fingerprint, pattern, or slide the first touch doesn't respond and I have to tap whatever app or item I am trying to use. I'm using Cataclysm ROM with the most recent ElementalX kernel. Maybe it's a ROM/Kernel thing and I should try stock but just wanted to ask here.
[Nexus 6P Q&A, Help & Troubleshooting] dl200010:
It does sound like a ROM/Kernel issue to me. I would suggest NANDROID and test stock.
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
Yeah, you're probably right.
[Nexus 6P Q&A, Help & Troubleshooting] dl200010:
NANDROID it so you can go back if that does not fix it.
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
So I turned on "Show Touches" in developer settings so I could see if my touches were registering and I have discovered that sometimes when I unlock the phone there is a touch dot on the screen like something is registering a touch. When I tap the screen it goes away but doesn't open the app I tapped. It then disappears and taking the app again works. Wonder wth is going on. I do have a screen protector on. Wonder if it is that.

Nexus 6P
[Nexus 6P Q&A, Help & Troubleshooting] dl200010:
Is the touch spot in the same location every time? I have not actually ever heard of a screen protector doing that, but anything is possible.
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
Nope. Here are some examples...http://imgur.com/i3qKrW0 http://imgur.com/3gQrlua

http://imgur.com/acY2PgT

Sent from my Nexus 6P
[Nexus 6P Q&A, Help & Troubleshooting] globen:
I have this same problem
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
What are you doing about it? I'm thinking I'm going to call google.

Sent from my Nexus 6P
[Nexus 6P Q&A, Help & Troubleshooting] globen:
Its annoying to say the least...let me know what they say
[Nexus 6P Q&A, Help & Troubleshooting] toknitup420:
Have you verified this happens on stock.
[Nexus 6P Q&A, Help & Troubleshooting] dl200010:
Are you running on the factory image?
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
RMA'd

Sent from my Nexus 6P
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
Just got my rma device and it's still happening. So it has to be a kernel issue or an app. I'm on the latest stock 6.0.1 security update. Need to find the stock kernel.

Sent from my Nexus 6P
[Nexus 6P Q&A, Help & Troubleshooting] dl200010:
Factory images are here:

https://developers.google.com/android/nexus/images

Or you could just try another ROM
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
Pretty sure I've figured out the cuplrit. Seems as though the double tap to wake gesture for elementalx is causing it. If you touch the screen when locked it holds on to that touch waiting for the second touch. Turned it off and haven't had it since going on two hours.

Sent from my Nexus 6P
[Nexus 6P Q&A, Help & Troubleshooting] dl200010:
Well than. Here is the answer! Now it all makes sense! I was searching like crazy and racking my head over this, because I just love a problem. Thank you for letting me know.
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
Looks like it hasn't been completely fixed but it helps. I've only had it happen a few times since then. Still need a fix.

Sent from my Nexus 6P
[Nexus 6P Q&A, Help & Troubleshooting] SlimSnoopOS:
There won't be a fix to double tap to wake. How it behaves, whether it works or has issues, is due to Google's code. Flar2 just enables the option for the user in ElementalX.

Edit: only thing I could suggest is try flar2's Wake gestures app or stick with Sweep2Wake.
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
I'm now testing on the stock kernel. Will report back.

Sent from my Nexus 6P
[Nexus 6P Q&A, Help & Troubleshooting] flar2:
Elementalx is not the cause of your problem. Please don't spread misinformation.
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
No issues on the stock kernel for the past few days. [MENTION=4684315]flar2[/MENTION] says it's not his kernel so I'm not sure why I don't have issues in stock kernel but do on his.

Sent from my Nexus 6P
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
Not touch issues on stock kernel now for almost a week.

Sent from my Nexus 6P
[Nexus 6P Q&A, Help & Troubleshooting] maanse:
Ive been having a similar problem with my 6p. Only for me its only the bottom right of the screen that the touch wont respond after unlock, the rest of the screen is fine... Then after a minute or so it all works fine again. Only been happening since flashing custom ROM. I first noticed it using using purenexus (no additional kernel flash).. thinking it was an issue with that ROM i changed to cataclysm and flashed elementalX (my fave combo from my nexus 4 days) but im still getting the issue. So i dont think its a particular rom or kernel causing it.
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
The only way to know is to test on stock. Complete stock.

Sent from my Nexus 6P
[Nexus 6P Q&A, Help & Troubleshooting] maanse:
Ok its been almost 2 weeks totally stock, not a single issue with the touch screen! So, while im not blaming any particular rom or kernel or anything, it definitely seems to be an issue with something custom. To root and flash i followed the guide here at XDA http://xdaforums.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
[Nexus 6P Q&A, Help & Troubleshooting] Matrix_19:
Edit : I was wrong
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
Anyone have an update on this? I recently went back to a custom kernel after running stock android rooted with no issues. After flashing the custom ROM Chroma and having no problems on the Chroma stock kernel I flashed ElementalX to see if the latest version had fixed the issue after some time off. Within a day it was happening again. Still have no idea what is causing it?
[Nexus 6P Q&A, Help & Troubleshooting] Krunk83:
So I have figured out how to replicate it. Turn on "Show touches" in developer options. When the screen is off, with a custom kernel installed, tap the screen a few times and then turn on the screen via the power button. You will then see the false touches. I am on my third phone and happens every time with a custom kernel installed. Why?
[Nexus 6P Q&A, Help & Troubleshooting] ezio84:
Are you using Nova Launcher?

Try to open its settings, then disable "Aspect --> Expansion action with root" if enabled.

I noticed the same delay with that option (maybe it was caused by the SU service not responding quickly).

Furthermore, after doing that step you can also go in the developer settings and set "Animator duration scale" to 0.5x or 0.8x.
[Nexus 6P Q&A, Help & Troubleshooting] dubluv17:
I just wanted to contribute to this thread, since it's basically the only one I can find regarding this issue. I have it, and it seems to only present itself with custom kernels. Stock kernel works great. Does anybody know what kernel setting might be affecting this?
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
Hello dear Xperia T Users :)

since we lost Whiteneo we all got a big hearthurt ;-( but now its time to go on! I managed to build a booting CM13 build for mint! Much thanks go to [MENTION=5122093]WhiteNeo[/MENTION] for his work so far (that i used)

THIS IS NOT FOR DAILY USE!!! IM NOT RESPONSIBLE FOR DAMAGE TO YOUR DEVICE!!!

(link will come later here.... for alpha 1 testing please m me)

So Alpha 1 is booted up.... but there is LOT OF WORK to do!

whats working?

- RIL ( 3g + telephony)

- WIFI

- Touch

- Vibrates

- sound

- storage

- gps

- bluetooth

- sensors

whats not working?

- camera

the other stuff is untested!!!

so now if you want to help me with this cm13 bringup please pm me! ^^
[Sony Xperia T, TL, TX, V] |>/\nte:
Thank god there's still development the xperia t. I'm eagerly waiting for more into this. If sound (and preferrably sdcard) is fixed, I'm offered for testing.
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
well im working on sound atm... need to figure out whats wrong (maybe i need newer drivers)
[Sony Xperia T, TL, TX, V] dantefff:
The only attempt is a good new for our old devices!
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
got the sound fixed :D

if someone is willing to test then i upload the rom!
[Sony Xperia T, TL, TX, V] FcukBloat:
good luck with this dear! will probably resume my old T soon when I'll get it again will be available for testing :)
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
nice to hear :)

im uploading todays latest build atm... its really an alpha (no storage you know?) but well i need some testers to find stuff i didnt checked yet
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
-> link removed <-

DO NOT TRY TO FORMAT SDCARD AS INTERNAL!!!!
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
aaaand storage fixed 8-)

uploading for testers.....through dsl 1000 this will need a while

Edit: aborted upload... dont have 2hours for that atm... maybe frieday
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
so here it is:

https://www.dropbox.com/s/0x8zkmmwn736l0r/cm-13.0-20160210-UNOFFICIAL-mint.zip?dl=0

WARNING!!! if your sdcard0 is shown as "damaged" within android settings->storage DO NOT FORMAT it in android!!!

if this is the case... reboot to twrp... save all your stuff from internal sdcard to pc.... and format it IN TWRP (wipe -> advanced -> change fs -> exfat )

this is necessary due to new voldmanager

rules for testers:

known bugs:

- camera

- bluetooth

- gps

do not report the bugs above! i know it and working on it (next goal is camera)
[Sony Xperia T, TL, TX, V] |>/\nte:
I flashed the kernel via flashtool and I can't get into recovery (I tried pressing all of the phone's buttons [in all combinations and each separetly]), I tried flashing the stock i.c.s. and I still can't get the phone to boot into recovery. Do we have to flash the rom from an already existing recovery?
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
well i used my existing neorecovery... or simply adb reboot recovery... well thats another bug ( i did not noticed yet) you cant enter recovery with keycombo.... flash neokernel and flash with this recovery

EDIT: this bug i have no focus on.... i will soon implement the new sony init and then this will be fixed... but that is at a later point of my list
[Sony Xperia T, TL, TX, V] samantafs:
hello dear SdtBarbarossa

i install this rom on my xperia tx and surprisingly it works and boot normally and in first view everything is ok but my screen is rotated and upside down :D

SdtBarbarossa plz help me to fix this issue i love to test your rom

love you
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
this rom is not for XTX... its XT only... i will fo a XTX build also soon
[Sony Xperia T, TL, TX, V] samantafs:
thanks to you

it looks good

my phone is going crazy "screen is rotated and touch sensor working mirrorly" :D :laugh: :eek:

i am waiting for proper build :victory:

thanks for your hard working
[Sony Xperia T, TL, TX, V] alial04:
Haha funny that it even booted ?
[Sony Xperia T, TL, TX, V] WhiteNeo:
Awesome work mate! :)

Keep going, you'll make it! :good:
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
- fixed gps

- decoupled from msm8960-common

- new sourcebuild sony-init

now you can push vol+ for fotarecovery and vol- for kernel-inbuild recovery
[Sony Xperia T, TL, TX, V] |>/\nte:
Testing the 2nd alpha build

I put a good 6-7 (give or take) hours on my phone running the 2nd alpha build. It's very fast, butter-smooth and really stable for what it is. I've encountered (almost) no weird stuff whatsoever while using the phone. Here's a complete list of the things I tested (what's working and what's not). Note that I used the phone like I would normally do (absolutely realistic to everyday usage - lots of video streaming and some browsing):

Working: Wi-fi

Mobile data (I get hspa+ with no problem at my area)

Vibration [for your private times ( ͡° ͜ʖ ͡°) ]

Notification led

Video playback (locally stored) (tested at 1024*600, 720p and 1080p - all videos were played smoothly)

Music playback

Sound (both the speaker and the hearing aid)

Phone calls

Messaging

Video streaming (youtube and kissanime were tested - all from the stock browser)

Internal storage (it shows as "damaged" at first boot - fix is provided by SdtBarbarossa)

Not working:

Camera (only accessible via the lockscreen - when launched you'll always get a "unable to connect to the camera" message)

Auto screen rotration (for the time being you can use an app called "set orientation" to force landscape orientation. Used it on my xperia t and it works just fine)

Access to recovery (no button combination is working - you need to have the phone connected to pc and use a.d.b. to reboot to recovery - other than that it works perfectly)

Bluetooth

N.f.c. (it does turn on but I can't test it without the bluetooth working - question mark on this one)

Proximity sensors

Other than that, the only times I found the rom to be a bit choppy is heavy scrolling (scrolling like a retard in a heavy page [e.g. facebook]) and video streaming when not in full screen. Also, some quick toggles are only visible when arranging the whole thing (e.g. torch, invert colors), but they cannot be used since they're hidden. Also, a section in the sound settings (it has to do something with vibration) causes the settings app to force close every time it's being opened. Despite this, I think the rom can be used as a daily driver if the camera is not a concern.

If there's anything you want me to test out, mention/quote me in this thread (or p.m. me, I'd prefer the first one though) and I'll test it out for you.
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
Thank you for the test report :)

1. Camera seems to be harder to fix then i thougt... this may take some time

2. i will test that in todays build ... i did not noticed that yet (not using it)

3. with newest build acess to recovery is fixed and optimized

4.yea thats my next target

5.NFC is working for me with NFC tags

6.i will have a look on that
[Sony Xperia T, TL, TX, V] zakcaree:
Can't wait to test this one out, can't touch my sd internals for now, but once the sd issue is fully fixed in the later alpha release', I'll be then joining the pack! BIG props to [MENTION=6248658]SdtBarbarossa[/MENTION] for giving this device a shot at CM13 and [MENTION=5122093]WhiteNeo[/MENTION] for his awesome previews builds with CM12.1. Really looking forward to having this as daily driver! :good:
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
there will be no change related to the internal storage.... internal sdcard as a ext4/f2fs partition is depricated and i dont think there is a way to make this working properly.... vfat is the new stuff
[Sony Xperia T, TL, TX, V] zakcaree:
Is that so, then I guess I'll give it a shot, will read more into this storage new stuff, Q: do I have to redo the sd-fix when I nandroid restore your build (or not coz it's nandroid)?.
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
if you backup/restore with twrp then twrp will always use the filesystem that was used before... so yes... BUT normally you dont backup/restore a internal sdcard because its damn too large... i would say wait for atleat the camera to be fixed so this can be used daily

Edit: BTW once formated to exfat your internal sdcard can also be used with cm12.1 normally
[Sony Xperia T, TL, TX, V] zakcaree:
Yep, not planning on backing up my whole internal though as that would eat my remaining storage, will wait for your next build on camera fix. Cool, I'll try exfat format once I test this out. Thanks!
[Sony Xperia T, TL, TX, V] |>/\nte:
Actually the SD card problem is fixed. All you have to do is boot into the recovery (use a.d.b.) and change the SD card's file system to exfat. It's provided by SdtBarbarossa at the first page of this thread. Internal sdcard works fine after that.
[Sony Xperia T, TL, TX, V] zakcaree:
Yes, I'll try that in a few days, I mean actually I can't for now touch my phone as I'm currently using it for work, but I'll report here soon as I try it out. Thanks anyway.
[Sony Xperia T, TL, TX, V] M00ny-ONE:
Hey m8

I want to help you building the CM13 for the mint device . i dont know how but i can test actively & give you feedback rightaway

i registered in here on XDA finally :D
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
https://github.com/sdtbarbarossa

sourcecode can be find here (use cm12.1 revision... not cm13... i pushed to wrong branch )
[Sony Xperia T, TL, TX, V] Indy500xl:
Does your rom use one partition on internal flash or does it use 2 partitions as Whitneo's 12.1? If it uses 2 partitions, do I have to make one partition as in the tutorial for Whiteneo's 12.1? Android or better the apps doesn't see the second internal partition so the space on the flash runs low very quickly.
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
it uses 2 partitions just like normal
[Sony Xperia T, TL, TX, V] Indy500xl:
Hmm...is there a way to tell the apps to use the sceond (bigger) partition? Standard is they use the small partition which is full very quick with only a few apps and the big fat second partition can't be used. There is no way to move the apps to the second partition because the OS doesn't "see" this partition at all. Only moving to external sd card is possible. But why should I waste the space from the second partition....

The 2 partition layout doesn't make any sense.
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
technically its possible to "swap" /data and /sdcard so you got 4gb for apps and 2gb for pictures
[Sony Xperia T, TL, TX, V] lubik1:
Bluetooth

Hi I try fix Bluetooth. Flash in recovery... and report...
[Sony Xperia T, TL, TX, V] |>/\nte:
We now have bluetooth. The device is being recognized as "xperia tx". Tried sending 1 image via nfc and 1 straight via bluetooth from my xperia sp to my t. It's working. Thanks for the fix mate.

[MENTION=6248658]SdtBarbarossa[/MENTION]
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
i need a fix in source ;-(

still trying to get cam running... no cam = no use
[Sony Xperia T, TL, TX, V] lubik1:
I can fix it, but it's not a source fix =)

[MENTION=6248658]SdtBarbarossa[/MENTION] can you build CM13 kernel for Xperia V? I have problem with RIL part in my ported ROM.
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
well i can build a XV rom.... but i wontn

... since i teamup with codezero .... so he will release XV if we are done or if he want
[Sony Xperia T, TL, TX, V] 1ch1go27:
Im so happy that someone continues the xperia t sage. I hope it will get as great as White neos Homebuild.
[Sony Xperia T, TL, TX, V] pietruccio1995:
Update?

Lord Barbarossa, no new update for the rom?
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
Im still trying to get the Camera working... [MENTION=2233641]Adrian DC[/MENTION] is helping me much with that ! so i hope we may get it working :)
[Sony Xperia T, TL, TX, V] FcukBloat:
at last resumed my old T.. would like to test this but can't find the link for the build with gps fixed and hw buttons combination for recovery writing? tia! :o
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
the build isnt uploaded thats why ;) will upload a new one soon
[Sony Xperia T, TL, TX, V] FcukBloat:
thanks mate will wait :o
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
https://www.dropbox.com/s/n40hi1dgpxfi1yf/cm-13.0-20160304-UNOFFICIAL-mint.zip?dl=0

here you go... accept it as a alpha!
[Sony Xperia T, TL, TX, V] FcukBloat:
thanks mate! trying it now :o rom is very fast, so promising thank you :o

the main problem i find so far is that i can't use the internal sd it seems. in settings > storage i see it as damage, and if i click on format, it says command failed.

so i only have a 2gb "internal memory" available, dunno where it is really located though. for this reason, even after flashing the bt fix posted earlier, i can't receive files via bt as it says missing sdcard where to save files. (in twrp instead i still see the internal sd and all the files inside it)

another problem i had after first boot (full clean install) is a FC about settings.apk, but didn't see it again later. and i had the same problem also in cm12.1 and aicp roms i tried (again clean installs) do you know the reason of this FC always comparing after clean flashing any rom?

thanks again for your work wish you the best and good luck especially for the camera!!! ;) :good:
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
the storage stuff you can fix by formating it to exfat in twrp (remember that will remove all pictures) see last pages for more info about that
[Sony Xperia T, TL, TX, V] FcukBloat:
thanks mate sorry I missed it. so I tried what you said but it seems it doesn't work :( i go to wipe etc, select sdcard, change filesysyem and choose fat (exfat is not present) then swipe to accept but i get the error "unknown MTP message type: 1"

and the sdcard is still ext4...

i then disabled MTP in mount section, tried again and now i don't get errors when changing the fs to fat, but in twrp i still see sdcard as formatted in ext4.. and after rebooting to mm i still see it as damaged :( what am i missing?! tia

edit: can't even provide a log because in twrp i can export log to sdcard, then i see it in /sdcard/recovery.log, but after booting the phone can't find the sdcard and recovery.log file anywhere :(
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
flash whiteneos last boot.img so you get his twrp... then format the sdcard to exfat ... and then flash my boot.img again and boot
[Sony Xperia T, TL, TX, V] FcukBloat:
thanks mate but still no luck :(

got the boot.img from latest cm12.1 by whiteneo (did you mean that one?) and with that i could select exfat. but same error message about MTP. disabling MTP, again error disappears but I still see ext4 for the sdcard after changing the FS, and booting again with your kernel inside mm, still sdcard is seen as damaged :(

before trying cm12.1 and your cm13, I formatted the internal sdcard from stock 4.3 (settings - storage - format internal sdcard), could that be the problem?

i'm driving crazy would really like to test your build more deeply :(((
[Sony Xperia T, TL, TX, V] SdtBarbarossa:
hm... for now keep on cm12.1 ... maybe you do somwthing wrong i dont can see atm
[Sony Xperia T, TL, TX, V] Majonez89:
OMG Dude, this is the best rom ever made for this Phone.

It looks a bit faster and smoother than CM12.1 and original CM12 roms for me, and good for daily use (except camera and proximity sensors).