Related
Well, even though I actually don't have a problem with WinMo 6.5 outside of a few minor annoyances I've decided to make the switch over to Android...guessing NAND...though, still looking to here about WinMo 7...
I'm just noticing that there is more support and apps being developed for Android and the future of my HD2 suddenly shows more growth...have my fingers crossed waiting for Netflix to resolve the DRM issues they have with Android!
I was always waiting for a solid Android build that actually replaced WinMo (NAND is finally here). During that time I used WinMo and actually liked it. First thing I will miss is the customization. I don't think there's another Mobile OS that beats it in that department...and I REALLY like customizing.
I've been using Android more now and still don't understand how the NAND will work. Have read a lot...as far as installing, that won't be a problem with me. My questions start with customizing. Where will the media folder be? Is there a folder on the SD card that Android associates ring tones with? I make my own ringtones as mp3 files, so i need to know the structure of how Android handles media. WinMo was simple. Also, the Android build I was using did not support USB without major hickups...well...it just didn't work. I'm not going to assume all Android builds are like this, but can I expect Android to be able to link via USB and I can work with it as a storage device and create folders and organize in this manor?
I know you guys work hard and appreciate it, so please do not take this the wrong way. Which Android build is the most stable at this time with all features working? I ask this cuz I notice there tends to be some builds that come along much slower than others and bugs as well as a lack of hardware support can occur. Is there a build that's considered stable and all hardware is supported?
I've basically been trying to make Android provide the same experience as far as apps and ease of use I had with WinMo...I think I'm there.
Does Android have a set structure with Wallpapers...ringtones...documents and such? Example...does each file type have its own folder on the device or storage card in which Android associates the tools which manages them? I always keep my device clean and move all files to the card that don't NEED to be on the device. Is this possible with Android?
Android play well with Microsoft Docs?...Word?
I've always felt that Android ran smoother than WinMo 6.5. I noticed after a while it can get a little sluggish. Is Android like that? I believe Android is Linux base? I'm expecting memory management to better. On PC, I'm use to any Unix based OS to out perform WinAnything with resource management.
I also noticed something strange about some of these apps in the Android market. One, a lot of adds within the apps. Two, a lot of these apps tend to require access of priveledge areas that can be security risks...to make it worse you fine yourself saying why a browser would need access to anything else outside on internet and maybe GPS. Other apps have access to areas that make no sense to me.
Are their security issues with Android...it's market...or apps?
That's all i can think of now. Didn't have a moment to proof read, so please excuse me. Have to take care of a few things. be back shortly.
Thanks.
WOW! What can I say... Ditto. I love WinMo, but I'm fearful that I'm watching it's death rattle. Win Phone 7 seems like a illegitimate infant in a world of fast moving, focused, college freshmen (albeit, not the brightest).
I had a lot of reservations with switching from WM. Mainly related to the phone being able to handle work related stuff. So I too ran WM and android on SD. I must admit though, that after having run android for almost 2 months without loading WM, (I basically pretended I had bought a new phone and forgot all I could do with WM), I had figured out work-arounds and got it running more than sufficiently. The only problem I had was having to back-up the SD in fear of a random reboot corrupting the data.img. Now with NAND, it's no longer a problem. I can honestly say that the switch was easy, and I'm glad I no longer have winmo in my life.
IMO Android is a far superior OS, and I can't sing it's praises enough.
As for all the questions:
Media folder is built like this:
media
->audio
->->alarms
->->notifications
->->ringtones
->->ui
Different folders are available for their obvious uses (i.e. go into ringtone selection, and you don't get the ui folder listed).
USB is more than stable (for me at least), never had a problem since NAND. Having most stuff moved to SDCard the phone hates it when I plug it in as a disk drive, (widgets disappear etc.) but within a minute of unplugging it it's back to normal.
I personally feel the desire build are the best, however as for more stable? I believe we are reaching a plateau where stability is the norm. I have tried nexus builds, and have had no problems with them either, it's just personal taste. The HD builds (Desire HD Base) are a little more 'experimental' but with reading, you'll learn what works on each build, and what doesn't. Figure what's important to you, and check.
The best advice I can give is get hold of SPB Backup (For WM). Do a full backup. Then jump in at android's deep end. (After reading how obviously). If you don't like it, re-flash winmo, redo your backup, and it's like you never left. You won't regret it though.
Man I'd love to dump WM as well, bu I can't bear the thought of all the days going by where I can't be the dude on the bus who reboots into ubuntu to pass the time...sigh.
MattOG said:
The best advice I can give is get hold of SPB Backup (For WM). Do a full backup. Then jump in at android's deep end. (After reading how obviously). If you don't like it, re-flash winmo, redo your backup, and it's like you never left. You won't regret it though.
Click to expand...
Click to collapse
Microsoft My Phone actually does fine with all the backup I need.
I'm still wondering about security issues. Example: http://news.cnet.com/8301-1009_3-20026804-83.html
Also, hit a bump in the road. It would seem that Android doesn't support the Mugen 2600 Extended battery!
The primary security issue with Android isn't Android or Linux, it's Google. Google's security is very problematical, Gmail has been hacked (as has Gmails security software) by someone.*
*Some think it's the Chinese government, the official Chinese response is, "No, it's just kids" but since all hacked accounts we know about have been dissidents, the government theory looks pretty solid....
The primary issue is NOT Google. It's the user.
If you're loading up banking apps on a device that you could lose, be stolen, or bluetooth hacked, then don't blame anyone but oneself.
I've yet to know anyone who's been phone-hacked if that's any consolation.
As a former hd2/android user Id have to say It makes the entire experience of the phone better.
I think it also depends on what you are use to. as far as customizing I would venture to say that there is just as much customization with winmo as there is android. Though id have to say I found myself looking for skins more often than not cause winmo was so ugly to me.
I enjoy having almost direct access to all my data without it having to look like winphone7.
As far as security I think its always been tighter because most people were on different types of phones. now that we have blackberrys and iphones and android phones I think possible viruses will show.
I believe google has a built in kill switch for rogue apps. Also if you buy apps from the legit market you should have no problem!
Ok two things that I'm trying not to get frustrated about before I put a little research into it...
First, why in the world does Android want to crop every image instead of using the entire image as a wallpaper?
I even have wallpapers that are the exact size of the display and Android still wants to crop a small portion of that image?....help please...
Second, why can't I get a simple widget or window dedicated to favorite contacts, such as sense in WinMo does without having to pay for it?
Android doesn't have a simple tool that allows you to setup a favs like Sense does in WinMo? There's this LaucherPro that wants to charge me to do so?
Thanks
Why does Photoshop Express require access to personal information, phone calls and full internet access?
Devils1stBorn said:
Why does Photoshop Express require access to personal information, phone calls and full internet access?
Click to expand...
Click to collapse
checking the install notes It says
the only one that bothers me is the it reads contact info.
the phone state is different than phone info. it basically should shut down when you recieve a phone call. why it needs access to your contacts is why im uninstalling it.
I can also set basic contacts by long pressing a blank spot on the screen and selecting shortcuts>contacts>the actual contact.
wallpaper I believe if you set the picture with the proper resolution it shouldnt crop it
Devils1stBorn said:
Ok two things that I'm trying not to get frustrated about before I put a little research into it...
First, why in the world does Android want to crop every image instead of using the entire image as a wallpaper?
I even have wallpapers that are the exact size of the display and Android still wants to crop a small portion of that image?....help please...
Second, why can't I get a simple widget or window dedicated to favorite contacts, such as sense in WinMo does without having to pay for it?
Android doesn't have a simple tool that allows you to setup a favs like Sense does in WinMo? There's this LaucherPro that wants to charge me to do so?
Thanks
Click to expand...
Click to collapse
1. You can just expand the crop window so it encapsulates your entire wallpaper, if it indeed is in perfect size. Keep in mind the crop window is sized for 3 homescreens or 5 or however many you have, so if your perfect size is for just one screen (480x800) you'll have a bit of a problem there.
2. You can just place contacts on the desktop. That's the closest you'll get without paying for this in LauncherPro. While you're at it, even if you don't want to pay - get LauncherPro and replace the default Launcher already. You'll love its speed superiority immediately.
A lot of devs put permissions on to prevent possible problems, also, not sure if it relates to android, but I know some permissions are needed for things that you would not normally relate them to, possibly things like automatically pausing operations when a call comes in etc...
schunniky said:
1. You can just expand the crop window so it encapsulates your entire wallpaper, if it indeed is in perfect size. Keep in mind the crop window is sized for 3 homescreens or 5 or however many you have, so if your perfect size is for just one screen (480x800) you'll have a bit of a problem there.
2. You can just place contacts on the desktop. That's the closest you'll get without paying for this in LauncherPro. While you're at it, even if you don't want to pay - get LauncherPro and replace the default Launcher already. You'll love its speed superiority immediately.
Click to expand...
Click to collapse
I figured out the contacts on desktop, thanks though!
As for the wallpapers, I do try to expand the Window and it never completely encapsulates the entire image. I just dont get why Android doesn't allow the Wallpaper to remain static while your homescreens maneuver over it.
Hi guys,
I thought i share my thoughts and experience with people who have not decided which phone to buy. Maybe my input will make the decision easier (or maybe it will confuse you even more hehe).
Also I am hoping people with Android experience maybe can assist me with some of my negative bullets. I'm very new to Android so i apologies for my mistakes in my so called review/comparison.
And lastly i dont want to start any fanboy android vs iOS. This is just my personal view of the two phones/OS'es. Its maybe a bit unfair since i been using iPhone for the last 3 years and Android for only a week but still some of the bullets are independent of that. Any how lets dig into it, First i take the negative side of SGII and next the positive sides.
(maybe my topic is a bit misleading but below some of the items are compared against iPhone but i wont write all the plus/negative for iPhone since the SGII list is already pretty big and i want to focus on SGII which i hope can replace my iPhone)
- When i exit USB mode (where i can access the SD card) i cant find a way to reconnect it without cable unplug->plug. Is there a way i missed?
- Browser doesnt word wrap the text/column so good on table tab. I had a side by side comparison with my iPhone4. On iphone the whole article including images are resized and the text is fully readable. On Galaxy S2 images are not resized and text is readable but just barely. So the whole screen real-state is not fully utilized with the lower resolution and bad browser formatting.I have tested Opera also but the whole word wrapping experience left a very bad taste in my mouth. It was the worst experience ever, the article jump up and down every 5 sec or so, i think the browser got confused for some reason and couldnt decide how to format the page (this was when double tapping).
- Default browser crashes (go to qj.net where i usually visit to read about games).
- Text selection is a pain sometimes. First problem is that in every app it behaves differently. Second problem is that the process to select a text isnt so smooth.
- Confused about task and background proceses that start magically! When using taskmanager i can see mostly 2-3 tasks there and this makes sense. Now using other task killers suddenly they show 10-15 tasks. I understand these are background task but its beyond me why some of them suddenly are there. Like Kies, this should never be started unless i am using Kies. I can see now why my battery goes dows so fast (well compared to iPhone again). Why is there so many tasks started and why cant i control them from vanila Android. This should be a must. I dont want to root my phone to do the basic settings.
- Pretty much all application is downloaded can only be installed on phone memory. Why doesnt Google enforce developers to adapt to new versions of Android is beyond me.
- I havent found a way to backup everything on the phone (including applications and their save data) to my pc/mac. Without this i dont like to experiment rooting and other shizzles.
- Apps are not as smooth and functional on GS2 compared to iPhone4. Ex: Tunein Radio, i cant skip to next song. Ex2: ign app (iphone) allow for daily videos while the Android version is very poorly done and dont have any videos. Feels like Everything works just a little better on iPhone compared to Android phones.This is something most people cant understand if they havent had iPhone for a long time i think.
- Slow battery charging. I usually start charing at around 20% battery left. In one hour GS2 reaches around 40-50% while iPhone goes to 80%
- Headset lacks volume + next/back track when playing music.
- Creating folder through Kies Air not possible. for ex in media make a folder called movies.
- Drag&Drop in Kies air missing.
- When uploading a file through Kies Air there should be a progress bar, now it just looks busy and you dont know if its uploading or it hangs.
Ok now to some good sides on the Galaxy S2:
+ Brilliant screen (even if i think resolution could be better)
+ Flexibility and open market for every sort of application. Much like windows here you can add more functionality and make the phone very personal.
+ Excellent codec support. It plays pretty much everything i through at it. Well done Samsung.
+ Very good camera (even better then iPhone i admit)
+ Very good video recording (also better then iPhone)
+ Very light
+ Feels pretty good in your hand (even though i’m afraid one day the backvocer will break, i had a Nokia N95 and one day the smal plastic edges broke when i was opening the cover. Same thing will happen ti GS2 i’m sure)
+ Expandibale uSD.
+ Very cool fearure called Kies Air where i can access most studd through browser. (this can also be added to minus since it doenst work perfectly everytime i tested but the potential is there)
+ Nice features like pinch effect for desktop + many nice widgets.
+ I think you can make proper call recording on SGII (CallRecorder) but havent confirmed myself yet.
Lastly i like to say SGII is a wonderful phone and i really really want to use it as my primary phone. The one thing i hope Samsung fixes that will make me more loyal to Android is the default browser. The text wrapping must be improved and the browser more stable. I like the smoothness of the default browser and this is the most used part of the phone and so far my iPhone is better but i hope 2.3.4 update maybe can improve this.
Any input, tips, tricks are welcome. I really appreciate your help.
Hopefully this will help you, at least in some areas (i numbered them in the order that you have used):
1) using developer mode at least (i prefer it as its faster and more compatible than samsung's stuff) you can mount/umount at will the card on the pc via the phone without unplugging
2) You may want to try Opera Mobile, it seems to do a very good job at this. I'd like to see this in the stock browser too, but hey, this is Android, you have the choice to change the browser if you like ;-)
3) Well, same thing I guess. 2.3.4 may improve stability but the rest, I don't know, I wouldn't bet on it. I like Firefox quite a bit as well, but text wrapping is odd on it.
4) Android issue =/
5) I wouldn't use any task killer. Check the active apps and uninstall any app that doesn't behave (keep only the ones you REALLY need that still do stuff in the background, like email etc, but not too many). Seems to work a zillion time better for battery life. Unfortunately, there doesn't seem to be a decent way to enforce such a policy.
Regular background tasks are not necessarily ever active. It just means they're frozen in the background and do nothing. As long as they do nothing it's fine, it's just faster to start them again (instant, in fact). The issue is really when they're activating every XX minutes while in the background.
6)Doesn't matter, the recent samsung phones such as the SGS2 have a HUGE internal memory compared to other phones, you'll never have space issues for that imo.
7)Install a kernel with CWM and then, boot in recovery and run a nandroid backup. It will create the backups on your sdcard. Copy them to your PC. Also, copy /efs using tools or manually..
You can restore using a CWM kernel later on and nandroid restore.
You can also use stuff like TitaniumBackup, but it's not nearly as thorough as nandroid backup (which is doing basically disk images, while Titanium and other such apps just copy app/settings)
8)Trollish subject. Some apps are superior on Android, some are superior on iOS. Heh SGS2's browser speed eats my IP4 for breakfast for example. If the same Android app doesnt have the feature of the iOS app, complain to the dev or find another app.
9) it's true it's like that, nothing you can do about it (technically, something could be done but that's probably not wise at all)
10) Use another music player, such as PowerAmp if you like. There's (many, many) other possibilities as well. It also let you boost the volume higher than the stock max volume (although I find stock to be loud enough)
11) Don't use KIES air to do that then ;-)
12) Likewise. There are apps like KIES air, you might want to try them btw. Make a little search, I dont have the name in mind, but they do exist, others will probably point them out
13) I do get a progress bar that moves, maybe a browser issue. Anyway, see point 12)
Cheers for the answers and help. I write the comments inline below.
bilboa1 said:
Hopefully this will help you, at least in some areas (i numbered them in the order that you have used):
1) using developer mode at least (i prefer it as its faster and more compatible than samsung's stuff) you can mount/umount at will the card on the pc via the phone without unplugging
A: i did test this mode but it asked me to unplug the cable also, same thing for MTP. Dont you get that?
2) You may want to try Opera Mobile, it seems to do a very good job at this. I'd like to see this in the stock browser too, but hey, this is Android, you have the choice to change the browser if you like ;-)
A: As mentioned i already tested this. Opera does some things better and some things worse. For instance visiting one of my favorite sites like Engadget.com the whole page jump up and down when i zoom in a little. To be honest the stock + Opera feel very bad compared to iPhones browser. I hope Opera or Samsung improve on this area. This is the most used feature for me.
3) Well, same thing I guess. 2.3.4 may improve stability but the rest, I don't know, I wouldn't bet on it. I like Firefox quite a bit as well, but text wrapping is odd on it.
A: Lets hope so
4) Android issue =/
A:
5) I wouldn't use any task killer. Check the active apps and uninstall any app that doesn't behave (keep only the ones you REALLY need that still do stuff in the background, like email etc, but not too many). Seems to work a zillion time better for battery life. Unfortunately, there doesn't seem to be a decent way to enforce such a policy.
Regular background tasks are not necessarily ever active. It just means they're frozen in the background and do nothing. As long as they do nothing it's fine, it's just faster to start them again (instant, in fact). The issue is really when they're activating every XX minutes while in the background.
A: Yes true, i think Android just shows to much info for regular user. I have to see past the background tasks perhaps. Also some appz you can not remove like the hubs and such. Sure i can root and hack but i'm not so interested to do so just yet. Maybe when i'm a bit more user and understand Android better
6)Doesn't matter, the recent samsung phones such as the SGS2 have a HUGE internal memory compared to other phones, you'll never have space issues for that imo.
A: Actually i got over 12Gig of Appz on my iPhone so 16Gig (or actually 12Gig which is free) isnt all to much when you have navigator (3,5Gig) and games and blogs and such. But sure its enought for a time to come. The bottom line is Google must be tougher with the market otherwise the fragmentation will just grow.
7)Install a kernel with CWM and then, boot in recovery and run a nandroid backup. It will create the backups on your sdcard. Copy them to your PC. Also, copy /efs using tools or manually..
You can restore using a CWM kernel later on and nandroid restore.
You can also use stuff like TitaniumBackup, but it's not nearly as thorough as nandroid backup (which is doing basically disk images, while Titanium and other such apps just copy app/settings)
A: Thanks for the tips, i will write it down. As said i dont dare yet to mess with hacking but soon i was actually considering using the TitaniumB , hear its easy to use.
8)Trollish subject. Some apps are superior on Android, some are superior on iOS. Heh SGS2's browser speed eats my IP4 for breakfast for example. If the same Android app doesnt have the feature of the iOS app, complain to the dev or find another app.
A: I'm noob on what is there on the market so i'm sure there are many awesome apps on Android but when comparing the same app on Android vs iOS the Android was inferior. That was what i was comparing.
Another thing i dont really experience is the speed. To be honest i dont see such a huge speed difference when using my Wlan at home. But maybe you are right
9) it's true it's like that, nothing you can do about it (technically, something could be done but that's probably not wise at all)
A: I guess your right. On the other hand it could be possible a fw update could adjust some values for the current input, this could be a software limitation also i think. Lets hope
10) Use another music player, such as PowerAmp if you like. There's (many, many) other possibilities as well. It also let you boost the volume higher than the stock max volume (although I find stock to be loud enough)
A:Thanks for the tips will test this. Actually this is same thing as the copy/paste issue. I expect the behaviour to be the same no matter application (coming from iOS) but here it seems its application to application. This offer more freedom to developers for sure but it will also generate crapy software and result in a bad user experience. It would be so much better if there were a set of rules that all developers should follow on certain areas (this one is one such area).
11) Don't use KIES air to do that then ;-)
A: hehe true but this is the official way so i thought it should have been well tested and all
12) Likewise. There are apps like KIES air, you might want to try them btw.
Make a little search, I dont have the name in mind, but they do exist, others will probably point them out
A: Will do.
13) I do get a progress bar that moves, maybe a browser issue. Anyway, see point 12)
A: Strange, have to test again on IE which i hate, i use Firefox only. Also tested Safari on my mac.
Click to expand...
Click to collapse
Thanks again for your input mate. Back to play more with my GSII
Applications can also be installed on the external sd card.
Applications and I also believe their user data are backed up on google server. So if you factory reset the phone and sync with google, it will download all previous apps.
About the slow charging - are you on old firmware version or do you charge over USB?
Creating a folder through kies air is not possible, that is correct. To be honest I am happy that there is even an app which allows to copy media etc. over wifi, you know there are phones which don't have that, for example the iPhone.
All apps I am using are working fine. If an app is not stable it's developer's fault, not the phone.
Ios is from 2007.. android 09.. 1-2 years between them. just think how far android have gone the last year.. give it 2 years and then compare it to iphone 4 in it current state.. well yes i know android is older.. but the initial realse was around 08-09 and IOS june - 07.
and yes.. so far iphone fits those who just want it to work better.. that means ppl not that used to computers etc.
and currently i dont own an iphone but i got a first generation ipod touch.. and yes even that stoneage IOS thing does alot of things better then my S2..
bah but this iphone vs android is getting old its a subject that can go on forever and ever..
well ill stick with my laggy android.. well i've been told by my iphony friends that its laggy.. i just dont see it
vampyren said:
Hi guys,
Any input, tips, tricks are welcome. I really appreciate your help.
Click to expand...
Click to collapse
Nice overview.
IMO S2 is the best phone on the market now. But due to appl's hype, n matter what hardware specs they release, the iphone will always be superior to ANY phone. They could release an iphone with 1st gen hardware, and it will still make more sales than sgs2.
But, slowly more and more ppl are moving towards androi, and apple are losing sales. they even copied bb and android in ios 5..
Also coming from an iPhone 4 to the GS2 I can safely say that I don't miss the iPhone at all which I thought I would.
Having owned a Nexus S in the past and feeling a bit bewildered as there was a lot of stuff within the OS which felt unpolished and unfinished and now 2.3.3 is like night and day for that and it feels much more like a complete OS to me.
@OP give it time there will be a lot of things you can do with your new phone which would require rooting on your iPhone 4
The world of apps and widgets and customization is at your finger tips so jump right in and enjoy
My phone is running ADW Launcher EX with 90% icon dock size, 5x5 grid for homescreen, transparent drawer and miui weather
The only thing you might miss is the app store and iTunes integration (if you use it), other than that the Galaxy S II has it beaten quite comfortably.
@zxz0O0:
OOH that is cool , i think some option about it but didnt think it was what i thought it was nice to have it confirmed. Then this is pretty much what Apple is adding into iOS now with the cloud thing. Pretty cool Android has it already. By the way why do people use program like TitaniumBackup when there is google sync ? is there any limitation to the cloud backup? will all games data, programs data, settings be backed up or just Android OS stuff?
About FW i use the latest i think KE7 i think its called but i read there is a new one coming out next week so hoping for better battery life.
And your last point is something we can debate about for a long time but my view is that if you dont have strict rules developers do what ever they want and can let their app go without update. On the other hand if Google enforce some guideline like having option to install to SD card developers must go by that or their application is removed from market. In the end users will benefit and the platform will grow. But this is my view alone.
@olyloh6696:
I dont think its just hype really. I mean we are comparing a year old phone to SGII here and they are pretty much head to head in most scenarios i tested. But i see your point and i do agree that Android has a charm about it. I love the moving background, i love the whole flexibility to do what you want with the interface. Specially SGII's support for codecs so i dont have to spend 2 day re-encoding all my movies etc. So there are definatley benefits with Android but iOS has the benefit to be easy and working perfectly with the functions it offers from the get go. I think its a matter of preference and more advanced users will move to Android (a bit like me).
@daleski75:
Yupp i think i just need to play with it more and get used to the eco system
I think i will harass Opera developers to fix the formatting thing on the webpages now
Thanks for your input guys, gonna go out and take a walk now, later.
There are also many other good browsers, xscope, miren and dolphin hd to name a few, they all have their own way to format the page and all are pretty good many have different options too for formatting and text wrapping (I believe the default samsung browser also has some options)
also I believe google sync doesnt save all app data (eg angry birds progress is not saved)
That is correct...Google Sync doesn't backup app data (like your Angry Birds scores). This is where Titanium Backup (commonly abbreviated to as TiBu) comes in. It "sort of" does cloud backup (via Dropbox), but its strength really shows when you start installing/changing/updating custom ROMs. Typically, it's used to backup your apps and their data to a folder on your SD card. I can also do some pretty advanced stuff that you probably wouldn't use much (if at all). In my view, the strength is it's ability to deal with batch jobs. For example, before installing a new ROM, I backup all user installed applications (non-protected ones, anyway) with only a couple clicks. Restoring is just as easy, provided you have the paid version (it allows for hands-off batch restore of your apps). Another cool feature it has is "freezing" apps. Say you root your phone and may want to clean some carrier crapware off of it, but aren't *totally* sure. You can freeze those apps...they stay installed and can be defrosted at any time, but they won't be available for use until you do.
Also, I agree with you that a lot of iOS apps are much better than their Android counterparts. I believe this is the case for one main reason: there are tons of people using Android and tons of people on iPhones...you can essentially count on one hand the number of iOS phones Apple has to support, and they are all sold by Apple. Now, look at the number of Android phones and devices and their individual specifications...that makes developing apps for Android pretty complicated. Devs have to take into account different CPUs, memory limitations, and the biggie--SCREEN DIFFERENCES! However, I like being able to run an app developed for a phone on my Honeycomb tablet. Yeah, it may be ugly (not necessarily), but it almost always works! I have a network tool I use that only shows up on about 1/6th the screen of my tab, but I don't care...it still does the job.
Don't forget another important aspect of the Android vs. Apple thing...Apple has control of their devices and their operating systems, and the cell phone carriers don't have control over when Apple releases an update. On the Android side, you have some manufacturers that are prompt with getting an update ready, and those who abandon their devices after they leave the store shelf. Not only that, but those who do release updates, and most do, have to deal with the likes of AT&T and Verizon and everyone else here in the US. Each company wants a ROM customized only for them, and sometimes the manufacturers actually have to pay the cell companies to push out updates. This is what causes the splintering of Android, but openness is what gives it its strengths.
As a general rule, I find that the more "techy" people like the Android OS, since you can customize it and tweak it like crazy. Those who aren't quite as savvy will probably like iOS more (there's less to screw up and they all look the same). Please don't flame me for saying that...it's just a general observation that has many exceptions.
Well that's my two cents. Maybe it will be helpful in some way? <*schrugs*>
Brad
Sent from my Inspire 4G using XDA Premium App
There is no practical comparison possible between the mentioned phones.
Appreciate the explanation brad, TB is a nice tool indeed
Just one point, In regard to customization i can pretty do anything also when i jailbreak the iphone which is even simpler then rooting Android and what all techies do anyway with their Android phones
But i agree Android has its charm with the more open eco system.
The 2 area i wish to have before it gets perfect is the browsing and more resolution for the big ass screen (4.3)
I've rooted my phones but haven't rooted my NST yet.
I'm interested in doing it mainly to get access to Dropbox and one of the Dropbox apps that let's you get feeds put onto your NST daily (I want to get my local paper there--which is available). I already have the paper portion working locally.
I have a few concerns:
1. What's the absolute latest/best way to root the NST? I'm on 1.1.
2. Will rooting suddenly drive my battery life down while the NST is sitting idle? I can go a week without touching it. I don't want to have to charge it every time I touch it.
3. Are the latest approaches problematic? I'm seeing threads about people having some pretty serious issues. Should I just wait at this point assuming there's serious thought to a near-bulletproof approach right around the corner?
All roots are pretty stable, there have been some methods that have had issues. TouchNooter for example had a major issue just yesterday because of a space in an Apps name. But it's been resolved and is stable.
Battery Life won't be affected so much depending on your wifi settings, if you keep wifi off you won't notice the difference between root and non-root. If you keep your wifi on though you may find yourself needing to recharge more often if you have your nook doing data updates too often.
Each version has it's advantages and disadvantages:
MinimalNooter - If you're willing to use CWM Minimal Nooter is available and is easily one of the most customizable of all the Nooters with different packages ranging from the most basic of roots "Minimal" to a full root package with Gapps XorZone's Mods etc.
Advantages
Clear Instructions, lots of information, can be a little confusing/overwhelming.
More Customizable with multiple packages
Lowest chance of FS corruption due to CWM use
No One Day Market Wait
No extra Apps to fix Market Search
Disadvantages
More steps to get to root through using CWM (Not just pop it in wait and done)
TouchNooter - TouchNooter was the original Nooter for Nook Simple Touch using the original Methods used on it's sibling the Nook Color. It installs a few mods and the basics to make it as customizable as a person needs you can drop apps in or remove them without having any real technical know how.
Advantages
Customizable with most extra apps in /data/app
Lower chance of FS corruption due to new TouchNooter methods
No extra Apps to fix Market Search
Clear Instructions that go step by step through each requirement
Disadvantages
One Day Wait to get Market Working
I would use TorimuNooter, because theCPU underclocking saves the most battery power.
I'd be very curious to know why Gabrial originally included TorimuNooter but then edited his post to remove mention of it.
[NST]MinimalTouch 1.1beta5 (+Index to manual rooting)
http://forum.xda-developers.com/showthread.php?t=1346748
My favorite so far, easy install as long as you can follow directions.
Market works immediately, lightweight - only includes apps necessary for functionality and has had no problems since installing a few weeks ago.
Still waiting for XorZones NST launcher for my nook to be complete
Agrajag27 said:
I'd be very curious to know why Gabrial originally included TorimuNooter but then edited his post to remove mention of it.
Click to expand...
Click to collapse
After the update to 0.5 in which TorimuNooter is no longer really a derivative of TouchNooter, not even bothering to change bootloader images or disk names or a number of other things unique to TouchNooter, I feel that it no longer deserves to be recognized as it's own "Nooter"
GabrialDestruir said:
After the update to 0.5 in which TorimuNooter is no longer really a derivative of TouchNooter, not even bothering to change bootloader images or disk names or a number of other things unique to TouchNooter, I feel that it no longer deserves to be recognized as it's own "Nooter"
Click to expand...
Click to collapse
He's gonna freak about that...
*hides*
So do I take it that the "simple" act of rooting will drive my battery life down, possibly significantly?
Agrajag27 said:
So do I take it that the "simple" act of rooting will drive my battery life down, possibly significantly?
Click to expand...
Click to collapse
No.
Rooting just makes you gain root access, so you can modify your device.
It wont eat any battery just for rooting, but depends on what you do with your device, it will consume more or less battery.
On idle, except if some app is preventing your device to go to sleep, it should be the same.
If you read a lot of pdfs, play games, use web browsers, etc, the cpu will stay much more time active and there will be many more screen refreshes than when reading books.
Your battery will last less when doing more intensive tasks, the same when reading books, and the same when idle.
Just dont bloat it with trilions of apps you wont use, keep it minimal as more apps running, normally means more problems with battery.
If you wanted to lessen the cpu states, you could try SetCpu or follow this manual tuto http://forum.xda-developers.com/showpost.php?p=20069231&postcount=4 (I preffer this type of tricks, instead of installing extra apps).
Don't forget to never leave the wifi on for long periods of time, as it dosn't let the device go to sleep.
Agrajag27 said:
So do I take it that the "simple" act of rooting will drive my battery life down, possibly significantly?
Click to expand...
Click to collapse
No.
If you have too many applications running the background such as email and twitter and weather updates and etc. Your battery life will be significantly less than if you have just email running. Your battery life is directly affected by what you put on your device and by which settings you use.
My nook is rooted and without underclocking my battery life hasn't changed that much, if I leave wifi off I can go weeks before I ever need to recharge, if I leave Wifi on I can go maybe a few days to a week. Which isn't abnormal or extreme battery difference from root to non-rooted.
It's very much like your android phone, when you rooted it the battery life didn't actually change, if you install new roms, or different kernels you risk a difference between non-root and root. However the only real difference between root and non root on this device is your ability to install apps on the device and do things that require root such as directly modify the filesystem, or use root ADB.
If you don't overload your device with bloat and lots of apps that want to run in the background you won't notice a difference. If you decide to bloat your device up with a bunch of excess apps that like to stick around in the background you risk the chance your battery life will suffer.
Googie2149 said:
He's gonna freak about that...
*hides*
Click to expand...
Click to collapse
I'm a dev, I don't care if he freaks, it's my honest opinion. To me there's a fine line between derivatives and non derivatives, if he can't even bother to change the things that mark the image he used as TouchNooter than to me that is theft and nothing else, regardless of the changes or additions he makes to it.
I had read elsewhere that an app or two that got installed as a by-product of the rooting process was taking up CPU that wasn't there prior.
That was the concern. For me I'd think about adding passive e-mail support, another keyboard, possibly another reading app and would be likely to read more PDF's though now it appears I can get my newspaper (which is the primary goal) in epub format daily.
On WiFi, I haven't touched the default other than setting up access and it's been a good three weeks since I last charged and just re-charged it at 10%. I guess I could do better than that turning that off.
GabrialDestruir said:
I'm a dev, I don't care if he freaks, it's my honest opinion. To me there's a fine line between derivatives and non derivatives, if he can't even bother to change the things that mark the image he used as TouchNooter than to me that is theft and nothing else, regardless of the changes or additions he makes to it.
Click to expand...
Click to collapse
I understand that entirely, but Torimu will still be upset about it. He is kind of going around advertising his as the best nooter, and having it "insulted" (in his mind) will probably set him off. You know what, I should probably just leave this whole thing alone... :/
Agrajag27 said:
I had read elsewhere that an app or two that got installed as a by-product of the rooting process was taking up CPU that wasn't there prior.
That was the concern. For me I'd think about adding passive e-mail support, another keyboard, possibly another reading app and would be likely to read more PDF's though now it appears I can get my newspaper (which is the primary goal) in epub format daily.
On WiFi, I haven't touched the default other than setting up access and it's been a good three weeks since I last charged and just re-charged it at 10%. I guess I could do better than that turning that off.
Click to expand...
Click to collapse
Gapps does get added in with some other apps to make it more usable. Gmail runs in the background but with the right settings it isn't an issue. The launcher I believe could also run in the background with some settings (I believe there's an option in ADW so it doesn't close completely) but I pretty much find battery life between root and non root is pretty much negligible.
I forgot about the disk names...
But I will change that. I'm just trying to improve upon others work.
Thanks for your opinion Gabreil......
I'll try to stop advertising.
Torimu.Joji said:
I forgot about the disk names...
But I will change that. I'm just trying to improve upon others work.
Thanks for your opinion Gabreil......
I'll try to stop advertising.
Click to expand...
Click to collapse
It's more than just disk names there were other changes I made, big changes that would be rather noticeable if you bothered to test your work. Like for example the start up image which was left completely unchanged in both your most recent updates.
@Gabrial and the other nooters
While you're on the subject of images I just want to take the opportunity to emphasize the importance of you guys keeping your images within the size of the original NST boot partition.
Reason is, as said before, people regularly do the mistake of writing your image directly to the NST instead of writing it to the SD card.
Just this week I've had four cases where people have written "garbage" data outside the boundaries of the boot partition, and as you (should) know, the next one is the tiny /rom partition with the really important stuff.
Thank you
-Roger
ros87 said:
@Gabrial and the other nooters
While you're on the subject of images I just want to take the opportunity to emphasize the importance of you guys keeping your images within the size of the original NST boot partition.
Reason is, as said before, people regularly do the mistake of writing your image directly to the NST instead of writing it to the SD card.
Just this week I've had four cases where people have written "garbage" data outside the boundaries of the boot partition, and as you (should) know, the next one is the tiny /rom partition with the really important stuff.
Thank you
-Roger
Click to expand...
Click to collapse
I often keep this in mind. It's even addressed as one of my "Before you Begin" pieces. The problem is there's only so much you can do before it just falls to the user to pay attention and not screw up their device. When "You must have an external microSDCard reader or this will not work. Do NOT use the Nook Simple Touch." is apart of the "Before you Begin" and a user ignores that, then it's unfortunately their fault if or when they screw up their device by not following directions.
I've always limited my images to 128 because it's big enough for people to add what they want or to expand Nooter as needed. I'll actually be switching over to the CWM method which would be safer but you're stuck with the same issues with CWM that you will see with using TouchNooter's current image based method and that is people not following instructions and screwing up their devices.
While limiting images and such to 70MB (I think that's right) would be ideal the issue is the majority of that space is already filled, meaning you're very much limiting what you can do with an "automatic" method.
Mind you I've heard of methods like noogie which is the exact size if I remember for the boot partition completely destroy a device because someone wasn't following the proper directions. So the issue isn't the size of the image but how the user uses them.
GabrialDestruir said:
Mind you I've heard of methods like noogie which is the exact size if I remember for the boot partition completely destroy a device because someone wasn't following the proper directions. So the issue isn't the size of the image but how the user uses them.
Click to expand...
Click to collapse
True, but my experience is, and I get around three to four cases every week, is that they write it to the root device which means that 76MB (or 155648 sectors to be exact) is ok.
Beyond that you go into the next partition and the data there is only a couple of hundred kilobytes.
So you see, just 300KB beyond the size of /boot is enough to completely brick a NST forever :/
Yes, there's a backup zip in p3 (factory) but it's usually fragmented and I have only once succeeded in recovering it..
Let me end with a 2012 version of a famous (mis)quote:
"155648 sectors ought to be enough for anybody"
-Roger
ros87 said:
Let me end with a 2012 version of a famous (mis)quote:
"155648 sectors ought to be enough for anybody"
-Roger
Click to expand...
Click to collapse
I wish that were true, lol, but considering how much information we want to put on the device it's hard. Perhaps if CWM could grab zip files off of the internal media storage you could toss CWM on 155648 sectors then keep all update zips, etc on the internal storage partition
So i just squires an NST and already have a Fire and Sensation for most of my needs, i really only want to use this as a reader, but the restrictions blow. i really only care about fixing this partition silliness. Which is the best way for just getting that space available.
We noobs, for good reason, are encouraged to search the forums for answers. The conversations between high level users, though, can sometimes be hard to follow. This glossary should help. It is not a guide. I don't know enough yet to create a guide. It's only a glossary that offers a bit of guidance here and there.
To the noobs: any technical jargon used in a definition should be defined elsewhere in the glossary. To the experienced users: I am a noob writing for other noobs, so please feel free to correct any glaring errors. I would like to keep the definitions both functional and phrased generally in layman's terms. I know I have left out a lot of details, some intentionally, some through ignorance. Further discussion is welcomed.
Glossary
*228 - This is the number to dial from any Verizon phone to activate it. Option 1 activates the phone (linking it to your number and account). Option 2 updates the data roaming, which can evidently enhance your data connection if done from time to time. In certain situations, a dial pad may not be available during the activation call. As an alternative, you can dial *22890 to directly program your phone. Depending perhaps on where you live and which ROM you are using, you can dial *22891 to directly update your roaming. If that fails, you can try *22899 to update roaming, but some users report that this may be risky. Other alternatives include setting up a speed dial as *228,,,,1 or *228,,,,2. The phone reads the commas as two second pauses. Your phone will dial *228, wait for a bit, and then press 1 or 2 automatically.
3 Finger Salute - Using 3 fingers, you hold down the Volume Up, Volume Down, and Power buttons on the sides of your phone. This will boot you into your recovery program. It can also be used to reboot a frozen phone without pulling the battery. This will not work on all ROMs, particularly those using MTD. In fact, if you do it while on an ICS ROM, you will get to see what a bootloop looks like.
adb - Android Debug Bridge - This is a method to connect your home computer to your phone. Generally speaking, it requires properly installed Samsung drivers and the use of the usb cable that came with your phone. People use adb for all sorts of things, including rooting and salvaging a messed up phone. You may see forum discussions where people discuss coding terminology in little grey boxes. These are generally adb commands.
example: adb push something.txt /sdcard/something.txt
AOKP - Android Open Kang Project - A play on the terms "kang" and "AOSP," this is part of a large multi-dev effort to bring the latest Android developments to a number of phones. For our purposes, it is currently under development as a Jelly Bean ROM that we can flash onto our phones. AOKP milestone 6, the final iteration of AOKP ICS, is still regarded as one of the most functional and stable ROMs available for the Fascinate.
AOSP - Android Open Source Project - This refers to the fact that Google shares its Android source code with the world, perhaps its main differentiation from Apple. Any software developer can work with this code. Functionally speaking, developers create AOSP ROMs for the Fascinate. AOSP ROMs could be considered the most pure version of Android, or Android "the way Google intended."
.apk - This is the file extension of ordinary apps and widgets used in Android. If you have the .apk file of a certain app, and you know what to do with it, you can run that app on your phone.
Example conversation:
Noob: I really like this new ROM, but I miss the Samsung Program Monitor widget.
Expert: Just copy the .apk from Nitsuj's stock ROM onto your SD card and install it using Root Explorer
Noob: What's Root Explorer?
Expert: *sigh*
Auto Reboot - This is a check box in Odin. It determines whether your phone will reboot itself after flashing a file in Odin. It doesn't really seem to matter a great deal whether or not it is checked. There seem to be a lot of opinions on this subject. Generally speaking, leaving the box unchecked will not cause any problems. Some problems have been reported in the situation of a failed flash of bootloaders when the box was checked.
Battery pull - Phones can become frozen in all sorts of awkward positions. They sometimes freeze on boot-up screens. They sometimes freeze on screens you won't even recognize. The traditional quick fix was to pull the battery out of the phone, give it a minute, put the battery back in, and then reboot. While this method often works, there is some evidence that it may be harsh on your sd card. The battery pull has essentially been replaced by the act of holding "Volume Up" and "Power" for a while (at least 5 seconds, maybe 10). Shutting down by holding these two buttons is widely regarded as safer than a battery pull.
BL - Bootloader - a.k.a. Boot Loader - This is the rudimentary software that kicks in when a phone is first powered up. Its only real goal is to get the operating system up and running. Some phones, like those from Motorola, have a "locked" bootloader, making it more difficult to use custom kernels. The Fascinate's bootloader was never locked. Here's where it gets complicated: bootloaders are broken down by Android version. There are Eclair bootloaders, Froyo bootloaders, and GB bootloaders. Just being on one version of Android, though, does not mean that you have the corresponding bootloader. It seems that stock Gingerbread phones don't use a Gingerbread bootloader. In fact, to put a GB bootloader on your phone (highly recommended for modern ROMs) you will need to flash a GB bootloader file.
BLN - Back Light Notification - This refers to a popular concept whereby the LED softkeys on the bottom of the phone will blink or light up as a means of notifying the user of missed calls, new texts, emails, etc. Most modern kernels are compatible with some form of BLN. Sometimes, an app will need to be installed from the Marketplace (Google Play) to actually control the settings. More and more, though, the settings can be controlled from within the ROM itself.
Bloat - a.k.a. Bloatware - This term describes all the software that Verizon installed on the phone, but would not allow you to uninstall. Bloat means different things to different people, but it's basically anything stuck on the phone that the user doesn't want. Opinions obviously vary. Common examples of bloat include the NFS Shift racing game, Vcast apps, and Bing.
BML - This is a technical term used by devs to describe the software organization in your phone as it relates to things called partitions. BML is the older, less flexible, and somewhat slower of the two organizational schemes currently available for our phone (MTD being the other). BML was long regarded as the more stable system. MTD ROMs, though, because of their performance benefits and available features, are now the gold standard. A stock Fascinate uses BML, as do several of the custom ROMs (GW, SC3, ,PWGB, TSM Res). Anything involving ICS or JB uses MTD.
Boot Loop - This happens when something goes wrong and does not allow your phone to boot properly. It will actually look like it is repeatedly attempting, but failing to boot up. There are numerous causes and numerous fixes. If you want to see what it looks like, you can do a 3 finger salute while on an ICS ROM.
Bootani - Boot animation. This is the image you see when your phone first boots up. The stock bootani is the Verizon logo. Developers tend to insert their own custom bootanis, and users often like to insert their own as a means of further customizing their phones.
Brick - a.k.a. Paperweight - The ultimate threat that keeps noobs from rooting, this is what people call a phone that does not work at all. It basically has the functionality of a brick or toy block. "Brick" is also used as verb, as in the act of turning your phone into a brick. There are several well established ways to brick phones. The one that noobs are most likely to encounter is the dreaded "Phone" button on Odin. Don't ever touch the phone button, EVER!
Cache - Common to many operating systems, Android included, this is a file where frequently accessed data is stored so as to perform overall performance. Wiping (i.e. clearing/emptying) the cache does not delete any user data, as the cache is rebuilt over time as the phone is used. Functionally speaking, many problems (poor performance, freezes, reboots) can be addressed by rebooting into recovery and wiping the cache and Dalvik cache.
Analogy: when you're reading a book, you could put it back in the bookshelf every time you get to a stopping point. However, it's much easier just to store it on your nightstand (your cache) for a while until you're finished reading it. That way you can access it much faster. If your wife/mom/maid comes and cleans off your nightstand, the book still exists, you just have to take the time to go get it out of the bookshelf again.
CM7 - CyanogenMod7 - This is an alternate version of Android 2.3 put together by a sharp group of developers who are involved in the Android Open Source Project. The CM7 ROM is perhaps most known for its ability to be customized by the user. The CyanogenMod team considers CM7 to essentially be finished, polished, and stable.
CM9 - CyanogenMod9 - This is CyanogenMod's version of ICS. Various releases have been available to the public for some time. Updates continue to be released. Many of the ICS ROMs on our phones carry bits and pieces of CM9. CyanogenMod's development attention has now shifted to CM10.
CM10 - CyanogenMod10 - CyanogenMod's version of JB, currently under rapid development. The various iterations are available as nightlies, which can be downloaded from CyanogenMod's website.
CNA - Codename Android - This is a ROM that, like many others, was available as ICS and is now available as a JB ROM.
CWM - ClockworkMod Recovery - This is an enhanced (understatement) alternative to the phone's normal recovery program. CWM is absolutely central to rooting. Most rooting guides will have you install some version of this program right away, for good reason.
CWM, once installed is accessed as follows:
1. Power down your phone.
2. Using 3 fingers, hold down Volume Up, Volume Down, and Power (see the guides for more specific directions).
Common uses of CWM include:
1. A complete data wipe of your phone (erases all apps, but not your ROM or kernel)
2. Wiping of the cache (often used before making major changes to your phone)
3. Wiping of the dalvik cache (also often used before making major changes to your phone)
4. Wiping battery stats. Some short battery life problems have more to do with your phone's interpretation of your battery than the charge of the battery itself. Wiping these stats can sometimes solve poor battery life issues.
5. Creating and using Nandroid backups.
6. Flashing custom ROMs and kernels (and other things). Users who are crazy about rooting and development will try several new ROMs and kernels in a single day. CWM makes it very easy to install these things and go back and forth.
There are two versions of CWM that most Fascinate users will deal with. There is the CWM 2.5 (CWM-recovery-ALL.tar) that is used for basic rooting or flashing ROMs that are closer to stock (SC3, GeeWiz, TSM Res). Then there is CWM 4 (CWM4_fixed_for_CM7-ODIN.tar) used for flashing MTD ROMs. There are some differences between the two, but they basically work the same way. See Droidstyle's guide for more details. Often, after successful installation of a ROM/kernel combo, one will find a new recovery installed on the phone. Not to worry, though, they all work in very much the same fashion.
Dalvik - This is what's known as a "Java virtual machine." It's the part of the software incorporated into all Android devices that actually runs the apps. It is named after a fishing village in Iceland, home to the ancestors of the developer who first designed the software. For our purposes, when problems occur with our phones, one of the first steps to try would be to reboot into the recovery program and use the available commands to wipe cache and Dalvik cache.
Debloated - This describes a phone that has had the Verizon bloatware removed. Debloating is one of the main motivations for rooting. It can make a phone run more smoothly by getting rid of a lot of things that run in the background. It's also just nice not having all of those useless icons clogging your app drawer. There are two common ways to debloat that most noobs will encounter:
1. Root your phone, install an app called Titanium Backup from the Android Marketplace (Google Play), and "Freeze" anything you consider bloat.
2. Root your phone and install a custom ROM. These ROMs basically come debloated from the developers.
Dev - Developer - These are the people who understand how to write and modify code in the android platform. They are the ones that make rooting fun and easy for the rest of us. They not only create fascinating developments (no pun intended), they package them up in neat little files that simpletons like us can download and install on our phones in a tidy fashion. It is always sad for the community when a recognized dev moves on to another phone. The Fascinate currently has a lot of devs working in a lot of different directions. It's a testament to the inherent potential of this phone.
Development Forum - This is the section of the xda Samsung Fascinate forums that is to reserved for actual development. In this section it is ok for noobs to READ, NOT TO POST. It is important to keep this section uncluttered to promote rapid and efficient exchange of information. It is not the forum in which to post your questions. Also, if you like a dev's work, etiquette dictates that you don't necessarily need to tell him in the Development Forums. You can simply hit the "Thanks" button. He will understand what you mean. The fact that some noobs may have posted in these forums does not serve as justification for other noobs doing the same.
Devil Kernel - This is a relatively new kernel on the Fascinate scene. There is a version for ICS, an alternative to the well-established IcyGlitch kernel, and there is a version for JB. It is the product of German developer DerTeufel1980, and it is undergoing rapid development.
Devil Recovery - As the name suggests, this is a recovery program (an alternative to CWM) from dev DerTeufel1980. Flashing his ROM or kernel will often give you his recovery.
DIDLE - Deep Idle - Some custom kernels can unlock this ability within your phone to dramatically reduce power consumption while idle. Predominantly, it works when the phone's screen is off, but some feature (e.g. a music player) is still running. Some tests by developers show impressive results for decreased battery drain while using DIDLE. Unfortunately for Fascinate users, it must be used with great care because it is well known to cause the Sleep of Death.
Dirty Flash - To properly install a ROM, one should always wipe all user data before doing so. This doesn't mean that the ROM won't flash if you refuse to do. To dirty flash, just clear cache and Dalvik cache and then flash your ROM in recovery.
Why would you do this? Because you're feeling lazy, and you don't want to have to restore your apps and settings.
Why shouldn't you do this? Because you'll have a lot of problems with your phone, call them bugs, blame it on the ROM, and then clog up the development forums with problems that no one else seems to be experiencing.
Download Mode - This is a setting in which you will put your phone when using Odin. There are other ways, but most noobs will reach download mode by powering down, removing the battery, and holding volume down while plugging the factory usb cord into the computer and phone. Odin can only communicate properly with your phone if the phone is in download mode.
Droidstyle's Guide - This is the holy gospel of noob rooting. It can be found in both the General section and Q&A section of xda's Samsung Fascinate forums. Noobs should read every page of the ensuing discussion. A noob with the ability to read and follow directions can be successfully rooted in a matter of minutes. Most of your silly questions that you want to post throughout xda have already been answered in this magnificent guide. Countless questions throughout all Android forums have been answered with nothing more than a link to this guide. If you follow Droidstyle's directions TO THE LETTER, you will be able to successfully do a lot of cool stuff with your phone without experiencing any of the monstrous rooting headaches you may have read about online.
Eclair - Android 2.1. Google likes to name its software releases after sweet foods. The Samsung Fascinate originally shipped with Eclair and hung onto it a really long time. It lacks so many features of later releases, though, that it is essentially a relic that won't come into play.
EH03 - This was the latest (and perhaps final) OTA firmware update from Verizon. Most normal non-rooted Fascinate users will be on the EH03 build number because Verizon basically pushed it out to our phones over the airwaves. It implies that your phone is using Android 2.3 and the EH03 radio. Previous builds shared the alpha-numeric naming system (eg dl09, dj05). Not all builds were officially released by Verizon. Some just sort of showed up on the devs' computers so they could tinker with them.
F. Reset Time - This is a check box in Odin. It's not clear that anyone knows the exact details of what it actually does, nor is it clear what will happen if you leave it unchecked vs checked. It seems to reset some arbitrary counter in your phone. As a general rule, you can either follow the instructions of whatever guide you're using or just leave the checkbox how you found it.
Fassy - a nickname for the Samsung Fascinate
Fast Charge - This is a feature on some ICS ROMs that can be turned on or off. When enabled, it allows your phone to draw as much charge as possible regardless of the charging source. Without fast charge, your phone will place artificial speed limits on charging when plugged, for example, into the USB slot on your computer. Fast charge bypasses these limits, letting your phone believe it is always plugged into a wall charger. It is worth noting that your phone will not be recognized by your computer as a USB device when fast charge is enabled. It will only charge.
FC - Force Close - This is when an app stops working unexpectedly. This can happen to both rooted and unrooted phones. It doesn't cause any damage to the phone. In most cases, the app can just be opened right back up. It seems to depend on a lot of factors, including the quality of the app itself. ROMs and kernels that experience very few FCs are said to be "stable."
Flash - This is a term used to describe the installation of software onto your phone. It refers to fundamental changes in your phone's operating system. It is different from just installing an app from the Marketplace (Google Play). Commonly, people will flash ROMs, kernels, patches, and radios. There are basically two ways to flash new software onto your phone:
1. Odin
2. CWM Recovery (or a comparable recovery program)
Freeze - There are two meanings in general use. One might use this term to refer to his or her phone becoming unresponsive. More commonly, though, it refers to a special ability of a program called Titanium Backup. This program can be downloaded from the Android Marketplace (Google Play), but it requires a rooted phone to work. When Titanium Backup is used to freeze an app or process, that app or process is essentially gone from the phone. It won't show up in the app drawer, and it won't be running in the background. The difference between freezing and uninstalling, though, is that anything frozen can be quickly "thawed," also with Titanium Backup. With the touch of a button, the missing app or process is right back where it used to be. This is a convenient way for newly rooted users to test the waters of debloating.
Froyo - Android 2.2. Google likes to name its software releases after sweet foods. In this case, they refer to frozen yogurt. Some custom ROMs are still based on 2.2. They are known for being extremely well developed and extremely stable.
Gapps - Google Apps - When flashing custom ROMs, the apps on the phone are usually deleted. As an alternative to going to the Marketplace (Google Play) and re-installing all the favorites (Google Maps, Google Talk, Google Voice, etc.), many devs have packaged these into a tidy zip file that can be flashed via CWM. Why don't they just put the Google Apps in the ROM, you ask? Custom ROMs and Google Apps get software updates at different rates, so keeping the two separate allows users to always have the most up-to-date version of each. On MTD ROMs such as CM7 or anything ICS, you generally must flash the gapps package to get the Android Marketplace (Google Play).
GB - Gingerbread - Android 2.3. Google likes to name its Android releases after sweet foods. Most of our stock phones are running on this release of Android. There are numerous ROMS and kernels based on Gingerbread. These are a good starting point for newly rooted users, as they will feel quite familiar.
Github - This is a web-based service where developers can post their code. Depending on the situation, their code can be accessed by other users, modified, or just shared with the world. The site encourages the kind of open source development for which Android is famous.
Governor - This refers to the type of logic your phone uses to control how fast its processor ramps up when needed or slows down when not. The choice of governor can influence overall performance and battery life. In the past, the governor could be selected using an OC/UV program such as Voltage Control or NS Tools. More and more, though, the governor controls are being integrated into the ROM/kernel combo, and can be found under 'Settings.' No one governor is right for everyone. The fun is in experimenting. Here are some (not all) examples and brief descriptions:
performance: Keeps the processor always ramped up to to maximum; useful for benchmarking
ondemand: Rapidly ramps up the processor when needed; gradually slows it down when not needed
conservative: Similar to ondemand, but ramps up more slowly
userspace: The user can define the parameters (for advanced users only).
lazy: This was developed specifically for Android by xda dev Ezekeel. He states it is an enhanced version of ondemand, tuned to our phones' capabilities. Don't be fooled by the name. He tested it with numerous processor-intensive applications.
interactive: Uses a logic to try to predict how quickly it needs to ramp up processor speed, attempting to balance battery life and performance
interactiveX: A tweak on interactive (by dev imoseyon), which locks the processor at the minimum speed when the screen is off
smartass & smartassV2: Modified interactive governors by dev erasmux, they use logic to determine how quickly to ramp up or slow down; designed to optimize battery life without sacrificing performance.
powersave: This keeps the processor always set at the minimum frequency. The name may be a bit misleading, as certain processes will just take longer, using up more battery.
Here's a more complete list from someone who knows a lot more than I do.
Gummy - This is a ROM based off of AOSP. Like many other collaborative dev projects, tt was formerly ICS and now JB.
GW - Geewiz - This is a three piece set of software put together by djp952. He has created a ROM, a kernel, and a custom Recovery (an alternative to CWM). All three can be used together, or each can be installed separately. This package of software is currently well respected for its smoothness and stability, as well as for its ongoing development. GeeWiz is widely considered to be an excellent choice for newly rooted users. The dev has recently released a media player ROM (i.e. no phone component) to get some life out of the old fassy through its Wi-Fi connection.
Heimdall - This program is similar to Odin. It was created by an Australian software company called Glass Echidna. It can be used to flash files onto your phone. Some users prefer this program over Odin. Heimdall can be used with Mac computers, whereas Odin can not. Many high level users regularly use both Heimdall and Odin.
Helly Bean - A Jelly Bean ROM from dev DerTeufel1980.
Hybrid - This describes a system where your phone begins to use some of the better features available in tablets, particularly when it comes to the use of available screen space. Basically, it makes a lot of stuff on your screen smaller so more can be shown on the screen at the same time. A ROM called ParanoidAndroid is currently considered the best iteration of hybrid mode, although other ROMs incorporate it to a certain extent.
ICS - Ice Cream Sandwich - Android 4.0. Google likes to name its Android releases after sweet foods. It comes pre-installed on the Samsung Galaxy Nexus from Verizon. Several developers have created ways to install ICS on the Samsung Fascinate.
Icy Glitch - This is a custom kernel created by a collaborative group of devs headed up by ssewk2x and Tk-Glitch. It is only for use with ICS ROMs such as AOKP and THS. It was extremely popular during the time when ICS was the bleeding edge. Many ROMs of that era were released with an optimized Glitch kernel pre-installed.
init.d - This is a type of script used by developers when they modify Android code. You hear the term a lot because modifications using this type of script have far-reaching effects in the overall performance of the phone. High level users (who aren't quite devs) can even insert bits and pieces of init.d scripts to make minor tweaks to their phones.
Inverted - By default, most Google apps consist of a white screen with dark lettering. Inverting changes this to a dark screen with light letters. There are several advantages to this. Beyond the aesthetic advantages, it tends to be easier on the eyes in low light situations and reduce battery consumption. Inversion is done by talented individuals called themers. For our purposes, groups like Team Baked often put out inverted GAPPS that we can flash instead of the regular ones. There are even 'blacked out' ROMs, where everything is dark.
I/O Scheduler - This refers to the type of logic your phone uses to order and process read and write requests to your phone's hard drive. There are several types, which are listed below, but there is no magic bullet. The joy is in finding the one that works for you in terms of performance and battery life. It is worth noting, though, that certain schedulers were designed to be used with mechanical rotating hard drives, taking the drive's rotational position into account. This does not apply to our phones, which use solid state drive technology. In older ROMs, a scheduler could be selected by using an OC/UV control program such as Voltage Control or NS Tools. In modern ROM/kernel combinations, the scheduler can be selected through the integrated settings. Specific descriptions are beyond the scope of this glossary, but simple Internet searches can expand on any of schedulers listed.
Examples: noop, deadline, cfq, bfq, sio, vr, bfs
* In the absence of a dev's recommendation, if you don't feel like reading up on the subject, you can leave the scheduler at the default or choose noop or sio.
JB - Jelly Bean - Android 4.1. Google likes to name its Android releases after sweet foods. This is the latest version of Android to hit the streets, and devs are flocking to it , making all JB development new and exciting. The development has reached a state where very stable ROMs are readily available.
Jig - This is a tiny Frankensteinian device made of a small chip, a transistor, and the tip of the little micro-USB connector that you plug into your phone to charge it or attach it to your computer. When your phone will not go into download mode through normal means, putting a jig into the phone when the battery is in will make your phone go into download mode. You can make one yourself or buy one online for less than $10.
Kang - Generally used as a verb, this means to take bits and pieces of someone else's coding and to then integrate it into your own. Granted, noobs won't be doing this, but devs do it all the time. For the most part, this is considered a welcome practice among friendly devs, provided it is done correctly and politely. Kanging often serves to better the community as a whole. The key for devs is to give credit to the other devs from whom they have kanged.
Kernel - This is one of the two main components (ROM being the other) of the software running on an Android phone. It is the piece of software that connects the hardware (screen, softkeys, vibration, speakers, etc.) to the other software components. An unrooted phone comes with a stock kernel. It is stable but somewhat slow. Practically speaking, installing (flashing) a custom kernel will make your phone feel much faster and smoother as it moves through screens and opens apps. Generally speaking, installing a new kernel will not change the basic appearance of your phone or erase any of your phone's information. Custom kernels can also unlock several abilities of rooted phones. Examples include:
-wireless tethering (ignoring that pesky $30/month charge from Verizon)
-control over how and when the softkeys at the bottom of the screen light up
-overclocking/undervolting
-voodoo lagfix (This only applies to phones with BML-based ROMs. MTD ROMs don't need lagfix.)
-custom boot animations
KGB - A custom kernel built by comradesven. This popular voodoo kernel is well known because of its many options for customization. It is also considered quite stable and fast. It is the everyday kernel of many rooted users. When installed, it comes with an app that allows a user to easily customize a number of features on the phone.
Lean Kernel - Created by imoseyon, this voodoo kernel is known for its simplicity and stability. He intentionally leaves out a lot of the "bells and whistles" to keep the experience simple, smooth, and fast. Imoseyon works with several phones, so it is imperative that you have the correct version of Lean Kernel, the one appropriate for your phone. It works with TouchWiz ROMs such as SC3 and TSM Res.
Linaro - This is a team of software engineers developing open source software for numerous platforms, particularly as it relates to getting maximum bang for the buck from systems with memory and hardware limitations. For our purposes, many Linaro modifications are making their way into our custom ROMs, promising increased speed and responsiveness.
Logcat - This is a log of all of the processing activity your phone did over a certain period of time. This is useful for bug reporting, as devs can examine logcats and attempt to determine the source of the error(s). Many threads in the development forum request logcats to go alongside any bug reports. A logcat can be generated through adb, and there are also some apps that will do it for you. Random complaints aren't terribly useful for devs, but logcats generally are. This classic cartoon illustrates how many devs feel about disorderly complaints about their work, even though most are far too polite to say anything.
{
"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"
}
Milestone - Devs are always trying to incorporate the latest and greatest features into their ROMs. The add-ons are incorporated as parts of new releases, or "builds." This is what makes development exciting, but it also leads to bugs. Milestone builds occur when the devs sit back, roll up their sleeves, and work the bugs out of all the awesome features they've crammed into their work. The milestones are considered the relatively safe and stable builds. When installed correctly, they rarely experience major bugs.
MIUI - This term is a transliteration of a Chinese name for a special customization of Android actually developed in China. MIUI ROMs can be installed on the Fascinate. They change the look and feel of the Android system, moving it closer to something resembling iOS, the iPhone's operating system. A lot of custom development has been done with the software code from the MIUI system. Many devs will integrate bits and pieces of MIUI into their own ROMs. For example, the TSM Resurrection ROM allows you to use the MIUI battery indicator, which looks completely different from the standard battery indicator.
MTD - This is a technical term used by devs to describe the software organization in your phone, as it relates to things called partitions. The bottom line is that the stock organizational system, called BML, is somewhat fixed and limited, whereas MTD offers devs a great deal of flexibility. Heavily customized ROMs like those from CyanogenMod or anything MIUI rely on MTD file organization. All of our ICS and JB ROMs use MTD. MTD ROMs, generally speaking, experience very little lag, as compared to BML ROMs. When returning to a normal BML ROM from an MTD ROM, special precautions need to be taken.
Nandroid - This is a backup of your entire phone as it stands at that moment in time (ROM, kernel, text messages, your Angry Birds progress, etc.). It is stored on your sd card, which is somewhat immune to your tinkering. A Nandroid backup is a good failsafe for the times when you might want to try out that new experimental kernel your favorite dev has been working on. The files can also be saved on a home computer/flash drive/etc. for safe keeping. Nandroid backups are created using a recovery program like Clockworkmod Recovery. CWM can also use old Nandroids to restore a phone to its previous condition.
Nightly - Nightlies - Some rooted users like the idea of having the most stable, tested, and reliable ROMs available. Others prefer the excitement of being on the cutting edge. Nightlies are the untested regular releases of whatever a certain dev happens to be working on at the time. They package them up, post them online, and let the discussions ensue. These are not for the faint of heart. They are for people who are comfortable addressing freezes, boot loops, and force closes. Having said that, the current nightlies from CM10 are actually quite stable.
Noob - If you have to ask what this means, this is what you are. It's a derivation of "newbie" or "newb," someone who's new to the activity at hand. In many ways, the noob is defined by his actions rather than by the amount of time he's spent rooting phones or posting on xda. Here are a few standard behaviors that will immediately brand someone as a noob:
-Posting new threads to ask questions that have been answered dozens of times. (Hint: It's best to search before posting)
-Posting ROM complaints (without logcat), beginner questions, and other non-development topics in the development forums (It has been theorized that this will ultimately be the end of xda)
-Diving in and flashing away without reading and then posting about your problems (Everyone needs to read the Guide.)
NSTools - This is an app that requires superuser permissions. It can be used to control a variety of the phone's features that are unlocked when running a custom kernel. It can enable fast charge, BLN, overclocking, and undervolting. It often comes pre-installed with ICS ROMs. Most JB ROMs have no use for it.
OC - Overclocking - Computer processors operate at a variety of speeds. When a manufacturer sells a product (like a phone) to the general public, they strictly limit the speed at which the built in processor can operate, even though the processor may be capable of more. This is to promote stability and reliability. Rooted users can overclock their phone's processor, raising the maximum speed at which it can operate. This can be done through various apps, including Voltage Control and NS Tools. Some ROMs even have the controls built into their settings. There are limits, though. Running a processor at too high a speed can cause overheating and/or glitches.
Odin - This is a program of seemingly mysterious origins that allows your home computer to communicate with your phone. You download it to your home computer. Good communication with your phone requires the installation of Samsung drivers on your computer as well as the use of the USB cable that came with your phone. Among other things, Odin can be used to root your phone, install CWM Recovery, install custom ROMs and kernels, and return your phone to stock after you've screwed it up.
*NEVER touch the "Phone" button on Odin. It should be labeled "Destroy your Phone"
OP - Original Post - This refers to the first post in any given thread, the one that started the thread in a discussion forum. A common noob mistake is to hop into a thread on page 27, read for 30 seconds, and then chime in with a question. He is often directed to the OP, which contains the answer to his question.
OTA - Over the Air - These are the official firmware upgrades that Verizon has released over the life of this phone. They were either pushed out to our phones in the middle of the night or offered up for us to download at our convenience. The latest one, EH03, came in December of 2011. Generally speaking, rooted users do not receive OTA updates. Also generally speaking, this doesn't really matter. The updates can be found on xda, and it is unlikely that the Fascinate will ever receive another OTA update.
Patch - This generally refers to a zip file that can be flashed using CWM. The file usually contains updates or small modifications to an existing ROM or kernel. A great example is the patch that reprograms the phone dialer's voicemail button to open Google Voice instead of the standard voicemail or Visual Voice Mail.
PDA Button - This is the button you will want to use when using the Odin program. You should always avoid the "Phone" button.
Pit file - This is a type of file used with Odin when returning your phone to stock. There is a "Pit" button on Odin you can push to enter the pit file you wish to use. An example of a pit file that you will probably use is Atlas_v2.2.pit. To return to stock, you would use a pit file along with a stock ROM, putting both into Odin at the same time. Droidstyle's guide provides detailed instructions.
Project Butter - This is a Google initiative, launched with Jelly Bean, aimed at reducing phone lag, both real and perceived. It involves research into human visual perception, the pairing of GPU and CPU, graphics buffering, and so on. It's purpose is to make your Android phone run "like buttah."
PWGB - Powerwashed Gingerbread - This is a custom ROM created by ccampos784 (with other credits given). Its name implies what it is, a cleaner version of Gingerbread. In its day, it was widely regarded as a well-debloated reliable ROM.
Radio - a.k.a. Modem - This generally refers to the software that manages the phone's connection to the outside world, not the physical device itself. Verizon would release new versions of this software from time to time in their OTA updates. The two most popular ones are currently EH03 (the latest) and EC09. Both of these work with Android 2.3 and the various Android 4.0 ROMs. The choice of radio can determine your 3g download speeds. It's difficult to say that one is better than another. Different users find good results with each one. Both radios are available as zip files that can be flashed in CWM.
Recovery - Your phone comes with a recovery program. You have to choose to boot it up as an alternative to booting up your phone's normal touchscreen interface. An ordinary phone user would probably never even see this program. It's not pretty. It's just functional. It is basically a list of commands and technical terms that you can navigate using the phone's softkeys, volume up & down buttons, and the power button (to select). *Note, the touchscreen is being used more and more in newer recovery programs* Essential to rooting are the special recovery programs such as CWM Recovery. A special recovery program, which is flashed via Odin, will replace the stock recovery program for a rooted user.
Re-Partition - This is one of the check boxes in Odin. This box should be checked only when returning your phone to stock. Of Odin's various check boxes, this is the only one for which widespread agreement of its use exists.
ROM - This is one of the two main components (kernel being the other) of the software running on an android phone. It generally determines the overall appearance of your phone, including which apps are installed by default. The ROM that comes installed on your phone right out of the box is known as the stock ROM. Created by devs, there are numerous custom ROMs available for the Fascinate. Popular Gingerbread ROMs a newly rooted user might try are Superclean3, PWGB, and GeeWiz. The current favorites of the Fascinate community are CM10, AOKP Jelly Bean, and ParanoidAndroid Jelly Bean. The process of flashing a custom ROM to your phone will, generally speaking, erase everything on your phone.
Root - When you buy your phone from Verizon, Verizon still controls it. You are simply a user who is allowed to perform various Verizon-approved activities on it. Gaining root access to your phone grants you the control that Verizon had previously held. Rooting quite literally makes you the "Superuser," opening numerous possibilities for improvement, customization, and ruin. Root access is essential to having a fast, fully customized phone.
Root Explorer - This is an app downloadable from the Android Marketplace (Google Play). As it requires Superuser permissions, it is only functional for rooted users. Its abilities far exceed those of standard file management apps. For example, Root Explorer can copy .apk files directly into the system/apps folder in Android. It's a great way to get that obscure Samsung widget reinstalled on your phone after your favorite developer's ROM washed it away and called it bloat.
Samsung Drivers - This is a small piece of downloadable software that will need to be installed on your home computer before it will be able to communicate with your phone (via Odin or adb).
SC3 - Superclean3 - This is a popular custom ROM created by Nitsuj17 (with other credits given). It has a lot of bloat removed, and it has several excellent additions. It also has a wide variety of readily available patches that allow users to further customize or reinstall things they miss about the stock ROM. It is known for being both fast and stable, and it is widely regarded as an excellent choice for newly rooted users interested in trying a custom ROM.
Skin - This is a program that a phone manufacturer creates with the goal of making its phones more user friendly. It is basically an interface that sits on top of the pure Android guts underneath, hence the term "skin." The skin that comes with Samsung phones is called TouchWiz. This is why our phones don't look quite the same as our friends' HTC or Motorola phones, even though they are all using Android. Some people love TouchWiz. Some people hate it. Some custom ROMs are designed to be used with TouchWiz. Others are designed to be rid of it.
SOD - Sleep of Death - This is when your phone goes into standby mode but then goes into a catatonic state somewhere between being asleep and completely powered down. Users report various degrees of SOD. Some ROMs and kernels have been associated with it, as have certain apps, certain radios, and certain SD cards. Experimenting with fringe OC/UV and didle settings are often responsible these days. Generally, a battery pull (or better, Volume Up + Power) will revive the phone. Once a phone experiences a SOD, it seems likely that it will happen again, so a fix will need to be instituted. A modification of OC/UV settings or a return to stock and clean installation of your ROM, kernel, and apps are recommended.
Superuser - A rooted phone will have a new icon in the list of apps called Superuser. This is what distinguishes a rooted phone from a non-rooted phone. There are numerous apps available on the web and Android Marketplace (Google Play) that require "Superuser permission" to do what they do. Common examples of these apps include NS Tools, Titanium Backup, Root Explorer, Voodoo Sound, NS Tools, and Voltage Control. When a rooted user first runs one of these special apps, the app will ask for Superuser permission. Since you are now the Superuser, you get to press the button that says allow or one that says deny.
S Voice - Korean Siri, courtesy of Samsung.
Swype Beta - One of the early perks of rooting, the latest version of Swype is not available to unrooted users because the Fascinate comes with a special pre-installed (and perhaps outdated) version of Swype. Upgrading gives a slicker version of Swype with a more advanced word selection logic. You must follow a few steps to do it correctly:
1. Change the input method to the Android keyboard (settings->language & keyboard).
2. Uninstall Swype using Titanium Backup.
3. Go to the Swype website, give them your email address, and then follow their lead.
*ICS and JB ROMs don't contain any traces of Swype, so steps 1 and 2 can be skipped for them
.tar - This is the file extension for the files that get flashed via Odin. The file to install CWM, for example, is a .tar file. Another example is the file that returns your phone back to stock.
TB - TiBu - Titanium Backup - This is an app available on the Android Marketplace (Google Play). It is for rooted users only, and it requires Superuser permissions to operate normally. Its two main functions are:
1. Creating backups of your phone (or parts of it) in case you screw it up
2. Freezing or uninstalling apps and other stuff you don't want (i.e. debloating)
Telus - This is a Canadian telecom company. They offer a Samsung Fascinate that is very similar the one from VZW. The Telus Fascinate only works on a GSM network, whereas the VZW Fascinate works on CDMA (GSM and CDMA are different wireless signal technologies). Kernels for the Telus Fascinate won't necessarily be interchangeable with those for the VZW Fascinate.
Thanks button - Once you have created an established account at xda and made a post or two, you will begin to see a button with a little thumbs up sign next to the word "Thanks." This can be found on the lower right corner of someone's post. Pushing this button lets the person who posted know that their work is appreciated. It is considered polite to thank anyone who has helped you, whether or not it was in direct response to your own question. It is always polite to thank the devs whose software you are using. Xda tallies these thanks and gives experienced users a quantifiable measure of their contributions to the community. You will see a thanks meter under other users' names. Helpful people and prolific devs can have hundreds or thousands of thanks.
THS - Team Hacksung - This is a group of developers whose mission is to bring all the best of the custom Android world to Samsung phones. For our purposes, they are currently working with the CyanogenMod code to bring JB to the Fascinate. As CM9 developed, THS worked to make sure it was available for our phones in the form of an easily flashed ROM. In reading about ICS ROMs, you will regularly come across references to THS Build 2. This is a very old version of THS, but it is critical to the installation of our ICS ROMs. THS Builds 1 and 2 contain code that preps our phone to run ICS ROMs. Therefore, if you are coming to ICS for the first time, it is recommended that you flash THS Build 1 or 2 (usually 2) and let your phone boot up one time. Droidstyle's guide will walk you through this process.
Troll - This describes a person who attempts to transform a civil forum discussion into a battle of harsh words. They generally lure people into a massive argument by posting inflammatory remarks that are just slightly off topic. They then sit back and laugh to themselves as the argument develops into the nerd equivalent of a bar fight. To feed a troll and make him stronger, just respond to him. To weaken him, report his posts to moderators.
TSM Resurrection - This is a custom ROM developed by TSM (teamsbrissenmod). Think of it as the "SC3 - The Director's Cut." While similar to SC3 on the surface, it has numerous additions that allow for customization.
TW - TouchWiz - see "Skin"
TWRP - TeamWin Recovery Project - This is an alternative to the traditional recovery program. Rather than using the volume rocker, softkeys, and power button to interact with it, a touchscreen interface is used. While it offers some interesting potential, it is still under development in terms of compatibility with the Fascinate and our popular ROM/kernel setups.
UV - Undervolting - This is a means of attempting to reduce battery consumption when using custom kernels. Rooted users can accomplish this through one of several apps, with Voltage Control and NS Tools being common examples. The point of whether UV reduces battery consumption is highly contentious, but there does seem to be a theoretical basis for its validity, as well as a preponderance of anecdotal evidence.
Voltage Control - This is an app available on the Android Marketplace (Google Play). It requires root access (i.e. Superuser permissions). When used with compatible kernels, it allows you to overclock and undervolt your phone. This would predominantly be used with Gingerbread-based ROMs.
Voodoo - Project Voodoo is a collaborative software development effort started by dev supercurio back when Galaxy S phones first hit the market. Its goal was to optimize the Galaxy S, bringing it up to its full potential. Voodoo innovations have been used by countless rooted users. Voodoo features can only be used on compatible custom kernels. The project consists of three main branches:
1. Voodoo Color - optimizes screen images/video *Not really available in most modern Fascinate setups, but people still talk about how they miss it.
2. Voodoo Lagfix - see below
3. Voodoo Sound - optimizes sound quality for audiophiles *The Voodoo Sound app is available from the Marketplace (Google Play) to control settings.
Voodoo Lagfix - For BML ROMs, there are basically two main types of kernels: Loodoo Lagfix and non Voodoo Lagfix. The stock kernel that comes with your phone is non Voodoo Lagfix. It uses a certain type of file organization that is considered extremely stable. It is also somewhat slow, evidenced by the lag many users have experienced on this phone from day one. Non Voodoo Lagfix kernels, slow and reliable, are the family sedans of kernels. The Voodoo Lagfix kernels are the sports cars. They organize file systems differently, allowing for reduced lag. To extend the metaphor, they are also more likely to be involved in crashes. Lacking the rock solid reliability of their non Voodoo counterparts, Lagfix kernels have a somewhat sordid reputation in older forum posts. Overwhelming evidence, though, seems to indicate that many of the later ones are quite stable. Many rooted users will tolerate the occasional force close or reboot to gain the speed benefits that Lagfix kernels provide. MTD based ROMs (CM7, MIUI, anything ICS or JB) use a completely different file organizational scheme, so they have no need for Lagfix.
Examples of kernels without Voodoo Lagfix: Stock, GeeWiz
Examples of Voodoo Lagfix kernels: KGB, Lean Kernel
*Note: Changing to a Voodoo Lagfix kernel or switching between Voodoo Lagfix kernels requires no special precautions. Changing from a Voodoo Lagfix kernel to a non Voodoo Lagfix kernel requires special precautions.
Wipe x3 - This term refers to the act of wiping the slate clean on your phone. It removes all apps you have installed and any data associated with those apps. It will not erase Android, your ROM, your kernel, or anything on your sd card (your photos and videos are on your sd card by default). The Wipe x3 is often done before making major changes to your phone's system. The process is accomplished through a recovery program such as CWM. Here are the 3 commands (hence the "x3"):
1. wipe data/factory reset
2. wipe cache partition
3. wipe dalvik cache
*Note, performing a wipe data/factory reset will reportedly wipe the cache partition and the dalvik cache, so steps 2 & 3 may be redundant.
zip - For our purposes, this refers to the file type for files that can be flashed with CWM or other recovery programs. For example, if you would like to install the Superclean3 ROM, you would need to download the zip file called sc3_milestone2_full and place it on your sd card.
I like how you split it up, to keep additions in alphabetical order. Nice job.
Sent from my SCH-I500 using xda premium
looking good sir! hopefully this gets stickied!!
droidstyle said:
looking good sir! hopefully this gets stickied!!
Click to expand...
Click to collapse
Your thread first, sensei.
Even better jawman!
Terminators run on Android
droidstyle said:
looking good sir! hopefully this gets stickied!!
Click to expand...
Click to collapse
jawman27 said:
Your thread first, sensei.
Click to expand...
Click to collapse
Both of your threads should be stickied - and droidstyle's thread should have been stickied long ago.
Terminators run on Android
skynet11 said:
Both of your threads should be stickied - and droidstyle's thread should have been stickied long ago.
Terminators run on Android
Click to expand...
Click to collapse
I think we have moderators mia
Sent from my SCH-I500 using xda premium
Sticky please
Sent from my SCH-I500 using xda premium
This is very clear and concise, thank you!
cotton42090 said:
This is very clear and concise, thank you!
Click to expand...
Click to collapse
You're quite welcome.
To everyone: I'm open to suggestions from noobs and senior members alike, so everyone should feel free to post any additions or changes they'd like to see.
Seeking advice from my more knowledgeable buddies...
Please check out the definition for bootloader, and let me know if it's ok. I've been doing a lot of research, but I keep bumping up against the fact that I'm still a noob.
Next, I think I'll tackle i/o schedulers and governors. I probably won't give specific differences in logic, but I might do something along the lines of -
conservative - defaults toward battery savings at the expense of performance
performance - running at max speed all the time (useful for benchmarking)
smartass, interactive, ondemand - all use a slightly different logic to determine when to speed up or slow down the processor, seeking balance between performance and battery consumption.
All input is definitely appreciated.
Did not see a bootloader definition
Sent from my SCH-I500 using xda premium
Alphabetized under 'BL'. I've kept it as a standard to alphabetize under initials used in forum posts, only because that's how the idea for this started for me....decoding of abbreviations.
I suppose this thing is big enough now that it's become more of a Ctrl+F glossary. I'll consider changing the alphabetization scheme if I hear feedback in that direction.
jawman27 said:
Alphabetized under 'BL'. I've kept it as a standard to alphabetize under initials used in forum posts, only because that's how the idea for this started for me....decoding of abbreviations.
I suppose this thing is big enough now that it's become more of a Ctrl+F glossary. I'll consider changing the alphabetization scheme if I hear feedback in that direction.
Click to expand...
Click to collapse
Looks good to me
Sent from my SCH-I500 using xda premium
Nice guide, certainly another good resource to point noobs to in order to expand their knowledge! Just noticed a couple minor things reading through it.
Bootloader - The locked bootloaders of Motorola phones doesn't so much make them harder to root (doesn't make it easier either), but it does mean that they cannot use custom kernels. Since a custom kernel is part of roms like CM7/9, it was very difficult and time-consuming for the developers to come up with a workaround, although it did finally happen in the form of 2nd-init.
Kernel - I don't think that saying you HAVE to flash a custom rom before you can use a custom kernel is entirely true. For example, you should be able to use KGB on stock Verizon EH03, unless I am mistaken. Obviously, any AOSP kernel requires a custom (AOSP) rom.
Recovery - Might want to clarify the differences between stock and the custom recoveries used for the fascinate (which ones are used for stock-ish TW roms, which are used for MTD). Also, using a custom recovery, you can navigate using the soft buttons, you don't have to use the volume and power keys (although you can if you wish).
SOD - I'm not sure which apps, radios, and SD cards have been associated with SOD issues? In my experience, it's been more kernel-related and can often (but not always) be avoided with the correct settings.
UV - There's some good info here regarding undervolting and other battery draining benchmarks. It's from the Nexus S forums, but their hardware is essentially exactly the same as ours.
Voodoo - You talk about lagfix, but don't mention voodoo sound or color. Also, the only "voodoo" implementation in icy glitch is voodoo sound.
Thanks. That is great info. I'll get to tweaking. I've actually been reading up on voodoo sound and color so as to modify the whole voodoo section.
[?]Let me run this by you guys to see if it sounds correct: Voodoo lagfix is only for BML based ROMs because of the nature of the file systems they use. MTD ROMs use a completely different (superior?) organizational scheme, eliminating the need for lagfix.
....learning as I go.
k_nivesout said:
SOD - I'm not sure which apps, radios, and SD cards have been associated with SOD issues? In my experience, it's been more kernel-related and can often (but not always) be avoided with the correct settings.
Click to expand...
Click to collapse
I based this on forum reports from various users describing how they got rid of frequent SODs. They weren't always Fascinate forums. The main app culprit that kept coming up was something called Youmail. The radio reports were just a couple of people saying that flashing a new radio helped. SD card formatting advice abounds, but mostly in older posts (ca. 2010). Another thing that came up a lot was the loss of a WiFi signal. I suppose that could be kernel-related, though. The SOD is not something I've ever experienced, so I'm hardly an authority.
It seemed in reading, though, that there is no one true SOD, but rather several variants. It also seemed that the cause wasn't always easily identified. Perhaps there is more current data debunking all of these old theories. Comments?
[redacted]
Some cool ideas there. A few comments (posted here because I don't see a way to leave feedback on the site):
1) I'd put the Charms bar on press-and-hold of a button, probably Search (which doesn't currently have any Hold action assigned). Double-tapping is an action that literally nothing else on the Windows Phone OS uses, and especially a button that is sometimes capacitive and sometimes physical (depending on phone model) it's not something I advocate adding now. I like the idea a lot, though, especially for its tie-in with Win8. One thing to add to the Charms bar though: as on Win8 (where it shows a bunch of status info when you open Charms), the Status Bar at the top of the screen should be always visible when showing Charms.
2) There's already a way to get to the task switcher; while it's OK to have multiple methods for achieving the same goal, it seems like there might be something more useful to do than duplicating functionality through a more round-about approach.
3) There should be a more visible cue about the notifications center. Either have something drop down from the top (perhaps a "you have <X> notifications" bar with an appbar-like pull indicator?) or add a button specifically for notifications (two-level Charms bar? Move it to the right edge of the screen? Not sure how best to handle that).
4) I know the whole "swipe down to close an app" thing is very commonly requested, and comes from WebOS, and vaguely resembles Win8, and... I still don't know if I want it. Closing an app is pretty close to literally never needed; backgrounded apps are not generally allowed to use any system resources (they may hold onto some RAM, but the system will take it from them if a foreground app needs it). Closing an app the "usual" way - by switching to it if needed, and then tapping Back until it goes away - also works, although it's more actions. My biggest concern would be that right now, it's not really possible to ever do the wrong thing on the task switcher view. Closing an app, though, is a destructive behavior - you lose the app's current state - and is something that would need to be carefully implemented to make sure it never happens by accident... or perhaps make it optional entirely.
5) The Xbox Music feature looks pretty good, although the drop-down switch between Albums/Songs/Artists/etc. might be a bit too... background. Also, the really basic problems of the new UI - things like songs getting duplicated when they exist both on the phone/SD card and on the "Music Cloud" - really need to be addressed. Highlighting the Search thing - I know you mentioned it earlier with global search, but it's good to have more focused search capabilities too - as the current lack of Search in the music app is a Problem.
6) "Windows and Windows Phone share the same store" is way, way more complex than anybody might be realizing. Leaving aside the fact that most Windows Store apps aren't written for the resolution or aspect ratio of Windows Phone and would therefore possibly look kind of crappy if they were usable at all, and the fact that app models of the two OSes are pretty different (for example, Windows Store apps are allowed to request filesystem access and are required to implement the Settings charm, while WP apps have neither of those things), the APIs are just different. WP8 can use a sort-of-subset of WinRT (the API for Win8 apps) but it's not the same thing (and Win8 can't run WP7 apps at all, not even close). Finally, there's the issue that even the most powerful WP8 are half as powerful as even the lowest-end WRT tablets, and that's going to make a lot of things that perform fine on things like Surface RT be unacceptably slow on a Lumia 920 and impossible to run on anything with lower specs.
7) IE11 is coming for sure. The sync feature would definitely be nice. I'd also like to see some version of (desktop) IE's feed reader (shared with desktop Outlook) get integrated into WP8.
8) Integration with photo services, in the same way as other parts of the phone are integrated with Facebook and LinkedIn and Twitter and so on... that is an excellent idea. Come to think of it, Facebook pictures are already integrated (a feature I never really use) so adding others should definitely be possible. It would be cool if apps could integrate that kind of stuff without explicit OS support, but that may be aiming too high.
Thanks for the good feedback!
Hmmm, concept by who?
that'd be me.
The sync of bookmarks from Desktop IE to WP IE has already been confirmed for a future version of WP. They didn't say which one exactlly so it might take until WP Blue.
I personally don't like the idea of having the icons in the settings - at least not at the end, just looks kinda weird. Perhaps it would work better if you put them in front and aligned them properly on a grid.
Camera settings actually return back to the defaults when you relaunch the Camera App (and didn't save your changes as defaults).
As for the charms bar - I like the idea of a universal sharing and search feature but I don't particularily like the implementation of it with the charms bar on Win8 and I really don't see it work well on WP.
I like it but MS always let's its users down and dismisses the best ideas and concepts. WP will go now where higher that where it currently is now because of MS's ignorance. The next 2 updates for Luminas that includes the Amber and the GR2 or whatever its called don't really bring much to WP at all; who cares about another clock on the screen or data sense? Or more camera tricks...? Really now!!
@sinister1: Does that post really help? Come on, there's no value in just being negative everywhere.
Also, you call Microsoft "ignorant", but I guarantee that they know far, far more about the smartphone market than you do. If you want to be persuasive, you need to come up with arguments that have more substance to them than effectively just calling MS names.
@KlausWidraw: I think I'm with StevieBallz on the suggestion to have the Settings icons be left-aligned; they do make the items easier to identify, but having a consistent horizontal position to look for them at would help. That said, the ability to re-order the options would be huge; I use some all the time (like Cellular, which is annoyingly just off the bottom of my screen) and others not at all (like "lock screen", "tap+send", or "theme") once I've set them up initially, and would like them out of the way to make room for the options that I care about.
GDR2/Amber as well as GDR1 before it and GDR3 after it are mere maintenance releases. No one expects an Update from Android 4.2.0 to 4.2.1 or 4.2.2 to bring major new functionality. No one expects updates from iOS 6.0 to 6.1 to bring major new features. Somehow everyone (contrary to all reporting on those topics) expects those maintenance releases in WP to do just that. Really new functionality will only arrive with WP8.1/Blue and this has been known pretty much since the WP Blue name first appeared in leaks.
GDRs mainly serve the purpose of fixing some bugs and enabling new hardware functionality that is required for device launches. It has been the same with WP7. There were updates like Tango that served to enable LTE. GDR2 now mainly serves to enable the new capabilities that Nokia required for their Lumia 925 and Eos Camera phones and to keep Google Mail usable. GDR1 was mainly bugfixes, GDR3 will enable new hardware like even higher resolution screens.
Amber then is bundled with the GDR2 update rollout but IS NOT a WP update. It is a device specific capability update like we have seen them by all OEMs in the past.
If there are two things I would change about WP (from a user perspective) those are:
1) A clock tile that updates real time, like the HTC one (srsly want one).
2) Battery saver profiles that let me choose what i want to remain active (bluetooth, wifi, mobile data, background tasks)
That's about it.
From a developer point of view, things are very, very different xD
GoodDayToDie said:
@sinister1: Does that post really help? Come on, there's no value in just being negative everywhere.
Also, you call Microsoft "ignorant", but I guarantee that they know far, far more about the smartphone market than you do. If you want to be persuasive, you need to come up with arguments that have more substance to them than effectively just calling MS names.
@KlausWidraw: I think I'm with StevieBallz on the suggestion to have the Settings icons be left-aligned; they do make the items easier to identify, but having a consistent horizontal position to look for them at would help. That said, the ability to re-order the options would be huge; I use some all the time (like Cellular, which is annoyingly just off the bottom of my screen) and others not at all (like "lock screen", "tap+send", or "theme") once I've set them up initially, and would like them out of the way to make room for the options that I care about.
Click to expand...
Click to collapse
Sorry for being so negative but this is really how I feel and what's wrong with that? I know that not everyone will agree with my views or me with views of others but my negative feed back is feed back just like positive feed back is also feed back. I'm pretty sure that you have your gripes with other things.
I'm just feed up that devs come up with some of the brightest ideas and MS simply ignores them. Tell me what is so hard for them to open the OS just a little more for people to be creative? Seriously? Now the truth is the best substance. And of course if you still don't agree with me that's okay; I won't hold it against you because those are your opinions and the way you feel. Please don't take any of my rants personal as all they are, my personal opinions.
sinister1 said:
I'm just feed up that devs come up with some of the brightest ideas and MS simply ignores them. Tell me what is so hard for them to open the OS just a little more for people to be creative? Seriously?
Click to expand...
Click to collapse
I have to agree with you on this one. There are some understandable things for security's sake, but its ridiculous how complicated it is to customize Windows Phone 8 or even WP7. With WP7, you could only have a static lockscreen (ignoring LockWidgets from WPH) and couldn't set a custom text notification sound (besides MS' and HTC's.) I could add a custom ringtone, but it was a pain to do, period. With WP8, its a tad easier. You can just copy and paste ringtones, lock screens are customizable, and alarm can be customized as well, as well as the battery percentage can be pinned to the lockscreen/start screen. But compared to the other 3 platforms (Andriod, iOS, and now discontinued Symbian) could virtually anything could be changed. I remember when the 7.8 Beta was out and there were swapped fonts in the roms. Its something that no one had even thought about modifying until it was an issue.
I do have to say the native apps ability is appreciated, but it seems that Interop is still an issue (except I have no idea how problematic it still is). I do have to say I don't know much of whats been going on, due to jumping ship getting Verizon's Trophy late in the game (like when I first signed up here) and then finally moved to WP8 with their 928. So I'm kinda in the dark as to what has been added from the GDR1, Nokia's supposed Amber update, whats in GDR2, future FM support, ect. I really just wish that MS would be a little more verbal about whats in WP8's updates. They were bad with WP7 and they aren't any better now.
Another feature that MS is completely missing is Xbox Video. Seems stupid for them to say their experience is coherent between all their devices when its clearly not.
Can u guys tell me ....which phones will get windows 8.1 update .????
Sent from my HTC Explorer A310e using xda app-developers app
Some people don't like customization.
Customization comes with the cost of performance. I had an android with "customization" and whenever i "customized it" it became really, really, really slow.
In order to even have customization working, the system has to waist a lot of CPU cycles on stuff like checking 1000000000000000 settings to figure out what it should render next, swap a gazillion artifacts from storage to memory etc etc.
I want my phone to do what I tell it to do. I don't give a damn about more customization than it already has, and so are 99% of all windows phone users, whom increase in numbers day by day.
If you are going to give feedback disguised as QQ, then you should head over to microsoft's site and make your voice actually count. You complaining here all day, on a freeking developer/hacker forums, will not help!
Windows 8.1 blue will probably loosen up the developers a bit, if they are going to implement all our suggestions. Which will come for all windows phone 8 phones.
@mcosmin: The conecpt the you trade performance for customization really isn't true. Yes, the phone could eke out a trivial amount of better performance by hardcoding its UI styles, but they don't do that. Things like accent colors, background colors, text styles, etc. are all stored in the registry; you don't have to modify a single line of system code to modify or create themes of your own, and they'll run just as fast. Other forms of customization, such as replacing some of the builtin libraries with custom ones, might be slower in certain circumstances, but only if the custom library either added new features (not just new customizations, but actual functionality that wasn't present before) or is simply very poorly coded. The first of those is a tradeoff, the second is easily fixed if people just share their source code.
@sinister1: It's not that I don't agree with you - I do, in fact, and frequently quite vociferously - I just don't see what value you're adding to this conversation by proclaiming it. This thread is to discuss mockups of UI changes to WP8, not to complain about OS lockdown in WP8 and Microsoft's apparent unwillingness to implement some requested changes.
GoodDayToDie said:
@mscosmin: The conecpt the you trade performance for customization really isn't true. Yes, the phone could eke out a trivial amount of better performance by hardcoding its UI styles, but they don't do that. Things like accent colors, background colors, text styles, etc. are all stored in the registry; you don't have to modify a single line of system code to modify or create themes of your own, and they'll run just as fast. Other forms of customization, such as replacing some of the builtin libraries with custom ones, might be slower in certain circumstances, but only if the custom library either added new features (not just new customizations, but actual functionality that wasn't present before) or is simply very poorly coded. The first of those is a tradeoff, the second is easily fixed if people just share their source code.
@sinister1: It's not that I don't agree with you - I do, in fact, and frequently quite vociferously - I just don't see what value you're adding to this conversation by proclaiming it. This thread is to discuss mockups of UI changes to WP8, not to complain about OS lockdown in WP8 and Microsoft's apparent unwillingness to implement some requested changes.
Click to expand...
Click to collapse
And how many people do you think will be able to do proper customization? Windows Phone shouldn't be Android with squares instead of rounded edge widgets.
And solid colors like the ones WP uses will always be faster than a image on the background, or some sort of gradients or whatever they they propose to have around the phone.
How many people will do "proper" customization? As many as want to. Who are you to say what is or is not "proper" for how I want my phone to look?
Of all the things wrong with Android (the battery drain due to background services not exiting automatically, the more stuttery UI on all but the highest-end phones due to poorer optimization, the ability for malicious apps to send premium SMS completely invisibly to the user, etc.) you choose to pick on the customizations? Nobody is suggesting that we want Android with WP-like tiles; in that case we would have bought Android phones and installed one of the several Metro-style home screen customizations. On the other hand, if I want a Windows Phone with "rounded edge widgets" and am willing to put in the effort to develop them, I see no reason I shouldn't be allowed to.
WP uses the graphics processor for its UI. Those "solid colors" are just textures like any other. A gradient, an image, a partially translucent image... they're all the same to the GPU. The performance cost would be unmeasurably small.
GoodDayToDie said:
How many people will do "proper" customization? As many as want to. Who are you to say what is or is not "proper" for how I want my phone to look?
Of all the things wrong with Android (the battery drain due to background services not exiting automatically, the more stuttery UI on all but the highest-end phones due to poorer optimization, the ability for malicious apps to send premium SMS completely invisibly to the user, etc.) you choose to pick on the customizations? Nobody is suggesting that we want Android with WP-like tiles; in that case we would have bought Android phones and installed one of the several Metro-style home screen customizations. On the other hand, if I want a Windows Phone with "rounded edge widgets" and am willing to put in the effort to develop them, I see no reason I shouldn't be allowed to.
WP uses the graphics processor for its UI. Those "solid colors" are just textures like any other. A gradient, an image, a partially translucent image... they're all the same to the GPU. The performance cost would be unmeasurably small.
Click to expand...
Click to collapse
It's not about the GPU.
It's about the CPU. The more complex the image is, the bigger the size, the more time wasted for CPU to process it.
Add to that the fact it needs to purge/load from memory several times a day (in the case of a background wallpaper for startscreen), and the performance loss and battery drain is suddenly no longer unmeasurably small.
You're talking about a difference of microseconds. Not milliseconds, microseconds. Several times a day. And telling me that this is *not* below the noise threshold of any measurement system we have today, never mind human perception?!?
Also, consider people who use apps (with their own tiles, not just system tiles that are mostly blank and therefore rendered as mostly a solid color) on their lock screen. You know, the whole "meet <person>" advertising campaign Microsoft has been running for this OS? Those app tiles take just as long for the CPU to decode and send the texture to the GPU as the customized tiles we're talking about here...
Except, customized tiles aren't even the point. If you don't want to customize your tiles because saving a few millionths of a second per day - a saving which will never amount to a whole second over your entire lifetime, much less that of the phone - you don't have to. The rest of us want features; customization is merely one of those features. It gets a lot of discussion because:
A) It's an obvious feature to have. MS advertises personalization. People like being able to change how things look, be it their clothing or their front yard or their Windows background. For some reason, though, they can't change their Windows Phone background.
B) It's really, really simple to implement. I mean, there are tons of third party apps, some rather sophisticated, to do this. Microsoft doesn't have to jump through the crazy hoops that we did, and they have the documentation on how the OS works as well.
c) It really does not affect performance. There's no cost. Look at the custom themes and custom system tray icons and so forth on WP7, and try telling me with a straight face the percentage by which it impacts performance to use them.
GoodDayToDie said:
You're talking about a difference of microseconds. Not milliseconds, microseconds. Several times a day. And telling me that this is *not* below the noise threshold of any measurement system we have today, never mind human perception?!?
Also, consider people who use apps (with their own tiles, not just system tiles that are mostly blank and therefore rendered as mostly a solid color) on their lock screen. You know, the whole "meet <person>" advertising campaign Microsoft has been running for this OS? Those app tiles take just as long for the CPU to decode and send the texture to the GPU as the customized tiles we're talking about here...
Except, customized tiles aren't even the point. If you don't want to customize your tiles because saving a few millionths of a second per day - a saving which will never amount to a whole second over your entire lifetime, much less that of the phone - you don't have to. The rest of us want features; customization is merely one of those features. It gets a lot of discussion because:
A) It's an obvious feature to have. MS advertises personalization. People like being able to change how things look, be it their clothing or their front yard or their Windows background. For some reason, though, they can't change their Windows Phone background.
B) It's really, really simple to implement. I mean, there are tons of third party apps, some rather sophisticated, to do this. Microsoft doesn't have to jump through the crazy hoops that we did, and they have the documentation on how the OS works as well.
c) It really does not affect performance. There's no cost. Look at the custom themes and custom system tray icons and so forth on WP7, and try telling me with a straight face the percentage by which it impacts performance to use them.
Click to expand...
Click to collapse
Don't compare the WP7 theme mods and stuff like that which were made by hackers that knew what they were doing.
If Microsoft allows this officially on the marketplace, it will be flooded by poor apps.
Anyway, we seem to not be talking about the same thing. We should let it rest.