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

[QUOTE=Van-man;38441748]Probably a stupid question, but did you remember to enable ADB_debugging_bridge on your phone?[/QUOTE] Not a stupid question at all, because I haven't An actual stupid question is how would I do that I'm useless :suicide: [editline]14th November 2012[/editline] If you mean USB debugging, I did that yeah

[QUOTE=FlashFireSix;38441510]Tried visionary, all it did was slow my phone down to a crawl until I managed to uninstall it Going to try unlock the bootloader but it's telling me to run the "SDK manager" in programfiles/android except there is no programfiles/android I found an SDK manager in the SDK tools bundle thing, but it doesn't open properly so confused :suicide:[/QUOTE] open cmd cd .. cd .. cd pro *press tab until program files 86*\a *press tab until android*\android-sdk type in whatever the tutorial tells you to do [editline]14th November 2012[/editline] im late

I have made many mistakes in my life I think filling up half my hard drive with random files and programs while I frantically try and root/unlock my Desire Z is one of the main ones

[QUOTE=Hunt3r.j2;38441425]No, it would. As it is, the One V runs a version of Sense 4 so stripped down that there isn't even a helicopter mode for the launcher. Tons of people on Nexus S forums and people I know that use the Nexus S report that JB is a pile of shit because of how much lag there is compared to ICS.[/QUOTE] So in order to justify not going from ICS to JB you're stuck admitting Jellybean is a complete and utter failure to bring Android even remotely close to how iOS and WP7 run on the same hardware, and that the claim it would bring the UI to 60fps was a lie. Also ICS was just as much of a pile of shit as JB on the Nexus S. I've used basically direct ROM ports to the i9000.

Jesus, I don't know what's up with your device. Make sure you've updated it to support HTCDev unlock, then go through fastboot and try again. [editline]13th November 2012[/editline] [QUOTE=Kaabii;38441877]So you're admitting Jellybean is a complete and utter failure to bring Android even remotely close to how iOS and WP7 run on the same hardware. Also ICS was just as much of a pile of shit as JB on the Nexus S. I've used basically direct ROM ports to the i9000.[/QUOTE] JB doesn't run well on older hardware, but really, with custom ROMs it's pretty doable to get acceptable performance with GB or ICS, with ICS being slightly slower than GB but not seriously so. I'm not dumb enough to say that Android runs as well as iOS and WP7, but it can get close enough that it doesn't matter.

[QUOTE=Hunt3r.j2;38441882]Jesus, I don't know what's up with your device. Make sure you've updated it to support HTCDev unlock, then go through fastboot and try again. [editline]13th November 2012[/editline] JB doesn't run well on older hardware, but really, with custom ROMs it's pretty doable to get acceptable performance with GB or ICS, with ICS being slightly slower than GB but not seriously so. I'm not dumb enough to say that Android runs as well as iOS and WP7, but it can get close enough that it doesn't matter.[/QUOTE] Yeah I checked it all, it's got the right software version, I've updated java runtime, HTC sync, and downloaded the SDK like 4 minutes ago so I have the latest version I've now forcefully installed ADB stuff for myself so I'll see if it'll work properly now

[QUOTE=Hunt3r.j2;38441882]Jesus, I don't know what's up with your device. Make sure you've updated it to support HTCDev unlock, then go through fastboot and try again. [editline]13th November 2012[/editline] JB doesn't run well on older hardware, but really, with custom ROMs it's pretty doable to get acceptable performance with GB or ICS, with ICS being slightly slower than GB but not seriously so. I'm not dumb enough to say that Android runs as well as iOS and WP7, but it can get close enough that it doesn't matter.[/QUOTE] It apparently does matter when devices need to be killed off after less than two years because Google refuses to make an OS that doesn't need the latest hardware to run acceptably. Where exactly is the justification that Jellybean, an OS incorrectly claimed to be an optimized ICS, runs significantly worse than ICS on certain devices.

surprisingly didn't work

[QUOTE=Kaabii;38441930]It apparently does matter when devices need to be killed off after less than two years because Google refuses to make an OS that doesn't need the latest hardware to run acceptably. Where exactly is the justification that Jellybean, an OS incorrectly claimed to be an optimized ICS, runs significantly worse than ICS on certain devices.[/QUOTE] The part where it's not actually any faster than ICS, just less perceptibly laggy at the cost of more RAM usage.

