Related
hi guys
-i am a new user for the EXEC. everything strange to me.so i wanna use this topic to collect all the thing for EXEC, such as, Softwere, Hardwere, Update, and so on.....just give the deatils for the everything you have been given. include.
-- Name
-- What is for?
-- How to use it?
-- Show the PIC
this topic only for people that it is easy to find, to communications, and to discussion.
brightming said:
hi guys
-i am a new user for the EXEC. everything strange to me.so i wanna use this topic to collect all the thing for EXEC, such as, Softwere, Hardwere, Update, and so on.....just give the deatils for the everything you have been given. include.
-- Name
-- What is for?
-- How to use it?
-- Show the PIC
this topic only for people that it is easy to find, to communications, and to discussion.
Click to expand...
Click to collapse
ur asking an awful lot from people. i can see however that you havent got the latest o2 update. go to http://www.my-xda.com/xdaexec_soft.html to update!
there is so much of this information on this forum that it isnt funny asking for it again.
I can see that you have only ever made 2 posts, so it would seem that your first forum is out of naivety rather than stupidity.
As such, here are some hints and a starting point for you. Please be aware, that there is quite a good search function if you take the time to look and can use the multiple fields to narrow down your search function.
You can also try the wiki ftp site if you just want some software and utilities to use. In the end though, you will find the best outcome and most stable device if you go and buy it.
Try www.spbsoftwarehouse.com www.resco.net www.handango.com www.ppcfreewares.com
Months and months ago I started this, and others have very comprhensive forum topics already.
Please dont restart what has already been done, lots.
Try this from September
http://forum.xda-developers.com/viewtopic.php?t=28343&highlight=apps
This in November
http://forum.xda-developers.com/viewtopic.php?t=32698&highlight=apps
This done by craigiecragie
http://forum.xda-developers.com/viewtopic.php?t=31697
Try this for an antagonist view
http://forum.xda-developers.com/viewtopic.php?t=30206&highlight=compatible+wm5
This should be detailed enough for you
http://forum.xda-developers.com/viewtopic.php?t=30443&highlight=compatible+wm5
Agreed, this has been posted a great many times, each trying to be the definitive post on all aspects of the Universal - something which I think is frankly impossible as no single post can cater for everything.
In the defence of somewhat overwhelmed newcomers, however, I do think it's time for x-d to be reorganised (how many times have we said this??) and broken down more specifically than just General, Upgrading and Accessories. There should also be beginners guides, for just this kind of thing.
@ brightming: the links provided above are a good starting point, read them all thoroughly!
Cheers
Ant
I've been (mostly) lurking here for a few months and I'd agree - it'd be fantastic to have 1) more specific/detailed forums under the Universal heading and 2) some well-written, clear guides for newcomers - particularly given the repetition and duplication of many subjects in different posts. An alternative place to have some good how-to type guides might be the wiki, especially considering that it appears to be underused at the moment. Any mods fancy tackling this?...
Mach
(edit: stupid spelling mistakes)
da1 said:
brightming said:
hi guys
-i am a new user for the EXEC. everything strange to me.so i wanna use this topic to collect all the thing for EXEC, such as, Softwere, Hardwere, Update, and so on.....just give the deatils for the everything you have been given. include.
-- Name
-- What is for?
-- How to use it?
-- Show the PIC
this topic only for people that it is easy to find, to communications, and to discussion.
Click to expand...
Click to collapse
ur asking an awful lot from people. i can see however that you havent got the latest o2 update. go to http://www.my-xda.com/xdaexec_soft.html to update!
Click to expand...
Click to collapse
thx for told. i have areadly done.
simon_darley said:
there is so much of this information on this forum that it isnt funny asking for it again.
I can see that you have only ever made 2 posts, so it would seem that your first forum is out of naivety rather than stupidity.
As such, here are some hints and a starting point for you. Please be aware, that there is quite a good search function if you take the time to look and can use the multiple fields to narrow down your search function.
You can also try the wiki ftp site if you just want some software and utilities to use. In the end though, you will find the best outcome and most stable device if you go and buy it.
Try www.spbsoftwarehouse.com www.resco.net www.handango.com www.ppcfreewares.com
Months and months ago I started this, and others have very comprhensive forum topics already.
Please dont restart what has already been done, lots.
Try this from September
http://forum.xda-developers.com/viewtopic.php?t=28343&highlight=apps
This in November
http://forum.xda-developers.com/viewtopic.php?t=32698&highlight=apps
This done by craigiecragie
http://forum.xda-developers.com/viewtopic.php?t=31697
Try this for an antagonist view
http://forum.xda-developers.com/viewtopic.php?t=30206&highlight=compatible+wm5
This should be detailed enough for you
http://forum.xda-developers.com/viewtopic.php?t=30443&highlight=compatible+wm5
Click to expand...
Click to collapse
thx very much. it is so much help for me.
Moderators, why the sticky thread disappear? The problem isn't solved, I know people having 64x with the problem .... also take a look here http://www.solopalmari.com/smf/index.php/topic,11129.msg49739.html#msg49739 is in italian but icons speaks and disallineamento means misalignment and 642 is 642 in any language ...
The sticky was useful to have a pulse of the problem, I know, may be isn't loved from HTC but what they love or not isn't our problem I believe!
sergiopi said:
Moderators, why the sticky thread disappear? The problem isn't solved, I know people having 64x with the problem .... also take a look here http://www.solopalmari.com/smf/index.php/topic,11129.msg49739.html#msg49739 is in italian but icons speaks and disallineamento means misalignment and 642 is 642 in any language ...
The sticky was useful to have a pulse of the problem, I know, may be isn't loved from HTC but what they love or not isn't our problem I believe!
Click to expand...
Click to collapse
Obviously I do not speak for the Moderators, but I think as a stick thread it had really served its purpose. We gained a good knowledge of how extensive the problem is and that you either have it or not and you either try the physical solutions or send it back.
Of course if there is anything new to add the thread is still available
http://forum.xda-developers.com/showthread.php?t=277861&highlight=alignment
and by adding to it, it goes top of the list. I suppose, for many of us it's just a boring topic now and the solutions (good or bad) are well known.
Personally I would not object if it returned to being sticky but will it really benefit us?
I guess others will post their views.
Mike
It has been sticky for two months (23 sept to 23 nov). If you or someone adds a comment to it it will be bumped to the top again, but I believe the problem has been discussed widely enough and doesn't need to be sticky anymore.
There is also a wiki page about the SA issue:
http://wiki.xda-developers.com/index.php?pagename=How to fix the Screen Aligment issue
I know, it has been up for long time but SA is STILL unresolved!
I discover isn't sticky anymore because I would like to add the 640xxx problems!
The wiki state no Hermes Screen Alignment (SA) problems since 638... Also all new users (and many old) avoid scrolling down for more than 1-2 pages and the Device forum IMO is something useful for both, new and old user.
The SA thread is useful for new users, to find solutions, to avoid "risky" conditions, some pants and some pockets (HERMES isn't a truly POCKET device, it stops working if you keep it inside a pocket )to the company to develop a FIX and not a PATCH like they have done until now.
The old userse can add knowledge, having all knowledge together in the same thread
Thanks to SA we learned about Hermes Hardware, HTC service, HTC national service problems and SA thread is the most viewed hermes thread.
IMO un-stick it when the problem is solved, a couple of months, not only a week later.
I'll be monitoring it and re-stick it if I see there's activity.
pof said:
I'll be monitoring it and re-stick it if I see there's activity.
Click to expand...
Click to collapse
Great! I will call you Solomon...
http://www.commem.com/prod06b.htm
So sticky is for threads with strong activity... LOL
LOL
Didn't meant that... but the SA issue has been widely discussed, and there's nothing new to be added.
- New Hermes owners buy new devices that don't have the issue. They don't care about S.A.
- Old Hermes owners have already read all the possible solutions about S.A. and probably taken action if they had S.A. on their device. They have solved the issue in one or other way (replacement, fix, etc...) So they don't care anymore about S.A.
- If someone has S.A. now, the thread is still here, the info is on the wiki and he can ask about it, but the thread doesn't need to be sticky for this.
- We all know HTC support is crap, otherwise we'll not be here trying to fix our issues, we don't need an sticky thread just for that
This is my point of view. Two months sticky was enough. If you feel the thread must be sticky again is just a matter of 2 clicks, i don't really care about it....
Anyone else wants the thread to be sticky? Any reason for it?
uh oh, even the new ones are having issues?! Doh! I'm awaiting a brand new one (twill be my 3rd TyTn)!
If this one plays up again, i'm getting a different handset! Its good, but i cant cope with hardly seeing it, as its in repairs all the time!
Mods,
Are the Relentless Appz posts being deleted because they contravene rules #7 and #11 about selling?
If so, fine, but if not - are they otherwise dodgy and to be avoided or is it just a forum rule thing?
TIA
NB - Don't mean to stir up a fire. Feel free to delete this thread and just PM me the answer if you prefer.
I too would like to know. Anyone have any first hand experience? I'd considered giving their rom roaster a try. Thought it was a bit shady for them to make their member name "admin-xda." That made me take a step back. Anyone with any first hand experience with these guys?
Well, this is going to get bumped until I get an answer (or it's deleted...).
Anyway, I've purchased the software and am getting active and responsive support from the developer. Having said this we're working through some installation challenges (might be my system, we don't know).
I've taken one for the team and now have considerable experience in packaging and bundling roms so will apply this software to my Kang-o-rama build to see how it suits.
I will write a review of the software when I have used it sufficiently and post that here on XDA.
In the meantime, I recommend you wait although so far I feel this guy (the dev) is honest and just trying to do a good job. We will see.
Well, this is going to get bumped until I get an answer (or it's deleted...).
Anyway, I've purchased the software and am getting active and responsive support from the developer. Having said this we're working through some installation challenges (might be my system, we don't know).
I've taken one for the team and now have considerable experience in packaging and bundling roms so will apply this software to my Kang-o-rama build to see how it suits.
I will write a review of the software when I have used it sufficiently and post that here on XDA.
In the meantime, I recommend you wait although so far I feel this guy (the dev) is honest and just trying to do a good job. We will see.
Click to expand...
Click to collapse
Just curious - what is it that you want to do with your ROM when cooking it yourself?
dsixda said:
Just curious - what is it that you want to do with your ROM when cooking it yourself?
Click to expand...
Click to collapse
Well, to be honest I'm sceptical it will help me. But, it may and I'm willing to check it out on behalf of other XDA users and report back. The 5 quid isn't much to me but may be for others.
Also, because I've been building Kang-o-rama I think I'm in a good position to objectivity review the software.
On first appearances and based on the specs I think this has the potential to be quite a useful resource for junior rom builders... but that remains to be seen. If it works then really, it will be quite a nice solution for many because it's apparently a little more flexible than the various online kitchens.
Additionally, my communication so far with the dev has been positive and it really does appear as if he's got a personal interest in helping out the community. Of course I can't vouch for this fully yet.
Finally, if it actually allows me to save my build as versioned projects and simply execute the build from a single interface it may actually save me some time.
Having said all this, I've now practically automated my entire build so I suspect most of the value of my purchase might just be the potential review on XDA... we will see.
djmcnz said:
Mods,
Are the Relentless Appz posts being deleted because they contravene rules #7 and #11 about selling?
If so, fine, but if not - are they otherwise dodgy and to be avoided or is it just a forum rule thing?
TIA
NB - Don't mean to stir up a fire. Feel free to delete this thread and just PM me the answer if you prefer.
Click to expand...
Click to collapse
As I'm certain you know, there are many facets to a situation; and contrary to any announcements or statements you may have seen, this was not a targeted attack by a specific moderator. The owner of Relentless Appz clearly understands why the account suspension was placed for a third time.
I'm not going to get into providing the details about the action taken. I will say however, that several weeks of ongoing deliberation and discussions amongst Moderators/XDA Admins led to this action. As a sufficient number of forum rules were violated, and in the best interest of the members of this community, it was unanimously decided that this was the most appropriate course of action.
Please visit the Relentless Appz support forum on his website for assistance with trialware/purchased versions of his applications.
Regards,
Ref: Forum Rules
I really don't want this to come across wrong, but I just have to say it.
Developers, I appreciate all your hard work. I understand this is all beta/test/etc. I understand it is free of cost, even to those who did donate to one dev or another. You do it because you want to, not because you have to.
But please, for the love of all that's good - keep an updated list of Known Issues!
It sucks having to read 50 pages of posts to try to figure out if a particular release is reliable or not, to find out if there's a key feature broken or buggy. What makes it worse is you can't tell when reading these threads which users are on which release, because many still post issues after they've been resolved. Others post things that aren't really "issues" but user error.
You know what your issues are, you read the threads and you fix the issues. But trying to find a decent rom to flash is very, very difficult when your OP says "No known problems" and the thread that follows show that to be very untrue. It generates a lot of extra posts with people posting things you already know about, and it generates a lot of bad will when someone flashes something only to find that there are a number of game breaking issues.
All it takes is to update a post, say #2, in your thread, with KNOWN ISSUES. Once you confirm a bug, whether you intend to fix it on your next release or not, add it to that thread. It helps you, as a dev keep track of the bug, and it helps potential downloaders know what bugs have been confirmed and make an educated decision as to whether they want to install your release.
Hiding known issues is something I don't think anyone does intentionally, but it feels that way sometimes. It feels like devs are in a popularity contest, and any admission of flaws in their particular ROM is a weakness. Well, to tell the truth, I and many others are sick of installing something that was CLAIMED to be working perfectly, only to have glaring problems that have been there for many versions.
For a civil and productive development community. Please. Be honest with your known issues. It will go a long way in building trust with the people who you're providing ROMs to, and will mean fewer posts for YOU to wade through of users reporting known issues, without having read 500 posts first.
I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate
They don't care to list them. It's beneath some of them.
Maybe AirBus should list "midair exploding engines" as a known issue too...
kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
Click to expand...
Click to collapse
+1. Hell, at work I run a $100,000.00+ software suite and even that company won't do what the OP suggests!
If you have a problem with them stop using their roms go back to stock and see how much better theirs is even with a few bugs, not one of you has any right to complain. They do damn good work for free with some donations that do not come close to what they should be paid for it but they do not whine at all.
The problem I find is the "spammy" and useless comments average and pretentious users make which is both hard for the developer and the end user to read the threads. A dev releases a ROM and there is a guaranteed "Oh I can't wait to flash this" comment that will pop up. And there are some issues that are minor and are sometimes not related to the release that are posted and some pretentious loser who extends his ego by trying to make simple matters complicated. This forum didn't much of this problem before and I could quickly flash ROMs easily since I could clearly grasp the status on the ROM project.
I wish they would start a new thread with new releases. It's a pain to try to read through a 500 page thread, and you comments about this or that, and you have no idea which version the person is talking about. I gave up on custom roms and just using the leaked tmo 2.2, thanks for that Eugene
kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate
Click to expand...
Click to collapse
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.
Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Update: Here is the link for the WIKI page.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
swehes said:
Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Click to expand...
Click to collapse
You are in a heap of trouble, a lot of people don't read, and you are gonna get 1000000000000000000000000000000000000000000000 repeats of the same issue.
"OMG! MY SD CAR DONES"T MOUNT< HELP ME!11!!111"
chui101 said:
I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.
Click to expand...
Click to collapse
The issue here is really that a forum is not the ideal place to manage software releases. A list of bugs emerges from community testing, but there's nowhere to "post" that list of issues, or attach it to a specific release. Since there's no way for the community to add such documentation, it falls on the ROM builder, who probably has other priorities.
This kind of project could be well served by using a real software project management software solution, such as say google code, which has an issue tracker and other useful features. But XDA does already give us a better tool than the forum - the XDA wiki!
I wish people would use the XDA wiki more extensively. This would be a good place to keep updated documentation such as this, without requiring the OP to keep a forum post updated with the latest findings. All the OP needs to do is link to the wiki page, and other people can help maintain it.
OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?
swehes said:
OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?
Click to expand...
Click to collapse
Depends on the project. The Linux kernel is GPLv2, so any kernels fall under that license. AOSP as a whole uses both GPL and apache code.
The issue with ROMs is that unless they're AOSP derived (like cyanogenmod) they often include binaries for which the license situation is murky at best, so google code isn't really an ideal fit for a "ROM" that's only ever released as a binary.
Really I was throwing google code out there as a well known example, there are tons of other ways to track issues. There are dedicated issue tracking systems such as trac, bugzilla, etc, but they require hosting. Most of the freely available hosted services require that you're running an open source project, which isn't necessarily true for the ROMs here.
IMO a serious project could very well benefit from such tools, but just using an XDA wiki page which community members can freely update is a great first step.
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.
Stargazer3777 said:
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.
Click to expand...
Click to collapse
Thanks. On both accounts.
Maybe this should be a post to Microsoft
To quote "there are known, unknowns and unknown, knowns and and even sometimes unknown,unknowns............but.........
Developers ----develop they do not become a bookkeeper of their development.........that is coordinating work...........good luck getting any developer in ANY Specialty to do that............. reporting bugs........
---Maybe this should be a post to Microsoft---
N8ter said:
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.
Click to expand...
Click to collapse
I have yet to see a REAL (completely dead) "bricked" vibrant from flashing a released Rom alone. I have seen a lot of user error cause boot loops or "soft-bricks" & HWL phones become unflashable because the end user didn't take the time to research though. As far as devs being "lazy" I dont really see that when the developer is coming here for us to tell him what else we find wrong. They are coding, you flash, you report back with a logcat. This is how development is made to my understanding. If ppl are to lazy to JUST do this then why shouldn't the developer discount long winded post or something they are not experiencing? If they know there is a bug its in the OP.
If you guys can change the interwebz & how 500 post per update are made completely useless please feel free to do so....
swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
I think it's a pretty awesome start for sure
As a matter of personal taste, I think having an individual wiki page per ROM (with the known issues and other detailed info) might be nice, although I'm not sure what the policy on new pages is with the XDA wiki.
Speaking from professional experience, the most challenging aspect of any documentation system is always convincing people to use it. It's great to compile the information, but unless ROM builders and devs post a link to the wiki in the forum threads nobody will ever see it. Having good, community based documentation is a benefit to everybody though, so hopefully people will recognize the utility of it and encourage its growth!
I'm having major missed call issues and was wondering how many people are having the same issue?
Also has anyone contacted Verizon about this issue? If so, what did they do about it?
Sent from my I500 using XDA Premium App
From lurking around i've seen that a lot of people are having this problem, regardless of rom/kernel/baseband etc... I myself have this missed call 'bug' and as of right now I don't believe there's anything we can do to fix it yet. As for telling VZ, yes they know about it and many people have complained, although they wont do much besides offer you a replacement Fascinate or a "comparable" phone (read: Droid X). If you're lucky you can smooth talk or berate them into giving you MAYBE a Droid X2 or Incredible 2.
tapatalked from my KangBanged Fascinate
Mike from VZW posted this on there site
Re: Any One Having Missed Call Problem After ED04 Update Post Here So We Can Get A Count[ Edited ] Options
Mark as New
07-01-2011 10:58 AM - last edited on 07-01-2011 11:03 AM
I have posted this in another forum thread about missing calls on the Fascinate, and I wanted to update this one as well with the updated information. This software release will address multiple issue including text messaging issues. Here's what I posted in some other threads:
I have been keeping track of this issue, and I have some news for those having the issue.
This has been escalated to the manufacturer. They rigorously tested and researched this specific issue. Samsung has developed a confirmed fix for the phones not ringing as of 06/30/11. We are working with them to finalize the fix and deliver it to the phones. I really wish I had an ETA to give everyone, but we don't have one yet. I just wanted to keep everyone in the loop.
Historically, these fixes have been pushed or updated via a software update. Here's a link to the Samsung Fascinate software update page in case we push this fix in a similar fashion. This page will update when we get very close to delivering the update if done via OTA software update.
Thanks again for everyone's feedback and patience.
Edited Note: I have also removed the resolution for this post. Perhaps once the software updates are launched, tested, and confirmed by multiple users as resolving the issue, then we can mark this as solved. Our goal is to fix issues, not just see the a green check mark on the page to make everyone feel better. I apologize about that, and I agree it was completely marked in error.
MikeS1_VZW
Follow us on Twitter @VZWSupport
Please look over recent topics (or use search) before posting a new thread... literally 10 posts below this is a 5 page thread called "Experiencing missing calls" where all your questions would have been answered. I'm not trying to be "that guy" here, but it is basic forum etiquette.
ooo, Sorry my bad, I didn't see that one before...mods please lick.