Hey guys. I'm so frustrated. I tried towelroot, framaroot, z4root,kingroot, something else the name escapes me. I have no access to a pc. Please advise. Thank you.
Affichage des articles dont le libellé est touch. Afficher tous les articles
Affichage des articles dont le libellé est touch. Afficher tous les articles
dimanche 1 mars 2015
samedi 28 février 2015
Area of Touch Screen not responsive!!? topic
My speakers had become distorted or blown so i bought 2 replacement speakers, i took the phone apart and replaced the lower speaker but when i got to the top speaker i noticed that i had received the wrong speaker. As i wont be getting a replacement speakers for a few days i decided to part reassemble the phone , all ribbon cables have connected, have replaced some but not all of the screws and slightly replaced the rear case but not fully clipped it back in place as i want to be able to easily remove it again once the top speaker has arrived.
Upon powering the phone on i have notice that a certain area of the screen doesn't seem to be responsive any more, it seem to be a vertical area going down the screen where the 'W', 'S' and 'Z' keys are on the keyboard!. Is this because i haven't fully reassembled the phone or have a buggered part of the touch screen when taking the phone apart?
Upon powering the phone on i have notice that a certain area of the screen doesn't seem to be responsive any more, it seem to be a vertical area going down the screen where the 'W', 'S' and 'Z' keys are on the keyboard!. Is this because i haven't fully reassembled the phone or have a buggered part of the touch screen when taking the phone apart?
[Q&A] [RECOVERY][tornado_348] TWRP 2.8.5.0 touch recovery [2015-02-27] topic
Q&A for [RECOVERY][tornado_348] TWRP 2.8.5.0 touch recovery [2015-02-27]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][tornado_348] TWRP 2.8.5.0 touch recovery [2015-02-27]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy! :)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][tornado_348] TWRP 2.8.5.0 touch recovery [2015-02-27]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy! :)
G2 Screen Touch problem topic
I am in Chinese D802 Software stock kitakat..
My dial pad 4 5 6 rows stop working..
I did factory reset two times..
But issue still persist..
So I flashed a European Stock Kitakat..
And now whole screen becomes..
Unresponsive...
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app
My dial pad 4 5 6 rows stop working..
I did factory reset two times..
But issue still persist..
So I flashed a European Stock Kitakat..
And now whole screen becomes..
Unresponsive...
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app
vendredi 27 février 2015
[RECOVERY][tornado_348] TWRP 2.8.5.0 touch recovery [2015-02-27] topic
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:


Tablet look:


CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Phone look:
Tablet look:
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
[TEST] [kernel] for Ubuntu Touch on Xperia Z1 Compact topic
Hi, after some ideas in my mind about true Ubuntu server on my phone I have done full changes to the kernel needed for Ubuntu touch but never tried real Ubuntu touch installation, I have done only kernel so if somebody need kernel you can try from here! Curently everyhing is patched and enabled needed for Ubuntu touch except CONFIG_ARM_UNWIND since android display stop working if I disable these configuration, everything other is enabled as you see in this:
I going to share kernel with you, compressed and uncompresed, allso sharing kernel modules with you, hope you get something usefull from all of them, at least hope somebody get Ubuntu touch working on our device, I never tried and probably will not. Enjoy!
Quote:
Checking config file for Ubuntu Touch specific config options. CONFIG_IKCONFIG is already set CONFIG_IKCONFIG_PROC is already set CONFIG_SYSVIPC is already set CONFIG_CGROUP_FREEZER is already set CONFIG_NAMESPACES is already set CONFIG_UTS_NS is already set CONFIG_IPC_NS is already set CONFIG_USER_NS is already set CONFIG_PID_NS is already set CONFIG_NET_NS is already set CONFIG_AUDIT is already set CONFIG_AUDITSYSCALL is already set CONFIG_AUDIT_TREE is already set CONFIG_AUDIT_WATCH is already set CONFIG_CC_STACKPROTECTOR is already set CONFIG_DEBUG_RODATA is already set CONFIG_DEVTMPFS is already set CONFIG_DEVTMPFS_MOUNT is already set CONFIG_DEVPTS_MULTIPLE_INSTANCES is already set CONFIG_ECRYPT_FS is already set CONFIG_ECRYPT_FS_MESSAGING is already set CONFIG_ENCRYPTED_KEYS is already set CONFIG_EXT4_FS_POSIX_ACL is already set CONFIG_EXT4_FS_SECURITY is already set CONFIG_FSNOTIFY is already set CONFIG_DNOTIFY is already set CONFIG_INOTIFY_USER is already set CONFIG_FANOTIFY is already set CONFIG_FANOTIFY_ACCESS_PERMISSIONS is already set CONFIG_KEYS is already set CONFIG_SWAP is already set CONFIG_VT is already set CONFIG_VT_CONSOLE is already set CONFIG_SECCOMP is already set CONFIG_SECURITY is already set CONFIG_SECURITYFS is already set CONFIG_SECURITY_NETWORK is already set CONFIG_NETLABEL is already set CONFIG_SECURITY_PATH is already set CONFIG_SECURITY_SELINUX is already set CONFIG_SECURITY_SELINUX_BOOTPARAM is already set CONFIG_SECURITY_SELINUX_DISABLE is already set CONFIG_SECURITY_SELINUX_DEVELOP is already set CONFIG_SECURITY_SELINUX_AVC_STATS is already set CONFIG_SECURITY_SMACK is already set CONFIG_SECURITY_TOMOYO is already set CONFIG_DEFAULT_SECURITY_APPARMOR is already set CONFIG_SECURITY_APPARMOR is already set CONFIG_SECURITY_APPARMOR_HASH is already set CONFIG_SECURITY_APPARMOR_UNCONFINED_INIT is already set CONFIG_SECURITY_YAMA is already set CONFIG_SECURITY_YAMA_STACKED is already set CONFIG_STRICT_DEVMEM is already set CONFIG_SYN_COOKIES is already set CONFIG_BT is already set CONFIG_BT_RFCOMM is already set CONFIG_BT_RFCOMM_TTY is already set CONFIG_BT_BNEP is already set CONFIG_BT_BNEP_MC_FILTER is already set CONFIG_BT_BNEP_PROTO_FILTER is already set CONFIG_BT_HIDP is already set CONFIG_XFRM_USER is already set CONFIG_NET_KEY is already set CONFIG_INET is already set CONFIG_IP_ADVANCED_ROUTER is already set CONFIG_IP_MULTIPLE_TABLES is already set CONFIG_INET_AH is already set CONFIG_INET_ESP is already set CONFIG_INET_IPCOMP is already set CONFIG_INET_XFRM_MODE_TRANSPORT is already set CONFIG_INET_XFRM_MODE_TUNNEL is already set CONFIG_INET_XFRM_MODE_BEET is already set CONFIG_IPV6 is already set CONFIG_INET6_AH is already set CONFIG_INET6_ESP is already set CONFIG_INET6_IPCOMP is already set CONFIG_INET6_XFRM_MODE_TRANSPORT is already set CONFIG_INET6_XFRM_MODE_TUNNEL is already set CONFIG_INET6_XFRM_MODE_BEET is already set CONFIG_IPV6_MULTIPLE_TABLES is already set CONFIG_NETFILTER is already set CONFIG_NETFILTER_ADVANCED is already set CONFIG_NETFILTER_NETLINK is already set CONFIG_NETFILTER_NETLINK_ACCT is already set CONFIG_NETFILTER_NETLINK_LOG is already set CONFIG_NETFILTER_NETLINK_QUEUE is already set CONFIG_NETFILTER_TPROXY is already set CONFIG_NETFILTER_XTABLES is already set CONFIG_NETFILTER_XT_CONNMARK is already set CONFIG_NETFILTER_XT_MARK is already set CONFIG_NETFILTER_XT_MATCH_ADDRTYPE is already set CONFIG_NETFILTER_XT_MATCH_CLUSTER is already set CONFIG_NETFILTER_XT_MATCH_COMMENT is already set CONFIG_NETFILTER_XT_MATCH_CONNBYTES is already set CONFIG_NETFILTER_XT_MATCH_CONNLIMIT is already set CONFIG_NETFILTER_XT_MATCH_CONNMARK is already set CONFIG_NETFILTER_XT_MATCH_CONNTRACK is already set CONFIG_NETFILTER_XT_MATCH_CPU is already set CONFIG_NETFILTER_XT_MATCH_DCCP is already set CONFIG_NETFILTER_XT_MATCH_DEVGROUP is already set CONFIG_NETFILTER_XT_MATCH_DSCP is already set CONFIG_NETFILTER_XT_MATCH_ECN is already set CONFIG_NETFILTER_XT_MATCH_ESP is already set CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is already set CONFIG_NETFILTER_XT_MATCH_HELPER is already set CONFIG_NETFILTER_XT_MATCH_HL is already set CONFIG_NETFILTER_XT_MATCH_IPRANGE is already set CONFIG_NETFILTER_XT_MATCH_LENGTH is already set CONFIG_NETFILTER_XT_MATCH_LIMIT is already set CONFIG_NETFILTER_XT_MATCH_MAC is already set CONFIG_NETFILTER_XT_MATCH_MARK is already set CONFIG_NETFILTER_XT_MATCH_MULTIPORT is already set CONFIG_NETFILTER_XT_MATCH_NFACCT is already set CONFIG_NETFILTER_XT_MATCH_OSF is already set CONFIG_NETFILTER_XT_MATCH_OWNER is already set CONFIG_NETFILTER_XT_MATCH_PKTTYPE is already set CONFIG_NETFILTER_XT_MATCH_POLICY is already set CONFIG_NETFILTER_XT_MATCH_QUOTA is already set CONFIG_NETFILTER_XT_MATCH_QUOTA2 is already set CONFIG_NETFILTER_XT_MATCH_RATEEST is already set CONFIG_NETFILTER_XT_MATCH_REALM is already set CONFIG_NETFILTER_XT_MATCH_RECENT is already set CONFIG_NETFILTER_XT_MATCH_SCTP is already set CONFIG_NETFILTER_XT_MATCH_SOCKET is already set CONFIG_NETFILTER_XT_MATCH_STATE is already set CONFIG_NETFILTER_XT_MATCH_STATISTIC is already set CONFIG_NETFILTER_XT_MATCH_STRING is already set CONFIG_NETFILTER_XT_MATCH_TCPMSS is already set CONFIG_NETFILTER_XT_MATCH_TIME is already set CONFIG_NETFILTER_XT_MATCH_U32 is already set CONFIG_NETFILTER_XT_TARGET_AUDIT is already set CONFIG_NETFILTER_XT_TARGET_CHECKSUM is already set CONFIG_NETFILTER_XT_TARGET_CLASSIFY is already set CONFIG_NETFILTER_XT_TARGET_CONNMARK is already set CONFIG_NETFILTER_XT_TARGET_CONNSECMARK is already set CONFIG_NETFILTER_XT_TARGET_CT is already set CONFIG_NETFILTER_XT_TARGET_DSCP is already set CONFIG_NETFILTER_XT_TARGET_HL is already set CONFIG_NETFILTER_XT_TARGET_IDLETIMER is already set CONFIG_NETFILTER_XT_TARGET_LED is already set CONFIG_NETFILTER_XT_TARGET_LOG is already set CONFIG_NETFILTER_XT_TARGET_MARK is already set CONFIG_NETFILTER_XT_TARGET_NFLOG is already set CONFIG_NETFILTER_XT_TARGET_NFQUEUE is already set CONFIG_NETFILTER_XT_TARGET_NOTRACK is already set CONFIG_NETFILTER_XT_TARGET_RATEEST is already set CONFIG_NETFILTER_XT_TARGET_SECMARK is already set CONFIG_NETFILTER_XT_TARGET_TCPMSS is already set CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is already set CONFIG_NETFILTER_XT_TARGET_TEE is already set CONFIG_NETFILTER_XT_TARGET_TPROXY is already set CONFIG_NETFILTER_XT_TARGET_TRACE is already set CONFIG_NF_CONNTRACK_ZONES is already set CONFIG_IP6_NF_FILTER is already set CONFIG_IP6_NF_IPTABLES is already set CONFIG_IP6_NF_MANGLE is already set CONFIG_IP6_NF_MATCH_AH is already set CONFIG_IP6_NF_MATCH_EUI64 is already set CONFIG_IP6_NF_MATCH_FRAG is already set CONFIG_IP6_NF_MATCH_HL is already set CONFIG_IP6_NF_MATCH_IPV6HEADER is already set CONFIG_IP6_NF_MATCH_MH is already set CONFIG_IP6_NF_MATCH_OPTS is already set CONFIG_IP6_NF_MATCH_RPFILTER is already set CONFIG_IP6_NF_MATCH_RT is already set CONFIG_IP6_NF_QUEUE is already set CONFIG_IP6_NF_RAW is already set CONFIG_IP6_NF_SECURITY is already set CONFIG_IP6_NF_TARGET_HL is already set CONFIG_IP6_NF_TARGET_REJECT is already set CONFIG_IP6_NF_TARGET_REJECT_SKERR is already set CONFIG_DNS_RESOLVER is already set CONFIG_IOSCHED_DEADLINE is already set CONFIG_SUSPEND_TIME is already set CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is already set CONFIG_CONSOLE_TRANSLATIONS is already set CONFIG_EVM is already set CONFIG_INTEGRITY_SIGNATURE is already set CONFIG_FHANDLE is already set CONFIG_DEFAULT_SECURITY="apparmor" is already set CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1 is already set CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0 is already set CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1 is already set CONFIG_SECURITY_TOMOYO_MAX_ACCEPT_ENTRY=2048 is already set CONFIG_SECURITY_TOMOYO_MAX_AUDIT_LOG=1024 is already set CONFIG_SECURITY_TOMOYO_POLICY_LOADER="/sbin/tomoyo-init" is already set CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER="/sbin/init" is already set CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1 is already set CONFIG_DEFAULT_MMAP_MIN_ADDR=32768 is already set CONFIG_DEFAULT_IOSCHED="deadline" is already set CONFIG_EVM_HMAC_VERSION=2 is already set CONFIG_ANDROID_PARANOID_NETWORK is already unset CONFIG_DEFAULT_SECURITY_DAC is already unset CONFIG_DEFAULT_SECURITY_SELINUX is already unset CONFIG_DEFAULT_SECURITY_TOMOYO is already unset CONFIG_DEFAULT_SECURITY_YAMA is already unset CONFIG_DEFAULT_SECURITY_SMACK is already unset CONFIG_SECURITY_APPARMOR_STATS is already unset CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is already unset CONFIG_SECURITY_TOMOYO_OMIT_USERSPACE_LOADER is already unset CONFIG_BT_HCIBTUSB is already unset CONFIG_BT_HCIBTSDIO is already unset CONFIG_BT_HCIUART is already unset CONFIG_BT_HCIBCM203X is already unset CONFIG_BT_HCIBPA10X is already unset CONFIG_BT_HCIBFUSB is already unset CONFIG_BT_HCIVHCI is already unset CONFIG_BT_MRVL is already unset CONFIG_AF_RXRPC is already unset CONFIG_KEYS_DEBUG_PROC_KEYS is already unset CONFIG_XFRM_MIGRATE is already unset CONFIG_XFRM_STATISTICS is already unset CONFIG_XFRM_SUB_POLICY is already unset CONFIG_COMPAT_BRK is already unset CONFIG_DEVKMEM is already unset CONFIG_NETFILTER_DEBUG is already unset CONFIG_IP_SET is already unset CONFIG_IP_VS is already unset CONFIG_RT_GROUP_SCHED is already unset CONFIG_ARM_UNWIND is set, unset it CONFIG_VT_HW_CONSOLE_BINDING is already unset CONFIG_FRAMEBUFFER_CONSOLE is already unset CONFIG_SPEAKUP is already unset CONFIG_CIFS_UPCALL is already unset CONFIG_CIFS_DFS_UPCALL is already unset CONFIG_KGDB is already unset Config file checked, found 1 errors that I did not fix. |
Alcatel One Touch M'Pop 5020D firmware update topic
My Android version is 4.1.1. and I got a notification about new firmware 01002. Does anybody know what is this firmware update about? I can't find any info about it and Alcatel support didn't replied to me. My phone just say this: "This update will improve the user experience and product performance. Please rest assured that you will not lose your data during the system update". This is not much helpful. :D
[Q&A] TWRP Touch Recovery v2.8.5.0 for Galaxy Young GT-S6310 topic
Q&A for TWRP Touch Recovery v2.8.5.0 for Galaxy Young GT-S6310
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for TWRP Touch Recovery v2.8.5.0 for Galaxy Young GT-S6310. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy! :)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for TWRP Touch Recovery v2.8.5.0 for Galaxy Young GT-S6310. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy! :)
jeudi 26 février 2015
[Q&A] [RECOVERY] Carliv Touch Recovery [ZTE V970] topic
Q&A for [RECOVERY] Carliv Touch Recovery [ZTE V970]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] Carliv Touch Recovery [ZTE V970]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy! :)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] Carliv Touch Recovery [ZTE V970]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Recovery] TWRP 2.8 touch recovery for Samsung S Duos 2 topic
Team Win Recovery Project 2.8.xx for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
ScreenshotsBugs!!
Time is shown wrong in recovery
Installation
1.Install samsung usb drivers,Download Odin, and my twrp recovery.
2.Open Odin 3.07
3.Switch off and Go into download mode(Home+Vol down+ power).
4.Put the recovery.tar file in PDA.(leave other options as they are)
5.Start Let it flash.After pass you can boot into twrp by Volup+power+home.
Downloads
1.
HTML Code:
<a href="http://d-h.st/iGvj" target="_blank">TWRP_RECOVERY.rar-7.82MB</a>Credits
Cyanogenmod team
Twrp team
SandPox
xda
mercredi 25 février 2015
[Q] Nexus 7 is not responding to touch, at all! topic
Hello.
I have recently run into a major issue where my N7 will not respond to touch at all. Checking the bootlog, there is an interesting message:
i.imgur.com (slash) qEe7pYr.jpg
Now, I know that is a bit dark to read, but here is the text:
The status flag hex code changes often, but I think it always starts with 0x1111.
Now, my touchscreen does not work in any location. Running CM12, it refuses to work. Opening TWRP or Multirom, no dice.
This complete lack of touch happened almost out of the blue. Sometimes, my device would develop an issue where it would refuse to acknowledge touches unless they were very firm. However, this is fixed with reboot. Thinking I had this same problem again, I rebooted and noticed my device not responding to touch at all. I then started logging the system, and noticed that ELAN error. I believe this is hardware, but I have no idea how to fix it. When tapping the back of the device, I hear it rattle a bit, like something is loose.
I've kept this device in great shape. It has not been exposed to drops, shock, moisture, or anything of the kind.
---
Primary OS: CyanogenMod 12, 2/24/2015 nightly
Kernel: ElementalX 3.4.0 Google Play Edition
Hardware Mods: None
I have recently run into a major issue where my N7 will not respond to touch at all. Checking the bootlog, there is an interesting message:
i.imgur.com (slash) qEe7pYr.jpg
Now, I know that is a bit dark to read, but here is the text:
Code:
QUP: I2C status flags: 0x111163c8, irq: 183
I2C slave addr:0x10 not connected
[elan] elan_ktf3k_ts_recv_data: i2c_master_recv errorNow, my touchscreen does not work in any location. Running CM12, it refuses to work. Opening TWRP or Multirom, no dice.
This complete lack of touch happened almost out of the blue. Sometimes, my device would develop an issue where it would refuse to acknowledge touches unless they were very firm. However, this is fixed with reboot. Thinking I had this same problem again, I rebooted and noticed my device not responding to touch at all. I then started logging the system, and noticed that ELAN error. I believe this is hardware, but I have no idea how to fix it. When tapping the back of the device, I hear it rattle a bit, like something is loose.
I've kept this device in great shape. It has not been exposed to drops, shock, moisture, or anything of the kind.
---
Primary OS: CyanogenMod 12, 2/24/2015 nightly
Kernel: ElementalX 3.4.0 Google Play Edition
Hardware Mods: None
TWRP Touch Recovery v2.8.5.0 for Galaxy Young GT-S6310 topic

Helloo readers... (^_^)/
Meet again with this cute guy.. :P hehehe .. OK back to topic. In this time i would like to share custom recovery with touch support for Galaxy Young GT-S310 that is TWRP v2.8.5.0. This custom recovery was developed by TeamWin and then I compile it for Galaxy Young.
Key Features :
- Ability to save custom recovery settings.
- Touchscreen driven with real buttons and drag-to-scroll.
- XML-based GUI that allows full customization of the layout true theming!
- Settings are saved to the sdcard and persist through reboots.
- Ability to choose which partitions to back up and which to restore.
- Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times.
And because this is v2.8.5.0, so What's new in 2.8.5.0 :
- Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution.
- Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state).
- Improve thread handling and move input handling into the main rendering thread to improve stability.
- Make MTP work even if unplugged and plugged back in.
- Unify scrollable list code and make kinetic scrolling feel more natural.
- Fix handling of mapped zip files for OTA updates (CM12 updater).
- USB keyboards should now work on all devices that support USB host mode via a USB OTG cable.
- Other small fixes and improvements.
Do you wanna try ? Let's follow this tutorial..
- Download TWRP_v2.8.5.0_royss_RC1.zip
- Restart the phone and go to CWM by pressing Volume Up + Home + Power Key.
- Install zip -> Search TWRP_v2.8.5.0_royss_RC1.zip
- Wait until the installation is complete and reboot.
But if you have not installed CWM in your device, follow this tutorial..
(you need PC/Laptop and odin to do this)
- Download TWRP_v2.8.5.0_royss_RC1.tar.md5
- Open Odin.
- Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons).
- Connect phone and wait until you get a blue sign in Odin.
- Insert TWRP_v2.8.5.0_royss_RC1.tar.md5 to PDA.
- Make sure re-partition is NOT ticked.
- Click the start button, sit back and wait a few minutes.
- Wait until the flashing process is complete.
- If the recovery mode changed to be like these screenshots, then you have successfully installed TWRP.
Bug :
- Can't set brightness
- Lemme know if you find another...
Special thanks to Allah SWT and Nabi Muhammad SAW
Credits :
- CyanogenMod Team
- TeamWin
- Cleverior
- Khristian as tester
- And you
DO WITH YOUR OWN RISK !!!
IF YOU WANNA RESHARE THIS RECOVERY, PLEASE FOLLOW THIS RULES :
- DON'T USE SHORTENER LINK (i.e. adfly, adfoc, etc)
- DONT REUPLOAD MY TWRP BEFORE ASKING PERMISSIONS
[Request]Ubuntu touch topic
I've tested Ubuntu touch for galaxy s2, and it was great
Maybe a skilled dev can try it? Or not x)
Thanks to devs works, Xperia SP keep alive ;)
Sent by Xperia SP using android AOSB 1.3.7 ;D
Maybe a skilled dev can try it? Or not x)
Thanks to devs works, Xperia SP keep alive ;)
Sent by Xperia SP using android AOSB 1.3.7 ;D
mardi 24 février 2015
[Q&A] [RECOVERY][maguro] TWRP 2.8.5.0 touch recovery [2015-02-12] topic
Q&A for [RECOVERY][maguro] TWRP 2.8.5.0 touch recovery [2015-02-12]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][maguro] TWRP 2.8.5.0 touch recovery [2015-02-12]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy! :)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][maguro] TWRP 2.8.5.0 touch recovery [2015-02-12]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy! :)
Flashing CWM Touch need link topic
How to find is HTC m7 at&t, mobile or sprint? And what is the difference?
I think my is Orange...?
And where I can find Clockmod touch recovery for htc one to flash?
On this forum I found thread with this recovery, but link doesnt work. Can anybody can help me?
I think my is Orange...?
And where I can find Clockmod touch recovery for htc one to flash?
On this forum I found thread with this recovery, but link doesnt work. Can anybody can help me?
Touch to Tap screen automatically topic
Is there an app that will automatically tap or touch the screen for you every couple of minutes for android? There is an app that has a continue button that pops up every couple of minutes. If you don't tap it it closes the app and then my tablet goes to sleep. I want to automatically tap it when I am at work so it continues to run.
lundi 23 février 2015
[Q] Flash Clockworkmod Touch Galaxy SIII GT-I9300 topic
Bom dia.
Ao tentar fazer o download automático no modo Flash ClockworkMod Touch ele apresenta o seguinte erro: "Erro ao baixar do servidor. Por favor, certifique-se de ter uma conexão estável e de que seu cartão SD está inserido e tem espaço livre!"
Tenho espaço suficiente nele, mas como devo proceder com isso?
Por favor, alguém pode me ajudar?
Agradeço desde já!
Ao tentar fazer o download automático no modo Flash ClockworkMod Touch ele apresenta o seguinte erro: "Erro ao baixar do servidor. Por favor, certifique-se de ter uma conexão estável e de que seu cartão SD está inserido e tem espaço livre!"
Tenho espaço suficiente nele, mas como devo proceder com isso?
Por favor, alguém pode me ajudar?
Agradeço desde já!
dimanche 22 février 2015
[Q] Camera Touch block Issue topic
Dear All,,
Device : Xperia Z2
ROM : existenZ ultimate 4
Here i requesting your assistance due to an error experienced by my device, Xperia Z2.
lately I use Z2 for under water photo, to be precise at Feb 20, 2015
Cronology:
1. Using phone under water for photo
2. activating touch block feature to prevent screen to be 'touched' by water
3. touch block's 'slide to deactivate' suddenly missing
4. until now I cannot touch my screen.
5. I do re-flash stock ftf file .167, but no changes, even in first use setup I cannot touch language selection.
If anyone have some clue to this issue, please tell me immediately.
Because I'm from Indonesia and Sony Service Center here is somewhat not satisfying.
Thank you.
Best Regards,
Amri
Device : Xperia Z2
ROM : existenZ ultimate 4
Here i requesting your assistance due to an error experienced by my device, Xperia Z2.
lately I use Z2 for under water photo, to be precise at Feb 20, 2015
Cronology:
1. Using phone under water for photo
2. activating touch block feature to prevent screen to be 'touched' by water
3. touch block's 'slide to deactivate' suddenly missing
4. until now I cannot touch my screen.
5. I do re-flash stock ftf file .167, but no changes, even in first use setup I cannot touch language selection.
If anyone have some clue to this issue, please tell me immediately.
Because I'm from Indonesia and Sony Service Center here is somewhat not satisfying.
Thank you.
Best Regards,
Amri
[Q&A] [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12] topic
Q&A for [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy! :)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy! :)
Inscription à :
Articles (Atom)