Hi Can anyone know can I start teh camera from S5,G901F to S5,G900H
from xda-developers http://ift.tt/20Pz83L
via IFTTT
lundi 18 avril 2016
S5 as a Dash Cam. App that can duo record
Started driving as Uber and could use a dashcam. Can't afford a new 2 channel dash cam yet so I would like to use my S5 spare I have as a dash cam. Was wondering if a dual recording app existed and if so, what's the name?
from xda-developers http://ift.tt/1qSB7rH
via IFTTT
Potential fix for touchscreen dead zones after MHC19J
Background:
There is a well documented problem for some charger/device/voltage combos where the touchscreen will become unresponsive when connected to the stock charger. Ultimately the problem is with the charger design but it appears Google made some attempt to mitigate the problem with software in the MHC19J release.
See this thread for the power adapter touchscreen not responsive details
http://ift.tt/1qSB5A8
Unfortunately in doing so it seems they may have put out a Synaptics touchscreen firmware that introduced a brand new problem for folks who've never had any touchscreen problems before, affecting them during *normal* usage rather than the more isolated case of only during charging.
Basically the symptoms are you start getting dead zones when you leave your device untouched for a couple of seconds. You can cycle the screen on/off to reset the touchscreen but the problem eventually comes back again. It even occurs upon startup when you need to enter your lock code or pattern, making it difficult to get into your device.
My theory is Google put out a new synaptics touchscreen firmware that adjusted the sensitivity of the touchscreen to compensate for the "noise" being generated by the bad power adapters. The change may have been too aggressive as it seems to have had a side effect of being too insensitive for some folks' touchscreen variations resulting in dead zones.
See these threads for the touchscreen dead zones after MHC19J details
http://ift.tt/1qSB5Aa
http://ift.tt/1qSB5Ac
So normally you'd just flash an older factory image and everything would be back to normal. Unfortunately for touchscreen firmware, flashing older factory images will have no effect. Once you have the new touchscreen firmware it will stay in place until a newer one comes out. Thus you can't actually get back to "true" factory by flashing the MDA89E factory image.
There is a way you can force a touchscreen firmware flash if you are rooted. This will be described in the next post.
I do NOT know for sure if the touchscreen firmware is definitely the cause of this issue. The symtoms really point to it, but it is just a theory right now. I really don't have the flexibility to break my touchscreen to test a potential fix, so folks who are affected will need to try this out and confirm.
There is a well documented problem for some charger/device/voltage combos where the touchscreen will become unresponsive when connected to the stock charger. Ultimately the problem is with the charger design but it appears Google made some attempt to mitigate the problem with software in the MHC19J release.
See this thread for the power adapter touchscreen not responsive details
http://ift.tt/1qSB5A8
Unfortunately in doing so it seems they may have put out a Synaptics touchscreen firmware that introduced a brand new problem for folks who've never had any touchscreen problems before, affecting them during *normal* usage rather than the more isolated case of only during charging.
Basically the symptoms are you start getting dead zones when you leave your device untouched for a couple of seconds. You can cycle the screen on/off to reset the touchscreen but the problem eventually comes back again. It even occurs upon startup when you need to enter your lock code or pattern, making it difficult to get into your device.
My theory is Google put out a new synaptics touchscreen firmware that adjusted the sensitivity of the touchscreen to compensate for the "noise" being generated by the bad power adapters. The change may have been too aggressive as it seems to have had a side effect of being too insensitive for some folks' touchscreen variations resulting in dead zones.
See these threads for the touchscreen dead zones after MHC19J details
http://ift.tt/1qSB5Aa
http://ift.tt/1qSB5Ac
So normally you'd just flash an older factory image and everything would be back to normal. Unfortunately for touchscreen firmware, flashing older factory images will have no effect. Once you have the new touchscreen firmware it will stay in place until a newer one comes out. Thus you can't actually get back to "true" factory by flashing the MDA89E factory image.
There is a way you can force a touchscreen firmware flash if you are rooted. This will be described in the next post.
I do NOT know for sure if the touchscreen firmware is definitely the cause of this issue. The symtoms really point to it, but it is just a theory right now. I really don't have the flexibility to break my touchscreen to test a potential fix, so folks who are affected will need to try this out and confirm.
from xda-developers http://ift.tt/20Pz3gH
via IFTTT
After repartitioning /dev/block/mmcblk0p15 is missing - mount /data (invalid argument
Hello,
I wanted to flash Android 6 on my Xperia S (32GB).
Bootloader + root are unlocked.
I downloaded the image and extracted the .zip file.
=> new cmd:
Now the TWRP 3.0 screen appeared.
The problematic part was now the reparitioning.
Here you can see the full output (I followed this steps: http://ift.tt/P01mt4)
The next step was
Changing the file system results in:
If I execute
I see that /dev/block/mmcblk0p15 is missing.
Can anyone help me out please?
Thanks in advance.
I wanted to flash Android 6 on my Xperia S (32GB).
Bootloader + root are unlocked.
I downloaded the image and extracted the .zip file.
=> new cmd:
Code:
fastboot flash boot recovery.img
fastboot reboot The problematic part was now the reparitioning.
Here you can see the full output (I followed this steps: http://ift.tt/P01mt4)
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 973824.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-14): 14
Command (m for help): n
First cylinder (769-954240, default 769): 42945
Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240):
Using default value 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table Code:
Now we will convert /data and /cache to F2FS.
Ext4 is not supported anymore on nAOSProm. You don't need to take care about the 16384 byte to reserve for encryption. TWRP will do it for you.
Wipe => Advanced Wipe => select Data => Repair or Change File system => Change File System =>F2FS =>Swipe to Change Code:
Mount Point /data
File system: f2fs
Present: Yes
Size: 0MB
Free: 0MB
Used: 0MB Code:
Could not mount /data and unable to find crypto footer.
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount /data (Invalid argument)
...done
Unable to mount storage
Failed to mount /data (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Failed to mount /data (Invalid argument)
MTP Enabled
Failed to mount /data (Invalid argument) Code:
fdisk -l /dev/block/mmcblk0 Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 954240 29161464 83 Linux Thanks in advance.
from xda-developers http://ift.tt/1qSB2V5
via IFTTT
[Request] Edge UX from S7 Edge for S6
Is there any way of getting all the edge features of S7 Edge for S6 , like an app ?
P.S. The app should mimic all the features on the S7 Edge.
P.S. The app should mimic all the features on the S7 Edge.
from xda-developers http://ift.tt/20Pz1Fm
via IFTTT
CAM PLUS does not charge phone!!! So don't lose the standard battery compartment!!!
So I did something very silly and manage to lose the standard battery compartment while I was using the CAM Plus. To my surprise the Battery does not actually charge when plugged in to the Cam Plus so I effectively have a large brick until I can source a standard battery compartment!
What a stupid design!
What a stupid design!
from xda-developers http://ift.tt/1qSAZJ1
via IFTTT
After OOS 3.0 - Signal drops
Hello together,
After updating the my OPT with the "official" OOS 3.0 Beta, I'm facing signal drops.
after each drop, my internet connection is broken, I cannot make calls anymore, and so on..
I need to restart my phone in order to use it again.
It happens at least once a day.
Attached a screenshot, you can see that the signal bar has an exclamation sign "!" next to it.
Do you know any solution for this ?
Thank you !
After updating the my OPT with the "official" OOS 3.0 Beta, I'm facing signal drops.
after each drop, my internet connection is broken, I cannot make calls anymore, and so on..
I need to restart my phone in order to use it again.
It happens at least once a day.
Attached a screenshot, you can see that the signal bar has an exclamation sign "!" next to it.
Do you know any solution for this ?
Thank you !
from xda-developers http://ift.tt/20PyZNR
via IFTTT
Inscription à :
Commentaires (Atom)