Android thread V-garychencool finally rooted his phone and got ICS edition - Hardware & Software

[QUOTE=garrynohome;37773828]Yah it's not so bad. Could be worse. You could have an Desire C.[/QUOTE] I have it, it's not that bad I mean it is bad but not wildfire level of bad

[QUOTE=garrynohome;37773828]Yah it's not so bad. Could be worse. You could have an HTC Wildfire or Desire C.[/QUOTE] So the HTC Wildfire is the prime model for a really bad Android phone. Okay.

so right now I have no phone at all but next Friday I will be the owner of an HTC Raider/Vivid/Velocity/Holiday. (Name soup, yay. I think I'll just refer to it as a Vivid, since that's the US name and the name XDA uses)

I've heard so many people complain about HTC devices. Do they make them shit?

[QUOTE=ShaunOfTheLive;37774094]so right now I have no phone at all but next Friday I will be the owner of an HTC Raider/Vivid/Velocity/Holiday.[/QUOTE] You'll be lucky to have so many phones!

[QUOTE=jaybuz;37774164]I've heard so many people complain about HTC devices. Do they make them shit?[/QUOTE] I think people just have a problem with Sense. I'm putting an AOSP ROM on mine.

[QUOTE=garrynohome;37773359]Verizon already released Jellybean for the Galaxy Nexus.[/QUOTE] They're only letting people update in waves. If you're chosen then you'll get an alert on your home screen, if not, you just have to sit and wait.

Alright, I got ICS flashed on my Bionic and it worked fine, but whenever I turn on my phone it boots into AP Fastboot and I have to go into the menu and select normal startup. Is there any way to disable AP fastboot from starting up when I turn on my phone?

[QUOTE=iCole;37773897]Yeah, S2 should get JB officially somewhere around November. If not, the Note has been confirmed a billion times already, and the HW is nearly identical so Note sources could be usable for all the ROMs.[/QUOTE] then why wouldn't they release a stable build of cm10 for the s2/s3 if it's confirmed and in a near future? Didn't read the article!!

Speaking of the S2. That's probably the best phone investment a lot of people have ever made. It still honestly holds its own against other phones today. I'm concerned about its future regarding updates. Most Android users do not flash their devices, and it'd be disappointing to see it get dropped at Jellybean because 18 months have gone by.

So guys Explain to a retard here: What is rooting? What is a custom ROM? Is stock Android the best Android? Thanks.

hey gary you're the screen expert is there a way to make my nexus 7 have better colors they're just so dull compared to my one x

[QUOTE=garrynohome;37774535]Speaking of the S2. That's probably the best phone investment a lot of people have ever made. It still honestly holds its own against other phones today. I'm concerned about its future regarding updates. Most Android users do not flash their devices, and it'd be disappointing to see it get dropped at Jellybean because 18 months have gone by.[/QUOTE] Aren't you the one who said the HTC Vivid/Raider was a shitty phone? It has exactly the same chipset as the S2.

[QUOTE=ShaunOfTheLive;37774752]Aren't you the one who said the HTC Vivid/Raider was a shitty phone? It has exactly the same chipset as the S2.[/QUOTE] No it doesn't. It has the same chipset as the crappy Qualcomm S2 which I told people not to buy when it launched. People on Canada's good network got the i9100M, a phone identical to the international one except for an M on the model number. [editline]23rd September 2012[/editline] [QUOTE=Ezhik;37774740]hey gary you're the screen expert is there a way to make my nexus 7 have better colors they're just so dull compared to my one x[/QUOTE] Probably not. If some kernel could do it someone would have done it by now. It'd need a fix from Google and Google has never demonstrated any care regarding calibrating displays on Nexus devices.

[QUOTE=iCole;37772573]apk's available here: [url]http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html#main_Archived_versions[/url] (search for "Android" if you don't want to scroll) I'm glad I uninstalled it, no more stupid flash ads.[/QUOTE] BRB, mirroring those for GB and up.

[QUOTE=garrynohome;37774756]No it doesn't. It has the same chipset as the crappy Qualcomm S2 which I told people not to buy when it launched. People on Canada's good network got the i9100M, a phone identical to the international one except for an M on the model number.[/QUOTE] Ah, you're talking about the Exynos version. Fair enough. I still think the Qualcomm Snapdragon S3 is a pretty good chipset.

[QUOTE=garrynohome;37774535]Speaking of the S2. That's probably the best phone investment a lot of people have ever made. It still honestly holds its own against other phones today. I'm concerned about its future regarding updates. Most Android users do not flash their devices, and it'd be disappointing to see it get dropped at Jellybean because 18 months have gone by.[/QUOTE] yea, im so happy i bought this phone its a great investment and its still very good compared to the new phones!