So uhh Might just Might just kill myself? probably be easier than rooting this phone

[QUOTE=FlashFireSix;38441977]So uhh Might just Might just kill myself? probably be easier than rooting this phone[/QUOTE] Your problem is that your device doesn't have a htcdev unlock supported hboot. Find the latest RUU for your device and flash the device with it, then try unlock again.

Peace out android thread, You're all awesome, and helpful people, I think it's just my sheer ineptitude when it comes to fiddling with android, I know I'd be a lot worse off without this thread to come to, I'm going to catch some sleep, night all. [editline]14th November 2012[/editline] [QUOTE=Hunt3r.j2;38442008]Your problem is that your device doesn't have a htcdev unlock supported hboot. Find the latest RUU for your device and flash the device with it, then try unlock again.[/QUOTE] I give up because I'll probably fuck that up aswell, it'll just sit in GB forever till I get a new device.

[QUOTE=Hunt3r.j2;38441976]The part where it's not actually any faster than ICS, just less perceptibly laggy at the cost of more RAM usage.[/QUOTE] So all that RAM is going toward hardware acceleration. Y'kno Google is pretty shortsighted if they keep building devices with hardware they know will be limiting because they refuse to write good code in a good language. Like, if you know the only way you're going to attempt to mask stutter is with a ton of RAM, start shipping your devices with a seemingly obscene amount of RAM.

Because apparently it [I]is[/I] supported, so I've just done something wrong, and I'm too tired to find out where

Does anyone know if Android is likely to become properly optimized for multi-core chips in the next couple major updates? Does that give Google less excuses to be lazy about keeping the N4 updated?

[QUOTE=FlashFireSix;38442035]Because apparently it [I]is[/I] supported, so I've just done something wrong, and I'm too tired to find out where[/QUOTE] Work on it tomorrow. That error happens because the bootloader doesn't recognize your command. [editline]13th November 2012[/editline] [QUOTE=Kaabii;38442030]So all that RAM is going toward hardware acceleration. Y'kno Google is pretty shortsighted if they keep building devices with hardware they know will be limiting because they refuse to write good code in a good language. Like, if you know the only way you're going to attempt to mask stutter is with a ton of RAM, start shipping your devices with a seemingly obscene amount of RAM.[/QUOTE] Google is short-sighted sure, but it basically boils down to support for multiple architectures. I really hope that they start using a translator that keeps the JIT compiled native code and then starts dynamic revision of that compiled code for further optimization based upon the architecture. [editline]13th November 2012[/editline] [QUOTE=mblunk;38442082]Does anyone know if Android is likely to become properly optimized for multi-core chips in the next couple major updates? Does that give Google less excuses to be lazy about keeping the N4 updated?[/QUOTE] It already is. Multi-core just inherently isn't as immediately useful as faster single cores. [editline]13th November 2012[/editline] And that's why Krait managed to be faster than T3 with just two CPUs.

Why bother supporting all these different architectures? It's a scenario of the issue being caused by the thing trying to eliminate it to an extent. The spec race only occurs because Android phones run so badly and people want faster hardware to minimize it. If it can be optimized to run very very well for a certain type of CPU like WP8 only using Snapdragon S4 chips then it's not going to matter that Samsung could put out a CPU that's a bit faster because nobody would notice. That's why people with the iPhone 4 really didn't give a fuck that the Galaxy S used the same CPU but 200MHz faster, because it ran like 200% slower.

A few questions. How can I put a toggle rotate button into the top bar (the one that you pull down)? Also, on the htc one s, if I press the back paneling around the bottom buttons, it makes an audible "click" sound. Is this an issue?

[QUOTE=Kaabii;38442315]Why bother supporting all these different architectures? It's a scenario of the issue being caused by the thing trying to eliminate it to an extent. The spec race only occurs because Android phones run so badly and people want faster hardware to minimize it. If it can be optimized to run very very well for a certain type of CPU like WP8 only using Snapdragon S4 chips then it's not going to matter that Samsung could put out a CPU that's a bit faster because nobody would notice. That's why people with the iPhone 4 really didn't give a fuck that the Galaxy S used the same CPU but 200MHz faster, because it ran like 200% slower.[/QUOTE] Because Android was meant to be universal. That's just a compromise that Google went with. iOS and WP8 went the other direction and every time they need to change resolutions or SoCs suddenly they need to do a whole new version number because otherwise it just won't run on the hardware.

