Hello
I made up a (very quick!) poll in order to estimate the statistics of the firmware issues and to try to link them to probable causes.
It only requires 20 seconds of your time so please consider answering even if you do not experience any issue.
Although the poll focus on 2.3.26 / 2.3.20 firmwares identified issues, answers for previous firmwares are very valuable to evaluate their origins.
Answer the poll ! (no thanks, but show me the raw results )
There is also a french version available (more than 250 answers already) :
Répondre au sondage ! (no thanks, but show me the raw results for the french poll )
I promise I'll come back with analytical results when there is enough answers (stats by device, influence of the type of install or the presence of google hacks, ...)
Thanks for your time. I mean it.
I just fill up the poll.
It's a good idea, but how we can make Archos reading this?
Flix123 said:
I just fill up the poll.
It's a good idea, but how we can make Archos reading this?
Click to expand...
Click to collapse
I'm not even sure they will eventually read it... But if they do (they definitely should), it may lead them to the origins of the identified bugs (and see that nearly 60% of users suffer from at least one of them ...)
Anyway, thanks for your contribution!
Just answered it, thanks for taking the time to do this, lets hope Archos actually reads it.
Arctablet has do this too, u with no results yet..
i hope this would be more effective
Lennb said:
Arctablet has do this too, u with no results yet..
i hope this would be more effective
Click to expand...
Click to collapse
The arctablet poll was for firmware 2.1.08 if I remember well and I can not tell for sure that archos devs efforts were influenced by it or not. Some 2.3.20 changelog entries seem to confirm that it might have.
Anyway, I have found out (like others did) that some bugs could be linked to probable causes (e.g. reboots loops / WiFi). This can be statistically confirmed and provide a strong hint for the dev team.
Also, nearly 60% of the pollers suffer from one of these bugs. This is a statistical proof that we're not talking about isolated cases and that something should be done.
Now I understand that archos business model require that all efforts must be focused on the Gen9. I'm just hoping that, when they'll come back to support tasks for Gen8, this poll will help them concentrate on the real troubles.
Thanks for your vote
Poll analytical results
Issues rate for firmware 2.3.26
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Issues rate for firmware 2.3.20
Issues rate for older firmware
Influence of type of install and / or google hacks on Issues rate
Discussion
- Overall error rate is very high (around 60%) but we should keep in mind that people that suffer from errors tend to take more the poll than others.
- There's not much differences between french and english polls.
- 32IT never reboot in loops (caution, very few results)
- 2.3.20 / 2.3.26 firmware show much more issues than older firmwares
- No noticeable change in issue statistics with fresh install (reinit)
- No noticeable change in issue statistics with Market hack (caution : few results)
Related
Seen this? Oh my, where do I sign up..?
IMG removed due to weirdness.
http://www.gsmcellphonereview.com/sony-ericsson-xperia-rachael-picture-and-specs-leaked/
http://www.gsmcellphonereview.com/sony-ericsson-xperia-rachael-more-official-pictures-and-ui-demo/
http://www.gsmcellphonereview.com/sony-ericsson-xperia-rachael-in-black-color/
- Android
- Qualcomm QSD8250 Snapdragon platform
- 1GHz CPU
- Dedicated graphics acceleration.
- Top-notch connectivity options such as Wi-Fi, GPS, and 3G-HSDPA support.
- 4″ WVGA touchscreen in 800 x 480 pixels
- 8 megapixel autofocus camera,
- Standard 3.5 mm audio jack and miniUSB port
Click to expand...
Click to collapse
Looks nice, but some of those specs are thought to be wrong. Apparently no snapdragon, and earlier reports on the rom/ram are wrong...apparently
MrRusch said:
Seen this? Oh my, where do I sign up..?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.gsmcellphonereview.com/sony-ericsson-xperia-rachael-picture-and-specs-leaked/
http://www.gsmcellphonereview.com/sony-ericsson-xperia-rachael-more-official-pictures-and-ui-demo/
http://www.gsmcellphonereview.com/sony-ericsson-xperia-rachael-in-black-color/
Click to expand...
Click to collapse
This is Android OS and no WM.
I really don't like the UI.
theoverseer said:
I really don't like the UI.
Click to expand...
Click to collapse
I understand, but remember - if it's Android based, creating custom UI's will be much easier. And with the new hardware this device is rumored to hold - possibilities are many and vast.
I believe we have a huge thread about it already.
orelsi said:
I believe we have a huge thread about it already.
Click to expand...
Click to collapse
I'm sorry, perhaps a moderator can remove the thread.
Future reader, please post in this thread.
MrRusch said:
I'm sorry, perhaps a moderator can remove the thread.
Future reader, please post in this thread.
Click to expand...
Click to collapse
MOD !! MOD !!
mod ???
anybody ??
The lack of moderaors is KILLING my willingness to go on developing and cooking... MR RUSH FOR MOD
(I am serious man, many constant users could be our mod, including you, but we DOON'T HAVE ACTIVE MODERATORS @ THE XPERIA SUBFORUMS !!!)
gtrab said:
MOD !! MOD !!
mod ???
anybody ??
The lack of moderaors is KILLING my willingness to go on developing and cooking... MR RUSH FOR MOD
(I am serious man, many constant users could be our mod, including you, but we DOON'T HAVE ACTIVE MODERATORS @ THE XPERIA SUBFORUMS !!!)
Click to expand...
Click to collapse
Well.. Ok, I'm a very active user, but obviously that is not enough for obtaining Moderator status..
Quote from FAQ:
"Moderators oversee specific forums. They generally have the ability to edit and delete posts, move threads, and perform other actions. Becoming a moderator for a specific forum is usually rewarded to users who are particularly helpful and knowledgeable in the subject of the forum they are moderating."
Click to expand...
Click to collapse
I'm not sure I am as knowledgeable as one would have to be. But I mean, for enforcing rules in the forum, and for deleting useless threads like this.. I think I could handle it And yes, there are far to few active Moderators.
I'm very sad to hear you feel this way though gtrab, as you are one of our real support-pillars here at XDA:X1. It's a shame that we keep driving people like you away with the lack of organization of the forum.
The problem as I see it is when you get "knowledgable" enough to become a Moderator, you most likely will be spending your time cooking and developing, and most probably have no time for rather simple tasks such as - deleting usless threads like these Sad downwards spiral..
It's already been discussed but I wouldn't buy this thing unless it has a slider form factor for a keyboard.
Does it apply to our MS2?
http://www.androidcentral.com/has-motorolas-bootloader-encryption-been-cracked
I'd be very surprised if it didn't. I don't believe they'd use a separate signing process for MS.
And all I have to say about this is: :3
Edit: Reading on their site (http://freemymoto.com/Documentation) it seems it was initially developed for the first Milestone. So I think we're in luck. At the moment it specifically relates to the Droid X which is basically... the same. So yeah. We should be good.
Edit #2: it's for anything with the SHOLES bootloader. So, if I understand correctly, that's all the current handsets excluding the very newest releases (Atrix et all).
Edit #3: We don't have a key for MS2 yet. The keys seem to be per device, but the process for finding the key appears to be the same. The key was originally discovered for the Milestone. However, it's trivial to calculate it, as the process for signing each of the phones is the same.
Edit #4: Talked to Nenolod. As I expected, the above is correct. Just gotta calculate the key for each handset, but it is for every sholes handset. This will allow us to create our own SBFs for flashing and not have them rejected. So we can theoretically replace the kernel. And not need to use the kernels that moto provided. In short: AWESOME
It seems like this is Kexec project.
FURTHER VERY IMPORTANT EDIT:
This means do not update with anything that Moto may release in the future for MS2. They can patch this problem away!
It will apply to our device, he provided an formula to get the code for our device. I'm no math-person though so don't ask me
This is the best news I've received all year
http://nenolod.net/~nenolod/sholes-keyleak-explained.html
Yesssssss this is the best news
Amazing?
I'm not afraid of Motorola patching this loophole away...they hardly ever release updates haha!
Oo !
That's just incredible, we absolutely need to test if the same key is used for milestone2.
How are we supposed to do this? What about eFuse?
If it works, champagne !
folks at MS1 forum have been talking a lot about it
http://forum.xda-developers.com/showthread.php?t=1001352
I don't agree with the people discounting the finding. I've dug through what is the theory behind it. Basically, if they used the same random integer (as sony did) and we can get more than one SHA1 codee (we can! each of the official roms has one!) you can directly solve X (let x = private key, used to sign the roms). If it's zero, it's even easier to solve.
That is, if it really is this cypher (elgamal) and they really did re-use the key for signing (it's not unheard of! look at sony! they did both of these things using the same cypher.) then we are home free. All that remains is to work out the process for signing the roms, and we can SBF to our hearts content.
Basically, the cypher used breaks down ultra simplistically to this:
SHA1 key = randInt (masterKey - 1)
It's very simply, but you'd have to know what you were looking for to get it. It's likely that Moto was just going for security by obfuscation, not -actual- security. Otherwise they would have used a real random integer.
the feedbacks are pretty negative. this is from kabaldan, who ported CM6 and 7 to MS1, http://forum.xda-developers.com/showpost.php?p=12261553&postcount=113
so? when will we know if it's fake or not? any O.T.A. of a clean .sbf??
Mikevhl said:
<nenolod> i think the bootloader signature verification is still worth looking into, even if my guess of what was going on was false
<nenolod> because that made motorola jump in a way i have never seen them jump before
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Therefore proven fake. I will release CM using the 2nd-init method so don't worry
Click to expand...
Click to collapse
At least we got a new ROM (Cyanogen!!)...
Absolutely confirmed as false.
http://pastebin.com/Y6J4fCQK
Guy was trolling. For no apparent reason other than to get people to pay attention to him.
*sigh* Back to the drawing board! At least we have kexec and 2ndinit
I really want to kick his ass now!
Sent from my MotoA953 using Tapatalk
I mean in terms of user habits. Can you:
- find out when the user is using your app/playing your game
- where they are geographically located (assuming they accept this prior to install)
- what the user has done in your game/app (as in what level they are at for games, or what data they searched for in your app)
- how often they click the banner ads in your app (if you own the banner ad for example)
- which banner ads they click (if you own the banner ad for example)
Thanks for your time guys!
yes, and that's not even the tip of the iceberg.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lol, nice pic.
so any anyone shed some light or recommend any articles which would tell me what type of info an android app can take ?
or a iphone app for that matter.
i don't like the way this conversation is going. if your intentions were good, fair and honest, you'd be asking 'how to make this kicking app', not 'how to monitor my users'. the first bit comes before the second one. and the second bit is just basic knowledge that you'd use from the first one.
Im doing this because I am writing a research report on app privacy. I am a Ph.D student. I have no programming background to ever create an app. I am just trying to post on forums with knowledgeable people like this one to gain a bit more understanding of the privacy issues of the iPhone vs. Android.
If you would not like to post here, please feel free to PM me.
Thank You.
it's very simple. look at the docs for android, think how it could be used to monitor users, et voila. an app could have total access to the phone meaning all data that is on it could be monitored by an app. whether the user will use your app that wants all these permissions is unlikely and you really are asking a pointless question.
you are a phd student, i'll assume you can think for yourself, and so you sh/could be researching this for yourself by reading the docs (mind you, you will have to think though). no one is going to come out and say juicy things like "well, if you do this, you can get this info and this info and use it to do this" because it's probably going to be illegal. it's your paper, your credit, think man, think.
misc86;13318741I have no programming background to ever create an app[/QUOTE said:
well, you need at least the basic understandings you'll gain from (again) reading the android documentation. it's open source, you could (heck) even read the source code.
Click to expand...
Click to collapse
misc86 said:
Im doing this because I am writing a research report on app privacy. I am a Ph.D student. I have no programming background to ever create an app. I am just trying to post on forums with knowledgeable people like this one to gain a bit more understanding of the privacy issues of the iPhone vs. Android.
If you would not like to post here, please feel free to PM me.
Thank You.
Click to expand...
Click to collapse
Defcon video about privacy
http://vimeo.com/14980971
Watch that (very informative), then maybe read:
Google Analytics
http://code.google.com/mobile/analytics/docs/
Flurry: company used by a lot of apps to do in-app tracking
http://www.flurry.com/product/analytics/index.html
Maybe check out AdMob's site too.
My site - 13 page permission guide
http://alostpacket.com/2010/02/20/how-to-be-safe-find-trusted-apps-avoid-viruses/
Also Android Police is a decent site for security news (IMO).
I also just released an app that's a guide for people new to Android about permissions but I dont think I'm supposed to link to it here.
Google "PocketPermissions" and some links should turn up to read about it if you want.
Hi everybody,
just wanted to let you know that I have successfully booted up CM6.1. Was kinda tricky but hey I promised to do my best. Now bugfixing time!
Please have a look here for more infos:
CyanogenMod6.1
I will post a bootup-video + some screenies later!
Ahh by the way: I would like to say thx to stockwell for pointing me to the right direction with a kernel-related problem.
Great work, can't wait to see what you did so I can see how close (or far!) my attempt was from working.
Edit: I notice you mention that the packages won't be made public. How do I get my hands on them?
stockwell said:
I notice you mention that the packages won't be made public. How do I get my hands on them?
Click to expand...
Click to collapse
I'm happy to test and provide feedback also. Well done.
@stockwell: I'll share it for everyone getting in contact with me! It's not even ready for a public release. It's meant for devs as I hope we will get some steps further with teamwork!
Please follow link on 1st post to grab the Alpha Release!
Could you give some info that what is working right now and what is not?
Verry nice to see that someone is porting
Gratz with the boot!
You were right, this is too much for me lol.
Not working:
Radio (Wifi, GSM, WCDMA, Bluetooth, FM, GPS)
GPU Acceleration (I think, the interface while speedy moves choppy)
Many other things
I will do some more messing around this arvo to find out more but this definately is not for those who need their device to be usable. It did boot fine though.
Yap it's meant for devs but I am working on the fixes
Thanks for your effort!
Is the X5 special in any way or is this many fixes always needed when porting CM?
vatoloco said:
Hi everybody,
just wanted to let you know that I have successfully booted up CM6.1. Was kinda tricky but hey I promised to do my best. Now bugfixing time!
Please have a look here for more infos:
CyanogenMod6.1
I will post a bootup-video + some screenies later!
Ahh by the way: I would like to say thx to stockwell for pointing me to the right direction with a kernel-related problem.
Click to expand...
Click to collapse
thanks,you are the best one
FYI: Got 3D partially fixed! Will provide a new update (including several fixes) in the next 24hours. It will be available again via link on 1st post. That's all for now
Would you be able to post up how you did what you've done so far on fixing 3D?
Would you please upload the source to github?
is radio working ?
no radio!
Alpha2 now available via 1st post! Still buggy and needs fixes...
Would you be able to post up how you did what you've done so far on fixing 3D?
Click to expand...
Click to collapse
Have a look at boot.img. I added kgsl specific perms to init.rc's. This works also with init from Vision (109,6kb) but I reverted back now to B160 init
I'm not developer my self, but is it possible to use kernel or radio drivers from another phone model ie. Desire z to get rid of those problems with randomly dropping 3g connection? I understood that desire is nearly with the same harware.
Sent from my u8800 using Tapatalk
That's something kernel devs should have a look at!
Anywqy if you follow link on 1st post there's now Alpha4 available.
Perfromance of this rom is very good compared to the stock Huawei. I was able to get over 2500 in Quadrant at 1.5GHz over 300 points higher than the stock rom at 1.5GHz. People should give this rom a go it's working great on mine so far. Only things I notice aren't working are camera, haptic and mobile data. There are a few bugs here and there but nothing major. It's fast and smooth. Screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
More users means more bugs found and fixed sooner!
Also not working:
Light meter
Compass
When mobile data works, then i will try, droolin til then
XDA depends on posts and threads. Making decent posts and threads is key to helping someone out and making XDA a much better place to be.
The original guide can be found here.
However, I am going to edit a few of these points to better associate it with XDA and forums in general.
To restate, this is not of my creation, and I highly recommend reading the original before reading this thread.
Stephen King has made a career of writing thousand-page-long books about ancient evils haunting divorced writers in Maine that are rich in detail to help the reader get absorbed with the story.
However – spoiler warning – you are not Stephen King. Thus, just because you write a wall of text that doesn’t mean people are going to read it. In fact, it’s a great way to get your post sent directly to the rubbish bin…
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Keep it short and simple. Write it like you would a Tweet, but with better grammar. And pay attention to those squiggly lines – with today’s technology there’s no excuse for bad spelling. Remember in school when they taught you about paragraphs? Use them!
RULE 2: White Space is your Friend.
Along with short and simple, be sure to include white space. Separate your 3 main parts with double spacing. The words themselves aren’t always as important as your formatting and it being easy to read. Think of a sign or a movie poster. Does it convey the information quickly and clearly? Or is it a mess?
RULE 3: Who you are. What you do. What you want.
This is the most important part. 9 times out of 10 you’re not just responding to a thread to say “I love your work” but because you want something. Therefore you need to be very clear about this in your post and not get bogged down in detail.
Your post should include 3 things: your firmware/rom version, your kernel, and what you want. Follow these simple things, and write them with ONE LINE EACH:
1) Your firmware/rom version: MIUI 2.8.28? AOKP Milestone 5?
2) Your kernel and version: Franco 241, Faux 19b6, also include what recovery you are using.
3) What you want. Don’t be afraid to ask because the person already assumes you want something. Just write it as plain and simply as possible. There should be no question as to what you want – one problem with a wall of text is the person might not understand what exactly you’re asking for. Also, search as much as possible before posting.
However you should be somewhat specific, ie, “What are differences between rom X and rom Y?” instead of “What rom is the best?” Roms are different for everyone, so you should really try what you think will fit you best.
Finally, add a brief thanks. I usually include this with the request line, to keep the entire post 3 lines long.
Also, hitting the thanks button when someone answers your post/question is much kinder than just saying "thanks".
Some final tips:
Never post a question you could have researched on your own, especially if it’s outside the expertise of the person. Example: “I see you’ve never modded a rom or theme. How would I go about doing that?” How would I know? I’ve never done it!
Use correct spelling and grammar. Nothing says “I don’t take care in what I do / I can’t afford what I’m asking for” like bad spelling. Also the first word of sentences should be capitalized.
Your first post is a request – not a discussion – so skip the fine details until they reply. A billboard for Pepsi doesn’t list all the ingredients.
A good signature line, with your name, title, company, contact info. Even if it’s made up, it looks official and you’re taken more seriously.
Once again, this guide is not mine, but is taken from the above link and edited to fit XDA.