[QUOTE=Sgt. Jerky;37772745]Cool, the Galaxy Nexus has an incredible amount of custom ROMs available. It really depends on what kind of experience you're looking for - though almost all of the available ROMs are Jelly Bean based by now. Here's a listing of a bunch of them: [URL]http://rootzwiki.com/forum/362-vzw-galaxy-nexus-development/[/URL] For what it's worth, I use Bugless Beast which is probably a page or two in by now. It's fully based on the Google Source code with very, very minimal additions (a custom reboot menu and emoji's built into the mms application are about the only front facing additions you'll notice vs. a pure AOSP build). [URL]http://rootzwiki.com/topic/9621-romjbicsaosp-bugless-beast/[/URL] Other notables are obviously Cyanogenmod and AOKP. If you're interested in Cyanogenmod, CM10(jellybean) is still in preview builds so the ROM is built nightly. I have no idea how stable it is as I haven't used Cyanogenmod since the OG Droid days, so if you encounter problems be prepared to have to flash a new build daily until it gets resolved. That said, CM10 has far more customizations available if you're into that sort of thing. -CM10: [URL]http://rootzwiki.com/topic/32574-romofficial-cm10-nightlies/[/URL] I've never used AOKP and frankly, I haven't heard a lot about it outside of it coming with a ton of customization options out of the box. -AOKP: [URL]http://rootzwiki.com/topic/32152-romjbpure-aokp-unofficial-nightlies/[/URL] I'd honestly recommend starting with Bugless Beast if you're new to flashing new ROMs. It'll give you the full Jellybean experience, and see how your phone reacts to the OS. If everything runs smoothly that'll be a good gauge as to how well the other ROMs might perform. The instructions for how to flash the ROMs are pretty much standard: - Download the .zip package from the thread - For beginners, rename the package as "update.zip" - Copy the zip to your phone's SD Card (MTP storage for the Galaxy Nexus) - Reboot into your custom recovery (For the Galaxy Nexus, power the phone off, then hold power+volume up and down to enter the bootloader, then use the volume up/down keys to select the recovery option and press the power button to confirm your selection) - In recovery, you're going to want to wipe data/factory reset, wipe cache partition, and wipe dalvik cache (dalvik cache option in the "advanced" section of Clockworkmod Recovery) - This step depends on what recovery you have installed (Clockworkmod vs TWRP), but for CWM go to "install zip from sd card > apply /sdcard/update.zip" if you renamed it in step 2 and put it on the sd card, otherwise you can browse for it by selecting the "choose zip from sdcard" option. - The install process should take care of the rest, wait until it finishes and reboot to make sure that the flash worked. As a note, the phone might take a REALLY long time to finish booting after you install a Jellybean ROM (Initially I think it can be upwards of 5-10 minutes). Don't panic - if this becomes an issue where rebooting takes forever you can try installing the updated vzw radios for the Galaxy Nexus. A lot of people reported that this fixes the slow boot times: [URL]http://wiki.rootzwiki.com/Samsung_Galaxy_Nexus_(toro)#Flash_Radio_Updates[/URL] ^These might be good to flash now before you start flashing ROMs, they'll work just fine with ICS and you don't have to do any system/data wiping to install them. Also keep in mind that for the VZW Galaxy Nexus the builds will often be referred to as "toro" which is just the codename for the Verizon version. Don't try and flash a build built for Maguro/Toroplus/Linaro - those are for different carriers. [B] EDIT: [/B]jesus that was an unnecessarily long-winded response.[/QUOTE] I'm now running Bugless Beast, thank you very much for that, I'd still be running in circles if it weren't for your help. The boot wasn't too long, it felt like the same time that my phone would boot up stock, so for now I'll leave it as is. Now when an update for Bugless Beast comes out, will I need to repeat this process again, or any type of ROM for that matter? Sometime I'll probably want to try out Cyanogen because its features look like they'd be nice to have.

[QUOTE=ShaunOfTheLive;37774885]Ah, you're talking about the Exynos version. Fair enough. I still think the Qualcomm Snapdragon S3 is a pretty good chipset.[/QUOTE] Well it's not. The Qualcomm GS II phones can't do basic scrolling or zooming without stutters that the Exynos version does fine. It's even more pronounced on HTC's 2011 phones which run what is basically the most resource intensive phone UI known to mankind.

[QUOTE=TippZ;37774482]then why wouldn't they release a stable build of cm10 for the s2/s3 if it's confirmed and in a near future? Didn't read the article!![/QUOTE] They could absolutely come up with some shitty excuse, don't underestimate OEMs when it comes to excuses. But S2 was repeatedly "left out" in official JB update lists from various Samsung branches. Some say it'll get JB, some don't, but still include the Note which is HW near-identical so [B]technically[/B] there would be no reason to leave it out. But as garrynohome said, the S2 is still extremely popular and still a pretty damn good phone, so it would be a real shame if Samsung just dropped official support for it because of a time frame.

HTC one X updates for unlocked phones rumoured for next month whereas phones with carriers are rumoured to be Christmas...