[QUOTE=Hunt3r.j2;38442637]Because Android was meant to be universal. That's just a compromise that Google went with. iOS and WP8 went the other direction and every time they need to change resolutions or SoCs suddenly they need to do a whole new version number because otherwise it just won't run on the hardware.[/QUOTE] Not exactly. iOS does have apps made for a specific resolution, it's a big factor for why iOS has so much better tablet apps. Developers have to make a 1024x768 and a 2048x1536 app anyway, might as well put together a new UI. But they don't need a new version to put in a new resolution on iOS. The iPad 3 launched under iOS 5, released alongside iOS 5.1. They've also released devices using new or altered SoCs under the same version as well. It's just that their OS releases tend to occur alongside their new phones. With WPX, honestly the only reason I think they're not calling 7.8 WP8 with cutdown features like Apple does with iOS releases on older devices, is because 7.8 will still be Windows CE and 8 will be Windows NT. [editline]14th November 2012[/editline] So yah. I just don't feel the ability to be "universal" in a sense that manufacturers can throw in whatever SoC they want benefits the consumer. But Google made that compromise five years ago and it'd be impossible to change now.

Oh cool, my Nexus 7 got the 4.2 update. The two different pull-down menus are useful, though nothing else is too amazing.

I hate how G+ doesn't have proper multi uploading except for sharing a post. I want to upload a bunch of photos into an album Damn it!

[QUOTE=benjgvps;38443744]Oh cool, my Nexus 7 got the 4.2 update. The two different pull-down menus are useful, though nothing else is too amazing.[/QUOTE] 4.1.2? If so I cant find this second drop down :saddown:

[QUOTE=DPKiller;38443888]4.1.2? If so I cant find this second drop down :saddown:[/QUOTE] No, 4.2. 4.1.2 is no longer the latest version of Android.

Just checked for updates via stock rom. "No Updates found" Time for new ROM! [editline]fdkgn[/editline] Apparently I'm dumb for going to Settings->About->System Update and It says I'm up to date.

time for the most basic casual question ever i've been given a nexus 7 as a gift, i've purchased a bluetooth keyboard to use alongside it, and now i desire a case for the tablet itself. is there any particularly awesome case (within a reasonable price range, say 35USD maximum) that I should procure? Ideally, i'm looking for one that folds flat, has good protection, and possibly has the ability to form into a stand (not necessary, but it'd be nice so I don't need to use the huge included stand with my keyboard)

I can't for the life of me find a flashable CWM for my ATT Galaxy S2 (I-1777), I've looked everywhere but there's only one kernel that has it built in, problem is I was going to install a different kernel in CWM once I did flash it. Or wait can I just flash the kernel with CWM and then flash the one I want right afterwards? I don't want to fuck anything up. EDIT: Thanks for the help again Kingo!

[QUOTE=BrickInHead;38444724]time for the most basic casual question ever i've been given a nexus 7 as a gift, i've purchased a bluetooth keyboard to use alongside it, and now i desire a case for the tablet itself. is there any particularly awesome case (within a reasonable price range, say 35USD maximum) that I should procure? Ideally, i'm looking for one that folds flat, has good protection, and possibly has the ability to form into a stand (not necessary, but it'd be nice so I don't need to use the huge included stand with my keyboard)[/QUOTE] Why didn't you get [url=http://www.focalprice.com/CS0159B/PU_Protective_Case_with_Bluetooth_Silicone_Keyboard_for_Google.html?utm_source=CS&utm_medium=GM_US&utm_campaign=CS_GM_US_CS0159B&gclid=CPG3uaHczbMCFYuZ4AodIEUAaQ#.UKMrXoc82So]this?[/url]

for one, i've already purchased the keyboard, and two, that keyboard is much too small and the reviews i've read for it say it's got pretty shoddy build quality, ie, people receive theirs with keys missing and they get stuck on the leather really easily

Welp when in doubt Force Close, Clear Data, and reboot. Downloading 4.2 now :v: