I would like to start off by giving Kudos to all you Devs, you guys have given this phone the much love and Attention that it has needed:good:
I would like to offer my my knowledge and skill set to help you all in the testing process of your roms. Although SQA ( Software Quality Assurance) is no longer my profession, I did it for 10yrs, most of that in Cellphone technology. So I am probably much older than most of you .
I'd rather keep my issue ( bug) findings between you and I, as not to clutter threads. What logcat app would you recommend and do you guys use a BTS (bug tracking system) else where that files can be uploaded to?
So if you are interested in my help please PM.
This is the development forum. It needs to be in the Q&A forum.
First suggestion - don't start threads in the dev forum. Second - use search and you will find recommendations for logs and where to upload them. Good luck.
Thanks, I asked about logcats and a place to upload the files for the devs to go through, pertaining to each project. as for searching around here, sometimes it's utter chaos.
aLogcat in Playstore and Pastebin with link to log in the respective ROM thread.
Related
I have an interesting problem with ATPlugininstaller.
I installed chome editor v1.6 on my wm6.5 device.
At first it was working fine, and I created 2 plugins using it.
THEN, I decided to add the "day of the week" to the clock panel, by placing code directly in the titanium.cpr files.
Well, the weekday was added successfully, BUT now, I CAN'T use chome editor to create new panels, and I CAN'T install any plugin that uses the ATinstaller.
Whenever I try to do either, I get:
"An unexpected error occurred in ATplugininstaller
ATplugininstaller.exe unauthorized access exception
At System.IO._Error.WinIO error()
At System.IO.FileStream..ctor
At System.IO.FileStream..ctor
At System.Xml.XmlTextWriter..ctor
At System.Xml.XmlDOMTextWriter..ctor
At System.Xml.Xmldocument.save
At ATPlugininstaller.Main.AddLayout to cpr()
At ATPlugininstaller.Main.Main ()
As I said
, I get this same message when I try to create a new panel or add any cabs that require the plugin.
However, the panels I already created and the plugins I already installed still work fine.
My question is, why? My manually adding the code into the cpr files to show "day of the week" on the cclock panel is no different than the entries the installer makes when I install a plugin, or create one using Chome editor.
I know, I've looked thru the cpr file content. So, why does the installer crash AFTER I add the code for "day of the week" to the cpr files?
Can someone please help? Thanks.
Moved, nothing to do with development.
Ok then where do I put it? The ATplugininstaller thread IS in this developmen section, so I beg to differ with you.
I put it out here after getting no response to my inquiry in that thread.
This is one responsive board, out of 10 or so inquiries I've posted, I've only received 2 responses, all from from the author of one sw.
This is a real HELPFUL board,, I've got to say.
And, my inquiry, to remind you, HAS to do with development because I'm creating panels in Titanium using xml.
If the particular sw in question is in this section, then my inquiry as to why it crashes deserves to be here.
I guess it doesn't matter, the members on this board are of no help whatsoever. It's a waste of time to even post.
If I sound frustrated, it's because I am. I have no desire to get flamed, but I need help, and no one even answers.
No need to get frustrated .
Your thread does not belong to the development and hacking forum, that foum is please read the rules of D&H here.
Someone can only help you if they know the solution to your problem, no need to blame the users or the forum itself. Posting in the wrong section will not be helpful to you and will add to our work.
And if you really think posting here is a waste of time, why bother posting ?.
I have moved your thread to Q&A forum, which is regularly visited by developers and people with great knowledge in this field, patience is the key; not blaming the users of the board or being sarcastic.
As far as development goes, you are welcome to post your work ( pannels for titanium ) when they are ready, but not questions.
Hope you calm down, and not repeat such bursts of frustration. You could consider this a warnning.
Please read this carefully:
2.3 Flaming: XDA was founded as a group of people sharing information about certain mobile phones. Sharing does not involve virtual yelling (flaming) it does involve working together to solve problems in an environment of mutual respect and understanding. Losing your temper and flaming another member, or group of members, is not acceptable behavior.
Click to expand...
Click to collapse
I do understand your need for help, but calm down and have patience, try searching or contacting XML writers/developers.
Hope you co-operate.
Understood. I had to do some venting because of all the nonresponses. Can you at least tell me where you moved my post, or did you just delete it? Thank you.
Thank you for your co-operation.
It has been moved to question and answers senction under the general section.
Many people come by here, surely someone will answer; if they have a solution.
madnish30.
just try it with TICS instead of ATPluginInstaller
(link in my signature)
there you don't need a hardcoded .plg and you have the possibility for pre-/postinstall scripts.
Also more definite error message, if you get in trouble.
I tried the contact form and it returned a "Failed to send your message. Please try later or contact administrator by other way." error. So I thought I'd post here. Please delete if inappropriate.
a message for egzthunder1:
First I want to thank you very much for this post: http://www.xda-developers.com/android/hamster-powered-clock-project-for-android-needs-help/
I think it is the reason I got to see my idea come to life. And this is why I'm writing right now. A coding wizard by the username Blou_Aap has taken upon himself to make this happen. We are working at it and so far we've gone through quite a few releases and lots of downloads in the market. Although still in development, we have a stable, working Live Wallpaper we want to share with the world. Free
The development thread is http://forum.xda-developers.com/showthread.php?t=819988 and we've added and improved on this app with the help of the community. This is how we got the name too
We also have a site about timester up and running complete with a donate section.
www.timester.info
Find more info in the OP of the development thread, including download links, recent changes, etc.
All means of spreading the word is appreciated and welcome - I am hoping for a news update on the original posting.
For any more info or images, I'm a reply away.
Thank you!
There are old threads of the same problem more than 2 years ago... So I decided to start a new one.
like this one http://forum.xda-developers.com/showthread.php?t=1426261
I don't want to waste time arguing with some of the opinions in the thread above or about the rule, so back to the case, I agree that people like the OP in the thread above or me are rarely seen. So I'd like to ask here if some moderator could help approve me as a member.
I plan to post in dev forum initiating a project that changes the behavior of Android Media Service. Currently Android Media Service always tries to guess the text-encoding in media files, resulting many messed tags in the library. But in fact there are standards defining what text-encoding of tags should be used in what format.
Please see some details at my previous post:
http://forum.xda-developers.com/showpost.php?p=57188174&postcount=466
So this is the motivation of initiating the project. And I'm an experienced developer with Android framework/kernel development experience. I want people in xda help with the development because I think most users don't take part in AOSP (Android Issue tracker in googlecode, for example) but take part in xda discussion.
Here is the github link of the project:
https://github.com/yumeyao/android_platform_frameworks_av
and the issue:
https://github.com/yumeyao/android_platform_frameworks_av/issues/2
and the issue I reported to AOSP tracker on googlecode:
https://code.google.com/p/android/issues/detail?id=81428
Thanks for reading (so long) and thanks in advance for help
----EDIT----
Never mind I can post now
Good! ?
Thread closed.
Background: Following some threads at XDA I’ve pretty early realised that quite a few bug reports, requests, and questions in regard to ROMs, kernels or applications are raised without sufficient information to allow (Recognised) Developers (RD), Recognised Contributors (RC), or other members to easily provide solid answers and recommendations or a possible fix. Everybody should remember even a highly professional member cannot read your mind.
Initially, I opened a thread with the same topic in regard to the device I use: The Samsung SGS3 LTE (GT-i9305). It’s accessible . If you already know that thread, I hope you don’t mind that I mostly copied and pasted.
Purpose: To provide some recommendations how to best phrase a request for support to possible ROM/kernel/applications issues in order to receive the most suitable answer and solution.
General recommendations:
Please read the XDA Forum Rules provided by @MikeChannon; a MUST READ for everybody who intends to post on XDA. Other MUST READ's I certainly recommend to everybody who wants to "breathe" what I believe the spirit of XDA is, are the following posts:
Forum Etiquette by @TheByteSmasher,
http://forum.xda-developers.com/show...postcount=2441 by @zelendel, and last but not least
http://forum.xda-developers.com/show...9&postcount=44 by @kyphur
Remember: Before you flash anything take a NANDROID backup or ensure you've an up-to-date one!
If you don’t know yet what’s hidden behind some of the expressions mentioned in the title of the following linked thread, just check it out: What is? Boot loader, custom ROMs, CWM, modem, kernel, flashing, rooting, ADB, baseband?? by @esimon311. Thanks to esimon311 for this great overview.
Guidance for useful modifications regarding some parts of your kernel can be obtained here: [GUIDE] Most up to date guide on CPU governors, I/O schedulers and more! by @Saber. Thanks to Saber for this great guide.
Before you post your issue or request, reboot at least once and try to replicate your problem. If it doesn't persist any longer the reboot might already have been the solution.
Read, read, and read again, read the OP (first post of each thread) and scan the respective thread. Use the search function of XDA. Remember: Make use of your friend – your favourite web-search engine. It does mean you have to read and study but I've no doubt you don't mind to do that for your device. Maybe, you'll find your required answer without having to post something.
A lot of OPs already contain hints how to solve commonly known issues.
Before you post in a ROM development thread, be sure not to run a custom kernel or Xposed. In case you use the latter, disable all Xposed modules and check if your issue still persists. Anyhow, if you’re using custom kernel or Xposed and you're convinced the issue is ROM related, you might post but mention the kernel and/or Xposed.
Last but not least: Don't ask what e.g. the best ROM, kernel or app is! All of them available at xda are great; however, each one of them has its different specification, capabilities, and pro's and con's depend on personal desire and expectations. The best one for you is the one, which meets your desire and expectation.
Before you post in a thread:
If you want to sell your car you probably achieve the better bargain the better (or more suitable) the portal is, in which you're offering it. I'm convinced you won't offer a car with the star at the bonnet on a webside covering military motorbikes.
Same applies to XDA. The more precise your post is going to fit into a thread or forum the faster and most likely better reply you're going to receive.
For this reason, I suggest you to exactly identify, in which of the 1000 fora or probably millions of threads to post. Prior to posting take you're time and study the following excellent guides and recommendations - all by @sd_shadow - to find the best and most reasonable place for your post.
[Guide] How and Where to Ask a Question on XDA
"Have Question about Posting?" in this post
[Index] of Help Threads (and Template)
When you post in a thread:
If available, post questions in Q&A threads (some threads have a dedicated Q&A section besides its development one) instead of the development thread. But if you have a solid bug report (never reported before, and your post is complying to all the required criteria provided below including all necessary info), you can post in a development thread.
Don't make a RD, RC or anybody else to read your mind. Don't have them to make assumptions – as soon as an assumption fails the whole solution is going to become void.
Please post your issue or request by using the English language as mentioned in the XDA rules to allow everybody to understand the post and hopefully to contribute, or at least to learn out of it. Don't be afraid if English isn't your native tongue – that's certainly the case for most of the xda users. A language barrier isn't an issue at XDA – as long as we all at least try to use the English language. Even if your English skills aren't too developed just use simple wording or a reasonable translator tool; nobody is going to blame you; however, try to be as precise and unambiguous as possible.
Always run a logging tool to be able to augment your post by a log file. Add the log as an attachment to your post or upload it into the cloud and provide the link in your post. Do not include the log into the text phrase of your post in order not to spam the thread. It doesn't matter, which logging tool you use but familiarise yourself with its use and where it saves the log. I'm personally e.g. using "Catlog" that saves logs to the internal storage. Alternatively use adb commands. Here is a [Tutorial] How To Logcat by @paxChristos. Thanks to paxChristos for this great tutorial.
If you're running (Ed)Xposed uninstall it, and take the log again (while Xposed is running, the log even states that it's useless because of Xposed).
Take screenshot(s) and attach them/it to your post. Don’t insert it/them into the “text box”. Before you take a screenshot, change your system language to English to allow everybody to understand the content of the screen.
Always provide exact and precise information about your issue. Write a description and, if possible, steps to allow for reproduction.
Unless the issue is only related to an application always provide exact and precise information about your device, the ROM, the kernel, your recovery, and specify the versions of the latter three. If you have issues with a theme, information regarding your ROM is certainly required. Occasionally information about your modem (or even bootloader) might also be helpful e.g. if you've problems with the RIL, mobile network or making phone calls. If you're on F2FS please mention.
If your issue or problem occurred immediately after you flashed a ROM* or kernel* or installed an application (incl. themes), please describe your installation procedure (clean, dirty, or describe when you wiped and/or formatted what).
*Please provide information, from which ROM or kernel you came.
Credits and many thanks to @woodman and @alias_ z3d in helping me to set up this OP.
First!!!
Perfect! After the i930x world, now the general version of your nice thread. I'm sure it will be a great addition to the XDA community. I hope a lot of members will read and remember your advices.
Background: Following some threads at XDA I’ve pretty early realised that quite a few bug reports, requests, and questions in regard to ROMs, kernels or applications are raised without sufficient information to allow (Recognised) Developers (RD), Recognised Contributors (RC), or other members to easily provide solid answers and recommendations or a possible fix. Everybody should remember even a highly professional member cannot read your mind.
Initially, I opened a thread with the same topic in regard to the device I use: The Samsung SGS3 LTE (GT-i9305). It’s accessible . If you already know that thread, I hope you don’t mind that I mostly copied and pasted.
Purpose: To provide some recommendations how to best phrase a request for support to possible ROM/kernel/applications issues in order to receive the most suitable answer and solution.
General recommendations:
Please read the XDA Forum Rules provided by @MikeChannon; a MUST READ for everybody who intends to post on XDA. Other MUST READ's I certainly recommend to everybody who wants to "breathe" what I believe the spirit of XDA is, are the following posts:
Forum Etiquette by @TheByteSmasher,
http://forum.xda-developers.com/show...postcount=2441 by @zelendel, and last but not least
http://forum.xda-developers.com/show...9&postcount=44 by @kyphur
Remember: Before you flash anything take a NANDROID backup or ensure you've an up-to-date one!
If you don’t know yet what’s hidden behind some of the expressions mentioned in the title of the following linked thread, just check it out: What is? Boot loader, custom ROMs, CWM, modem, kernel, flashing, rooting, ADB, baseband?? by @esimon311. Thanks to esimon311 for this great overview.
Guidance for useful modifications regarding some parts of your kernel can be obtained here: [GUIDE] Most up to date guide on CPU governors, I/O schedulers and more! by @Saber. Thanks to Saber for this great guide.
Before you post your issue or request, reboot at least once and try to replicate your problem. If it doesn't persist any longer the reboot might already have been the solution.
Read, read, and read again, read the OP (first post of each thread) and scan the respective thread. Use the search function of XDA. Remember: Make use of your friend – your favourite web-search engine. It does mean you have to read and study but I've no doubt you don't mind to do that for your device. Maybe, you'll find your required answer without having to post something.
A lot of OPs already contain hints how to solve commonly known issues.
Before you post in a ROM development thread, be sure not to run a custom kernel or Xposed. In case you use the latter, disable all Xposed modules and check if your issue still persists. Anyhow, if you’re using custom kernel or Xposed and you're convinced the issue is ROM related, you might post but mention the kernel and/or Xposed.
Last but not least: Don't ask what e.g. the best ROM, kernel or app is! All of them available at xda are great; however, each one of them has its different specification, capabilities, and pro's and con's depend on personal desire and expectations. The best one for you is the one, which meets your desire and expectation.
Before you post in a thread:
If you want to sell your car you probably achieve the better bargain the better (or more suitable) the portal is, in which you're offering it. I'm convinced you won't offer a car with the star at the bonnet on a webside covering military motorbikes.
Same applies to XDA. The more precise your post is going to fit into a thread or forum the faster and most likely better reply you're going to receive.
For this reason, I suggest you to exactly identify, in which of the 1000 fora or probably millions of threads to post. Prior to posting take you're time and study the following excellent guides and recommendations - all by @sd_shadow - to find the best and most reasonable place for your post.
[Guide] How and Where to Ask a Question on XDA
"Have Question about Posting?" in this post
[Index] of Help Threads (and Template)
When you post in a thread:
If available, post questions in Q&A threads (some threads have a dedicated Q&A section besides its development one) instead of the development thread. But if you have a solid bug report (never reported before, and your post is complying to all the required criteria provided below including all necessary info), you can post in a development thread.
Don't make a RD, RC or anybody else to read your mind. Don't have them to make assumptions – as soon as an assumption fails the whole solution is going to become void.
Please post your issue or request by using the English language as mentioned in the XDA rules to allow everybody to understand the post and hopefully to contribute, or at least to learn out of it. Don't be afraid if English isn't your native tongue – that's certainly the case for most of the xda users. A language barrier isn't an issue at XDA – as long as we all at least try to use the English language. Even if your English skills aren't too developed just use simple wording or a reasonable translator tool; nobody is going to blame you; however, try to be as precise and unambiguous as possible.
Always run a logging tool to be able to augment your post by a log file. Add the log as an attachment to your post or upload it into the cloud and provide the link in your post. Do not include the log into the text phrase of your post in order not to spam the thread. It doesn't matter, which logging tool you use but familiarise yourself with its use and where it saves the log. I'm personally e.g. using "Catlog" that saves logs to the internal storage. Alternatively use adb commands. Here is a [Tutorial] How To Logcat by @paxChristos. Thanks to paxChristos for this great tutorial.
If you're running (Ed)Xposed uninstall it, and take the log again (while Xposed is running, the log even states that it's useless because of Xposed).
Take screenshot(s) and attach them/it to your post. Don’t insert it/them into the “text box”. Before you take a screenshot, change your system language to English to allow everybody to understand the content of the screen.
Always provide exact and precise information about your issue. Write a description and, if possible, steps to allow for reproduction.
Unless the issue is only related to an application always provide exact and precise information about your device, the ROM, the kernel, your recovery, and specify the versions of the latter three. If you have issues with a theme, information regarding your ROM is certainly required. Occasionally information about your modem (or even bootloader) might also be helpful e.g. if you've problems with the RIL, mobile network or making phone calls. If you're on F2FS please mention.
If your issue or problem occurred immediately after you flashed a ROM* or kernel* or installed an application (incl. themes), please describe your installation procedure (clean, dirty, or describe when you wiped and/or formatted what).
*Please provide information, from which ROM or kernel you came.
Credits and many thanks to @woodman and @alias_ z3d in helping me to set up this OP.
First!!!
Perfect noc.jfcbs! After the i930x world, now the general version of your nice thread. I'm sure it will be a great addition to the XDA community. I hope a lot of members will read and remember your advices.