[QUOTE=Ninja Duck;37774944]I'm now running Bugless Beast, thank you very much for that, I'd still be running in circles if it weren't for your help. The boot wasn't too long, it felt like the same time that my phone would boot up stock, so for now I'll leave it as is. Now when an update for Bugless Beast comes out, will I need to repeat this process again, or any type of ROM for that matter? Sometime I'll probably want to try out Cyanogen because its features look like they'd be nice to have.[/QUOTE] Sounds good, glad you worked it all out. This is where trial and error really comes into play with custom ROMs. Normally when a ROM gets updated the developer will say if you need to wipe data/factory reset, wipe cache, and wipe dalvik or not. Sometimes you can get away with a "dirty flash" and only wipe cache, then apply the new release right over the current install (ie just install the zip in recovery without wiping anything). The problem is that this can cause any number of instabilities or other permissions issues. General rule of thumb - try a dirty flash and if you experience any issues, do the full wiping procedure (data/factory reset, cache, and dalvik) and try again fresh. I personally always do a full wipe because I really only have ~8 apps to reinstall. If you have a lot of apps to restore, grabbing a copy of titanium backup/my backup root and making a backup before you flash a new release will save you a lot of headache as both apps include your apps's userdata in the backup. For what it's worth, Bugless Beast is on a much, much slower release cycle than other ROMs because Pete doesn't release a new build until there's new AOSP source to build from and/or he's fully, fully tested a new feature and knows that it is bulletproof. The nice thing is that once you have BB all setup and customized to your liking, you can make and save a nandroid backup that you can always revert to if it turns out a different ROM that you're testing isn't to your liking.

So ended up having to go with the Razr M. What are some apps I should pick up?

[QUOTE=iCole;37775202]They could absolutely come up with some shitty excuse, don't underestimate OEMs when it comes to excuses. But S2 was repeatedly "left out" in official JB update lists from various Samsung branches. Some say it'll get JB, some don't, but still include the Note which is HW near-identical so [B]technically[/B] there would be no reason to leave it out. But as garrynohome said, the S2 is still extremely popular and still a pretty damn good phone, so it would be a real shame if Samsung just dropped official support for it because of a time frame.[/QUOTE] [IMG]http://www.swedroid.se/wp-content/uploads/2012/09/galaxy-s3-jelly-bean.jpg[/IMG] [quote=swedroid]A large number of Swedish Galaxy S2 and S3 owners are probably waiting for the Android 4.1 Jellybean, at least those who are interested in Google's platform. Some time ago there flourished a rumor that Samsung would release Jellybean for S3 in conjunction with the unveiling of Galaxy Note II, but that was not the case. An update is of course at once and Samsung Sweden has now via its Facebook page announced that the flagship tentatively will be endowed with the latest version of Android in October or november. Last year's Galaxy S2 will get Jellybean in november on the schedule, but a timetable for Android 4.1 updates for other devices lacking at present.[/quote] [editline]23rd September 2012[/editline] google translated that

[QUOTE=Nsybouts;37775411]So ended up having to go with the Razr M. What are some apps I should pick up?[/QUOTE] Why didnt you take the nexus?

[QUOTE=jaybuz;37774164]I've heard so many people complain about HTC devices. Do they make them shit?[/QUOTE] 2011 models were basically all pretty meh. But the lower end models get a bad rep because people think that it's going to run like a GS2 or some shit. [editline]23rd September 2012[/editline] [QUOTE=garrynohome;37774963]Well it's not. The Qualcomm GS II phones can't do basic scrolling or zooming without stutters that the Exynos version does fine. It's even more pronounced on HTC's 2011 phones which run what is basically the most resource intensive phone UI known to mankind.[/QUOTE] The problem is that the Snapdragon S3 is basically the S2 with upgraded GPU and an extra core, clock speed and core increases can't do any better than equal an architecture change. [editline]23rd September 2012[/editline] Oh, and unless HTC is getting a Tegra 4 in their next flagship, which sounds like a horribly inefficient design, they should seriously go with Kraitv3 or quad core Kraitv2.

Thinking of going for a Nexus 7 so what cable will I need to connect a MicroSD to it? Amazon UK link would be very helpful.

a micro-usb connection with a sd-card adapter?

[QUOTE=Sir Whoopsalot;37776206]Thinking of going for a Nexus 7 so what cable will I need to connect a MicroSD to it? Amazon UK link would be very helpful.[/QUOTE] USB OTG cable. [editline]23rd September 2012[/editline] [url]http://www.amazon.co.uk/IVSO%C2%AE-Nexus-Tablet-Micro-Cable/dp/B008WOXUKI/ref=sr_1_3?ie=UTF8&qid=1348434487&sr=8-3[/url]

Samsung: 128GB Internal Storage [url]http://www.computerworld.com/s/article/9231440/Samsung_increases_smartphone_storage_capacity_to_128GB[/url] This is gunna be guud