Hi
I know this is more of development question than "Q&A, Help & Troubleshooting" one, but since I didn't need to post anything on XDA yet I cannot ask this question in development section. So here's my question:
Is it possible to turn off ITUCH messages showing in dmesg log? It logs every time I touch or "untouch" the screen and in very short time dmesg becomes pile of useless garbage.
Code:
<4>[81444.265543] ITUCH : <0>(down)[959(2):625(4)]-1
<4>[81446.546546] ITUCH : <0>(up)[959(2):603(5)]-12
The same problem is with physical keys being pressed (GKEY logs), but those are less annoying.
Related
I'm looking for those two specifications from a Dialer:
Search into Facebook contact
Search number in the middle
By search number in the middle, I mean if I start dialing 555 it would show me number 0785556767 by example.
Dialer one has those two specifications but only with HTC Sense ROM, with non Sense ROM, it doesn't look into the Facebook contact
So I'm looking for:
a way to make Dialer One working with non Sense ROM for Facebook search into contact
another Dialer that would look for Facebook contact and search number in the middle with a non Sense ROM
a non Sense ROM that would allow any of the two above
Thanks,
Nickwe.
You may try with aTAKEphONE. The last version is 1.25
"- Search company (!) and notes (!) fields.
- Search (filter) call log list by text.
- Jump to a specific date in the call log.
- Schedule calls as entries in your Calendar.
- Search for contact in a super fast & sophisticated way -
using a T9-like mechanism (e.g. to search for "John" simply
tap the "JKL", "MNO", "GHI", "MNO" buttons)"
Thread Reported.
DON'T POST YOUR QUESTIONS IN THE DEVELOPMENT SECTION!
Do you not think the mod of this forum (Who also is a mod for 5 other devices) has better things to do than constantly moving all your '[Q]' threads?
Thank you,
NoobNazi
(Please don't create a new thread in General/Q&A, this *should* get moved soon)
Moved to correct forum. Why was this posted in Development?
WB
wacky.banana said:
Moved to correct forum. Why was this posted in Development?
WB
Click to expand...
Click to collapse
Good question. Most general queries end up in development these days :/
Is it not also bad forum etiquette to clog up threads with unrelated posts?
And yes, I'm aware of the irony.
I was playing with my friends Nokia, and his hardware keyboard allowed him to turn on his flashlight (camera led) by holding down his spacebar.
So I was thinking, is there anyway to map the optical trackpad press on our dincs to do this?
Ideally when the screen is on/unlocked you would hold it down a few secs to turn it on, then hold down a few secs again to turn it off. Also if the screen was off/locked, then hold it down to turn it on but have it turn off the second you stop holding it (for accidental pocket presses).
http://forum.xda-developers.com/showthread.php?t=813282
http://forum.xda-developers.com/showthread.php?t=818075
judging by those two threads this doesn't seem very possible. is that what you were getting at? because you probably could have just said "remapping doesn't work"
rmoney said:
you probably could have just said "remapping doesn't work"
Click to expand...
Click to collapse
Personally, I appreciate it when people provide me links to more information than a single line summary like, "remapping doesn't work."
But I'm sorry that I inconvenienced you with having to read other discussions.
You're welcome for providing you the information that you were too lazy to search out on your own.
rmoney said:
judging by those two threads this doesn't seem very possible. is that what you were getting at?
Click to expand...
Click to collapse
Actually, what I was primarily getting at was the fact that at least two recent discussions cover this topic, and that information was there for the taking if you would take a few seconds to search / read.
There's a reason that the forum software tries to find similar threads every time you create a new thread. There's also a reason why the forum asks you if your thread is a question when you create it.
Finally, this doesn't belong in Development, since you didn't develop anything.
Since you like things summed up, here you go:
"Your issue has been discussed multiple times recently, it is a question, it doesn't belong in this subforum, and you may or may not have this thread locked or receive a temporary ban because of the aforementioned rules for this subforum."
Hope I didn't waste too much of your time this time.
BNG303 said:
Personally, I appreciate it when people provide me links to more information than a single line summary like, "remapping doesn't work."
But I'm sorry that I inconvenienced you with having to read other discussions.
You're welcome for providing you the information that you were too lazy to search out on your own.
Actually, what I was primarily getting at was the fact that at least two recent discussions cover this topic, and that information was there for the taking if you would take a few seconds to search / read.
There's a reason that the forum software tries to find similar threads every time you create a new thread. There's also a reason why the forum asks you if your thread is a question when you create it.
Finally, this doesn't belong in Development, since you didn't develop anything.
Since you like things summed up, here you go:
"Your issue has been discussed multiple times recently, it is a question, it doesn't belong in this subforum, and you may or may not have this thread locked or receive a temporary ban because of the aforementioned rules for this subforum."
Hope I didn't waste too much of your time this time.
Click to expand...
Click to collapse
Wow....you could have just saved the time and not responded at all.
jackattack said:
Wow....you could have just saved the time and not responded at all.
Click to expand...
Click to collapse
Indeed. I just didn't appreciate rmoney's dismissive response to what I thought was a helpful reply: providing him with relevant links.
Hi!
I've been searching all over the internet for a solution, but I can't seem to find one.
I'm trying to change the way you answer calls (especially when in standby)
I've changed the lockscreen by renaming HTCLockscreen.
But the way you answer calls is still by swiping up/down..
Is it possible to change it to left/right at all?
Thank you!
Please do not post question threads in Development.
Post What Where:
General - general technical discussion items, news, anything else that does not fit into the other fora categories.
Q&A (Questions and Answers) - all questions, irrespective of type, get posted in here whether they be theme related, accessory related, technical, etc.
Accessories - any items to do with components and/or accessories relating to your device.
Rom Development - only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here.
Themes & Apps - anything to do directly with the development of themes and/or applications. Nothing else goes in here.
Woops, my bad!
I wonder the same. Is there something like lockbot for calls
Hi guys,
Since users who haven't posted 10 messages yet can't reply in a development thread and I couldn't find a decent topic in which my statements would've been answered, I would like to propose this topic to be used where people could sum up their wishes for the RCMix3D rom.
---
#1 - Scaling glitch
In version 0.1, there was a scaling glitch. If you pinched the desktop screen, the seven homescreens would zoom out, but when you zoomed back in the homescreen had a glitch: the screen would stretch from the top-left corner. This issue got fixed in version 0.2. In version 1.0, 1.1 and 1.2, this glitch has made its return, I would love to see it fixed, permanently this time please.
#2 - Lock screen font
When you unlock your phone, the font on the Weather unlock screen is stretched. It's blurry, and it doesn't have any margin on its left side... So if the devs could resize/move this, it would be appreciated.
#3 - Widgets
First of all, the calendar widget still hasn't been fixed since version 0.1. Yes, I have read the thread of the ROM over at the Development page multiple times and forgive me if I haven't seen your fix, but it's a mess. If I look at the overall result, it doesn't seem like a widget issue, but more of a resolution issue, I know the device from which this ROM was ported had a much larger resolution and probably causes this, but it would be nice if this could be fixed too?
---
To finish this first post, I would like to bring out a big thank you to the developers who made it possible to get this ROM up and running on the Desire HD, keep up the good work guys!
Congrats on your first post
Quite a good list of observations there. I would suggest you try the below and see ..... so far its seems quite good for a first release
Virtuous Unity 1.0.0
http://forum.xda-developers.com/showthread.php?t=1115312
tobmav said:
Hi guys,
Since users who haven't posted 10 messages yet can't reply in a development thread and I couldn't find a decent topic in which my statements would've been answered, I would like to propose this topic to be used where people could sum up their wishes for the RCMix3D rom.
Click to expand...
Click to collapse
You couldn't find a decent topic, did you even try to search? It's even mentioned in the OP of RCMix3D thread. Don't spam this forum...
capychimp said:
Please search read check buglist and discussion thread, development related questions here, all other in discussion thread
Problems:
If you have problems and questions, that is not realy related into coding and frixng the rom go HERE and post, this is a thread for it all about RCMIX made by Hawks556
Click to expand...
Click to collapse
Here's the link: http://forum.xda-developers.com/showthread.php?t=1071455
It's an active thread too so can't understand how you missed it
As stated by Hawks556, there already is a thread.
This one is closed.
Ok, basically this thread is meant to inform the DOs and DON'Ts on XDA, and also how to do certain things. I started this thread as I have noticed that there has recently been an influx of posts that fail to serve their intended purpose well (e.g. asking for help, bug reporting etc.) Also I hope that this thread will serve to at least provide a general guideline.
Rules
1. No stealing of ROMs.
Ok, this is quite obvious but I thought it would do well to just explain what this is so that some of you don't accidentally steal someone else's ROM. What this means is:
You are not allowed to publish a ROM that you didn't create yourself. What this means is simple -- you are not allowed to publish on the web any ROM that you:
a. have not compiled from sources yourself AND that you haven't added in your own code to
b. have ported from another device WITHOUT permission from the original ROM developer
c. have cobbled together from already-published work (take parts from different ROMs and combine them for a hybrid ROM without adding in your own original code)
The following kind(s) of ROM(s) are exempt from this rule:
a. Stock ROMs with/without modifications
++++++++++++++++++++++++++++++++++++
If you contravene the above rule, it will mean that you have stolen a ROM. If you wish to publish a ROM that breaks the above rule, you have to OBTAIN THE PERMISSION of the developers of the parts (be it scripts, ROMs, mods etc.) that you used in your ROM. Furthermore, in your ROM thread, you must give proper credits to the devs whose work you used and also link back to the original ROM.
If your ROM is simply someone's ROM with cosmetic changes (e.g. different theme and/or a few scripts added in), you must do the above and also post it in the Themes and Apps section as an update.zip that only changes the parts of the ROM as needed.
Lesson is simple: If you want fame on XDA, learn how to compile your own ROM sources and don't simply soft-mod -- usually many people inadvertently steal someone else's ROM this way.
##############################################################
Guidelines:
1. Don't post any non-development related stuff (bug-reports ARE development-related so feel free to post them though) -- it only serves to spam up the thread and hinder development. Posts like "This ROM is great", "this ROM is fast and the best I've used" and "Thanks for this awesome ROM" or, god-forbid, "This ROM sucks" etc are hardly informative, development-supportive, and have no purpose. You might feel good after posting this, but honestly it just serves to annoy others that are trying to locate something in the thread. So don't post this, PLEASE .
2. No ETAs. Please, do not post stuff like "When will the next release come along... can't wait!", "When will you fix XXX bug" and similar questions AT ALL. The ROM will be released when ready, and as above this only spams up the thread. If you are that impatient, I suggest you flash back to stock 2.1, no disappointments and is definitely the most stable .
3. Provide as much detail about your bug as possible. This is by far one of the most common problems. Posts like "my WiFi isn't working", "there's xxx when I yyy, please fix!" are really useless. There !re 1001 possible reasons why your WiFi isn't working, and why blahblahblah happens. To be actually helpful and have a greater chance of having your problem rectified, provide the following:
ROM you are on
Kernel you are using
Paraphernalia you have installed (e.g. Scripts like Supercharger, swap, OC frequency etc)
(If possible) How to replicate your issue
What steps you took to rectify the problem (if any)
Your logcat and dmesg
ON TERMINAL EMULATOR
How to get logcat output saved as a file called logcat.txt on your sdcard:
Code:
su
cat /dev/log/system > /sdcard/logcat.txt
And for dmesg to be saved as a file named dmesg.txt on your sdcard
Code:
su
cat /proc/kmsg > /sdcard/dmesg.txt
or for last dmesg after odd shutdown
Code:
su
cat /proc/last_kmsg > /sdcard/lastdmesg.txt
Flaming and trolling:
1. Refrainkfrom using personal insults as much as possible like "you are dumb", "how stupid can you get", "you are a noob" etc. This is the precursor to an unnecessary flame war. Try and be polite instead like, " you are new, so you may not know this, but blahblahblah". You were a noob once, so try and treat noobs as you would have wanted others to treat you when you were a noob.
2. Don't continue flaming. If someone posted something that flames something, don't flame back. Just report the post and sit back and relax. Continuing the post will just feed the troll and make things worse. You might get punished too.
3. Mind your language. Use English on XDA always, if you can't, include an English translated version of your original text and post it along with your original text. Also, never ever use vulgarities on XDA -- it's a surefire way to get infracted. Don't post any racist/political posts either. XDA is for mobile phone discussion and development, not for expressing your extremist/whatever views about...
_______________________________________________________________
Q&A
1. Use the search tool first. You are just one of over 4 million members on XDA, and it is very likely that your question has been asked and answered already. Search before posting any question to avoid spamming the forums. Remember, you are likely to get an answer faster this way, and this also prevents you from being flamed if your question has been asked before
2. Don't be demanding. People do not have an obligation to do things for you, hence don't demand quick answers, insta-fixes, or a detailed step-by-step guide. It just shows how much you actually bothered to search for answers first and also people will be less likely to answer to you.
3. Post questions in the Q&A forums. Just because the DEV and General forums get more traffic doesn't mean that you should post them there. Again, your question will most likely be answered faster in the Q&A forums and you won't get flamed either.
4. Don't revive old threads and answer them. Recently I have seen users who answer threads 2 days+ old that have been resolved already. Their answer is usually a paraphrase of one of the answer posts above. Then they put in a "Please hit Thanks if I helped". Thanks for answering, but no thanks for spamming and trying to get thanks for free.
++++++++++++++++++++++++++++++++++++++++++
Miscellaneous
1. Hit the Thanks button whenever you feel like posting Thanks instead. This reduces the amount of spam on the forums and is a good way of showing your appreciation for the person that helped you. Generally XDAers have a thanks limit of 8 per day, so use them wisely! (Unlimited on Tapatalk/XDA app apparently). At the same time, don't be a Thanks hunter -- someone who actively posts only for Thanks. Please, it is not some sort of "prestige meter", and anyway people can clearly see that you are a thanks hunter and will treat you as such.
2. Use the Report feature. If you see a post that breaks the XDA rules, report the post. Many people that I see just flame the rulebreaker on the thread instead of reporting and allowing a moderator to deal with things. Remember, moderators are not Gods that know whenever some person breaks a rule, so Report posts to help them along.
3. Think, search, then discuss, not the other way round. Only then will a constructive discussion start. Unfortunately, many people just post without thinking, resulting in flaming and general unpleasantness on the forums. XDA is a place where individuals from around the world gather to discuss and develop on mobile phones, so let's keep it that way :highfive::victory:.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
==========================================================
Credits goes to SpyderX for the post. Original link is here.
Nice copy-paste.
You can at least give credits.
Original thread here by SpyderX.
stamatis said:
Nice copy-paste.
You can at least give credits.
Original thread here by SpyderX.
Click to expand...
Click to collapse
Done.