Related
Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Neoprimal said:
Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Click to expand...
Click to collapse
I don't know how much direction pointing I can do but here goes..
Clockwork mod in my opinion is a necessity. Version 0.8 is the best one for most people because of how it deals with the memory locations. Yes, you can do things without it. The update process is as simple as putting an update.zip file, and a recovery folder with a command file in it on an sdcard and holding the vol + button while hitting power. It is easy. Clockwork has a lot of little features though that make life easier. You can make a complete system backup with it. You can install updates, and new firmware with it. You can completely lock up your tablet and using clockwork and your backup be back in business in about 3-4 minutes. You can load new roms and if you hate them you can go back to your old working stuff in minutes. Yes, there are ways to make one of these tablets work again when they get stuck. I don't think anyone has actually bricked one. Some may think they have, but I doubt it.
Unless you are dead set on wanting the stock TnT interface the easiest way to get what you want is to load one of the roms. Yes, there are ways to get most of it without loading a new rom. Most everyone that has gone the I have to stay stock but want all the mods has eventually just loaded a rom. TnT3.0 is based on the latest stock stuff. It has the market, flash, etc. already in it. VegaN is what I use mostly but they are both stable and fast.
Before you flash something brand new that just came out I would read about it and see what others have to say about issues. It usually only takes about 30 minutes until you can tell if it is going to be good or not.
All of the roms for this tablet have there own little quirks. The stock has gotten better with each update but it still is not as good as the ones I named.
Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard.
With a little bit of searching almost everything you may want it to do can be done. I really love mine, and when I got it almost 2 months ago I hated it...
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Neoprimal said:
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Click to expand...
Click to collapse
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
I can vouch for that. Erased system, boot, data and cache in preparation for a new ROM. Accidentally rebooted and couldn't get into recovery. Booted it into APX mode, flashed stock and was on my way.
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Sprdtyf350 said:
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Click to expand...
Click to collapse
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
hogasswild said:
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Click to expand...
Click to collapse
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
Thanks for the info Rothnic! I had already flashed it before I figured out it removed Clockwork. Learning new stuff every day is good... Thanks..
dragonfly1113 said:
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
Click to expand...
Click to collapse
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
hogasswild said:
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
Click to expand...
Click to collapse
Ok cool, thanks cant wait for my g tablet hopefully sat morning
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
hogasswild said:
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
Click to expand...
Click to collapse
my mom has an ipad and my dad could only buy it while i was on my honeymoon bc he knew i wouldnt approve of an apple device in the house haha.
rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
My device hasn't come yet (damn you FedEx!) but I'm eagerly awaiting it.
My plan:
Unbox, start it....do a factory reset from the getgo if it has enough juice.
Set it back up. Charge it to full. If whatever comes on it is as unbearable as I've seen in on Youtube - start modifications.
Will CWM install on it AFTER I do the update if it's available to me? I've seen that the update messes with it if it's already there - but noone's mentioned putting it on there after the fact. I may just go that route for simplicity sake.
Thanks for this!, and thank you all for chiming in with your experience. I feel much better about just getting my hands dirty in it all. I had wrote something to someone yesterday about jumping in and just doing it, but when it comes to dealing with it yourself it can be a daunting task - especially when it still has that new smell, lol. Anyway, thanks again. You guys really rock.
Will stop back later on after I've done my thing
I think they are both nice devices. There are trade off for both of them. I think the screen on the iPad is wonderful, where the gTab's is okay. But the gTab has a forward facing camera, you can print from it, and you can modify it fairly easily too.
Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
...famous last words...
Seriously though...trust the directions from the great devs like roebeet. Follow their instructions word for word. You can switch ROMs and then flash back if you want. No worries...
Off topic!
Well...disappointment! Fedex had my package out for delivery at 8am and at 8pm, they're not here. This is why I like UPS, they show up at my door on the day of delivery, no exceptions - they have shown up at almost 9pm before. The Archos 101 I got was sent out at 8am as well but got here at 1:30pm - I suppose that was before the holiday rush.
Checking the details of my tracking I'm seeing a "delivery exception" at 7:30pm (I guess it was time to get back to the facility so they can clock out by 8pm?) and upon calling them I get a somewhat stumbling but polite CS who tells me the delivery went out "late" - upon which I asked if 8am was considered late, especially from a distribution facility WITHIN the same zip code as I am, and all he could say was "Very sorry about this".
Aaaanyway....I guess it will be tomorrow before I can report my adventures.
Think I'll be able to get my $3.99 back from Amazon? I have Prime and with that the package would have come tomorrow anyway. Basically my $3.99 is wasted. Imagine if I didn't have Prime though? Whew.
ima_UNC_fan said:
...famous last words...
Click to expand...
Click to collapse
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
I finally got the G tablet tonight and...alright, don't flame me for this - but I don't see what all the complaints about the screen being horrendous or the device being molasses slow are about?
I don't know how people are trying to view it...but when looking at it or setting it on a stand to watch media, I'm not seeing any problem with the viewing angles. It's about the same as my laptop so I watch it the same way.
It's not even a 1/4 as slow as the stuff I've seen on Youtube or in some of the review videos I've seen around the net. I haven't gotten a single FC. Granted, I haven't put in a SD Card yet so maybe problems will start then?
I guess I should note, the very first thing I did was did a factory reset. Then I hooked it up to Wifi and got the 3053 update. I'm one of those who will be waiting for the 'official' update on the 24th.
I set up the time and date, restarted and everything works. I haven't installed flash yet (don't need it that much) and stuff that I DO want on there right now works fine (skype, pandora, fring, dropbox, evernote). I'm slowly figuring out a list of what I want/need from my Mytouch 4G to port to the VS GTab. Figure I don't really NEED Gtalk, Gmail on there because I have these on my phone AND PC - do I really want them making noises all around my home on 3 devices? I was concerned about getting the Google Apps on but now I'm finding I really don't need them. So it seems to me this will be a matter of learning to separate what I need on a tablet vs. my phone - I was of the mentality that I should just get whatever's on my phone on the tablet, this is something others apparently do as they seem to want everything that's on their phone, on their tablets as well.
I personally don't see the point in that. Had I had the Google Market, that would have escaped me as I'd have used Appbrain to just get my motherload of apps from the MT4G to the GTab. Not having it has slowed me, and now I get to re-evaluate before I do grab apps for it.
Now I just have to merge/convert my HTPC into a NAS device as well and find an app that will allow me to DLNA stream media from it and I'll be in mobile heaven.
I haven't had my wifi drop at all anywhere in my home and I've marched all over with it (I use full Wifi N, no G compat. so maybe my range is wider?). Tried email, etc. to replicate crashes and force closes but haven't so far. No surfing issues. I DID find that one app got 'stuck' being downloaded and I had to delete the file before the 'downloading' icon would go away, even after restart.
Maybe the trick to getting a workable GTab in the first place is to factory reset it before first use? Iunno. Things may change and issues may pop up the more I use it and as time passes - but so far, so good!
Again, I can't thank XDA enough for the advice and info. I've found and been given.
Sprdtyf350 said:
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
Click to expand...
Click to collapse
I figured it out. Accidentally hit one of the devkit nvflash .cabs and boom
I was one of the folks who got pushed the 20110509 build (came down this morning). Now, I have no dock at all. If I try to boot the machine with the dock attached, it stays stuck on the boot screen for minutes. If I boot without it and attach it, nothing happens for about a minute, then I get a battery icon with a question mark on it in the info window...that is it. It still is not registered with the system.
What...the...hell?
Were you rooted when you tried applying the new OTA ?
Negative. I've not rooted yet.
Sounds like you need to factory reset.
US version?
Yes, US version. Stuntdouble, is there no way to roll back an update? As in, reapply an older firmware file (20110423) that I have?
meatlocker said:
Yes, US version. Stuntdouble, is there no way to roll back an update? As in, reapply an older firmware file (20110423) that I have?
Click to expand...
Click to collapse
No I don't think so. Unless you root and re-flash with one of the roms from the dev section. Although now I've said that I'm not sure you can root from this new version yet.
Is it at least worth trying grabbing the correct downloadable firmware file from the Asus website and seeing if it will apply it ?
Yeah but only if a factory reset doesnt restore the unit to working with the dock first. I'm not a betting man but I reckon that will fix it.
Unfortunately, it didn't...I still have the same firmware (20110509) that I did before the wipe. I think the problem lies there, so I am going to need to figure out how to flash a prior firmware.
Thanks for the assistance thus far, guys.
I didnt expect it to wipe the firmware update but I did expect it to fix the connection problem. Good job I didnt bet. Anyways sorry you're having the problem. Probably a good idea to chat with those clever folks in the dev section to get it sorted though.
Thanks for the help. I was able to roll back the firmware of the device, but the dock issue remains. I am assuming that the dock itself has some kind of firmware, and that it is what got hosed.
Seams ro be plenty of people that are happy with the beta firmware. Try it one more time
Looks like the firmware push was a one-shot deal. I am not getting it offered to me again when I check for updates. As far as the dock goes, the power light is not even coming on when plugged in anymore. Friggin' weird.
meatlocker said:
Looks like the firmware push was a one-shot deal. I am not getting it offered to me again when I check for updates. As far as the dock goes, the power light is not even coming on when plugged in anymore. Friggin' weird.
Click to expand...
Click to collapse
Makes me scared to do the update that I requested from him. Looks like you were the one unlucky one of the batch according to the other dock update thread. Sucks!
This was a BETA firmware update so yeah once you download it it thats it.
Theres no real reason to discus it here any further, you need to contact the Asus dev thats been working with us on this and he'll work with you to get your dock working again. They did this beta release to make sure it worked before going with a full release. You signed up for a beta unverified release, that means there could be issues.
As you can see in the topics, most of us have had no issues. so just go talk to the asus dev and i'm sure he'll work with you to repair everything.
Already PM'd him. Will update with a response.
meatlocker said:
Already PM'd him. Will update with a response.
Click to expand...
Click to collapse
the fact he plugging it in has no light on sounds to me the dock is broken. factory reset wont help because that resets the tablet only. seem like a particular case here tho. i bet if you try a different dock itll work just fine. best of luck you find a fix soon.
mine installed the beta tablet firmware, then as soon as it booted it updated the dock firmware
did yours update the dock firmware on next reboot?
also... this may sound dumb, but does the dock have any battery life? Unplug your tablet from it, and plug the charger into it. See if the LED lights turn on...
No, it didn't. I got no notification at all about the dock getting updated (or needing to be updated). They were connected when I got the update, the unit restarted, and no more dock. If I try to restart with the dock in place, it just hangs on the second Asus boot logo. 2 seconds after I undock, I end up on the login screen.
I've spoken to Asus this morning, run through the normal wipe steps, and now waiting on a senior tech call. I doubt there is much that they can do, unless there is a magic key combo or other backdoor to refire the dock. It looks like I'm going to be RMA'ing back to NewEgg.
It's interesting that everyone else who has done this update has said that there is a 'part 2' to the update, which updates the dock. So the dock itself has firmware, this pretty much confirms.
There's an official T-Mobile update available as of this morning. It's over 40MB in size (pretty sure) so I'm imagining It's chock full of goodies.
I can't install it until I get home and defrost some bloat, so does anyone else wanna give it a shot?
I'll give it a shot. It says security and optimizations. DLing now.
EDIT: Looks like an update to Wifi calling.
EDIT2: New radio too: 11.59.3504.00_11.16.3504.20_2
Build: 1.55.531.3
Sent from my myTouch_4G_Slide using xda premium
yep, it's 43.2 MB, but definitely not ICS. will have to play with it to see if anything feels or looks different. i have attached the OTA package for anyone who'd like to have a look at it
http://dl.dropbox.com/u/18474790/OT....28.531.10_release_2279923pt850rhelkwzr8g.zip
Seems like the big weather widget is now missing the awesome graphics/animation?
Edit: also a BIG word of warning... Revolutionary is saying the new HBOOT is NOT supported at this time.
Does temp root still work?
jonnycat26 said:
Does temp root still work?
Click to expand...
Click to collapse
I don't think so, just tried it for the first time ever, but it didn't seem to work. Ran it twice but still don't have root access.
So I know this is gonna sound like a dumb question but please humor me. What would happen if I ran the update on my rooted phone? Would it brick the phone or just unroot it?
doost650 said:
So I know this is gonna sound like a dumb question but please humor me. What would happen if I ran the update on my rooted phone? Would it brick the phone or just unroot it?
Click to expand...
Click to collapse
Probably neither, it would more than likely just fail and you would just pull your battery out and reboot to where you are now.
Well I only rooted my phone to unlock it so if I wanted to install the update then I would have to unroot (which I already no how to do).
There was a bump in the kernel version.... but there's nothing in the release notes that would indicate what's changed there. They only mention netflix improvements, Google security fixes, WiFi calling improvements, and something else so minor I've forgotten it already.
doost650 said:
Well I only rooted my phone to unlock it so if I wanted to install the update then I would have to unroot (which I already no how to do).
Click to expand...
Click to collapse
Just wait a few days. Someone will float a rooted version out before too long.
Sent from my RubiX CubeD Extreme MT4GS using XDA App
and here's the info on the new HBOOT: version # is 1.45.0013. it says *locked* at the top, but it still says S-OFF. i accidentally still had a PC59IMG.zip on my sdcard, and it read it and asked if i wanted to update.....
yogi2010 said:
yep, it's 43.2 MB, but definitely not ICS. will have to play with it to see if anything feels or looks different. i have attached the OTA package for anyone who'd like to have a look at it
http://dl.dropbox.com/u/18474790/OT....28.531.10_release_2279923pt850rhelkwzr8g.zip
Click to expand...
Click to collapse
Looks like a lot of the stock ringtones are gone . I never rooted my phone..i only know they are gone becaise it put my ringtone as tmobile jingle. The one I use is gone.
Sent from my myTouch_4G_Slide using XDA App
Thanks for posting about this, and I really appreciate that the update has been provided so people can get it.
I am downloading the update now from yogi2010's dropbox - i'll see what I can find when I break it open after the download finishes.
I just woke up, so this gets to be the first item on my list.
If there is a new kernel provided, then don't expect to be able to open that up and scan for changes - but otherwise i'll see what I can find out and report back.
I updated my phone on friday night, and it was my first update ever. Is this the same one, or is it a newer version?
First impressions: wow, they made tiny changes to just about everything in the system.
I am going to focus first and foremost on the GPS changes they made - looks like they updated the SUPL certification, the GPS lib file - I need to find out what they did. They probably made it look like the GPS changes I made, but I never edited the SUPL certification file so expect an update to my GPS patch (probably) when I figure it all out.
I am also concerned about what they did with the bluetooth stuff - they updated the blacklist and also all of the Bluetooth files on the device.
If anyone applied the update, can you check and see if all of your bluetooth devices work?
I am half tempted to apply the update to one of my MT4GS phones, but I'm afraid of bricking it trying to go back after I sort through it all - writing the Radio is where you can brick your phone and that I would have to do ... so looks like i'll be figuring out how to decompile some of these update files and note the changes.
If anyone has any information to share about the update, please post it here.
Blue6IX said:
First impressions: wow, they made tiny changes to just about everything in the system.
I am going to focus first and foremost on the GPS changes they made - looks like they updated the SUPL certification, the GPS lib file - I need to find out what they did. They probably made it look like the GPS changes I made, but I never edited the SUPL certification file so expect an update to my GPS patch (probably) when I figure it all out.
I am also concerned about what they did with the bluetooth stuff - they updated the blacklist and also all of the Bluetooth files on the device.
If anyone applied the update, can you check and see if all of your bluetooth devices work?
I am half tempted to apply the update to one of my MT4GS phones, but I'm afraid of bricking it trying to go back after I sort through it all - writing the Radio is where you can brick your phone and that I would have to do ... so looks like i'll be figuring out how to decompile some of these update files and note the changes.
If anyone has any information to share about the update, please post it here.
Click to expand...
Click to collapse
the reason i was kind of a proponent of the first update was because there were changes to a LOT of things, even tho the size of the package was small. still, i myself don't know what was changed, if anything.
do you think the fact the HBOOT read the original PC59IMG.zip on my sdcard, and asked me to update, means that we can still go back to what we had before?
unfortunately no bluetooth devices here but will report back later about GPS.
yogi2010 said:
the reason i was kind of a proponent of the first update was because there were changes to a LOT of things, even tho the size of the package was small. still, i myself don't know what was changed, if anything.
do you think the fact the HBOOT read the original PC59IMG.zip on my sdcard, and asked me to update, means that we can still go back to what we had before?
unfortunately no bluetooth devices here but will report back later about GPS.
Click to expand...
Click to collapse
Probably - I may very well end up trying later but don't hold your breath. I might apply it to my phone that I bought with my plan so that I can take it back to T-Mo and force them to give me another one because their update broke it.
It kinda is special to me, being my first smartphone ever, so I don't want to part with it, but if I can't figure it all out i'm not so sentimental that i'll let that impede progress.
-also -
If anyone does flash this, some of the files that were removed with Undeadk9's security patch - and are also removed in my ROM, are put back onto the phone - most notably QXDM2SD.apk that I have seen thus far - this will have to be removed again if the update is flashed to prevent logging activities.
I have no idea what Smith.apk is - so decompiling and looking through that after I finish typing this out.
I'll keep people updated as I go through it.
can someone check if the CIQ stuff is still there or not?
i got a feeling...
Braccoz said:
can someone check if the CIQ stuff is still there or not?
i got a feeling...
Click to expand...
Click to collapse
I'm not sure yet about CIQ - but Smith.apk is absolutely a new logging utility.
It looks like it's primary function is to log battery stuff, but that doesn't look like it's all that it's logging - i'm looking into this and disappointed to see another attempt at spyware and intrusive logging being pushed onto our phones.
Please be advised that in addition to the .apk file mentioned above, Smith.apk is a logging utility that needs to be assessed and explored more in-depth. I am doing so now but others should as well if they can, maybe see something I miss.
Also looks like Smith.apk gives us a new dialer code - 76484 is the number but not sure what the preface is to get to it. Check my sig under 'guides index' to see the other dialer codes i've found so far.
If anyone has installed this update, can you experiment with the different ways of entering dialer codes to see about activating this number?
More to follow as I get through it all.
Thanks!
Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
I agree with you. At this point I'd be happy with some sort of update from Samsung/T-Mobile. Even if they just said "we're still working on it" and gave no ETA at least we'd know they hadn't forgotten about it.
If the Blaze Q whatever the hell they've decided to call it launches here in a few weeks with ICS and we still don't get the software I will be ticked.
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Sent from my Samsung Galaxy S Blaze.
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Sent from my SGH-T769 using xda app-developers app
dr4stic said:
Folks,
There's been no word, no dates given or leaked about the ICS update we're supposed to be receiving. Samsung has said we're supposed to get the update, but T-Mobile has been quiet. Hell, Samsung just announced that the GS2 will be getting JB and they've been working on it. I don't know how well that translates to the T-Mobile variant of the GS2, but it's still something. All we need is a kernel and some camera drivers. Hell, we could probably get away without the camera drivers and mangle the old ones using a compatibility HAL..
It is starting to feel like T-Mobile is simply going to forget the blaze. I mean, they released an update already, why would they hurry on to the next update...
I think if we're going to get something for nothing, we'll have to make noise about it. Same way we got this forum. I think it's going to take bugging t-mobile on the forums and on their support lines. You people on contract have it worse. You bought a really powerful phone in the presence of ICS, some of you after the promise that it would receive the update. T-Mobile wouldn't suffer penalties if they didn't push it, but I imagine they'll respond to some social pressure enough not to simply forget the update.
Hell, it'd be nice if we could even just get a date.
Click to expand...
Click to collapse
I completely agree with you. To be honest, I am already pissed off that they still havent released it. When I got this phone, T-Mobile promised I was going to get an ICS update in July. Yeah, so much for that. At the very least they could acknowledge our presence and let us know that they havent forgotten about us
Chitown021 said:
If push comes to shove and they don't release it can the devs port it or JB from another galaxy phone?
Correct me if I'm wrong but my understating is that it can but would take a lot of work and all are holding off since ICS is supposed to be dropping at anytime. No sense in going thru all that work only to have an official release dropped on us.
Click to expand...
Click to collapse
The problem is the kernel and libraries specific to our hardware. We have to have a working kernel and libraries before the rest of the rom can come.
I'm not sure why people thought the Blaze Q would've been a good thing for us because unless the hardware was identically similar (which no one had any proof that it was), the releases for that phone would've been useless for ours. The fact that it's now coming with a 720p display (I would've stayed with my Blaze 4G if it had that), and a keyboard tells me that there will be PLENTY different between the phones.
Hardware-wise, the T769 (Blaze) is EXTREMELY similar to the T989 (T-Mo SGS2). How similar you ask? In the original kernel configuration file for the T769, the options are set to build it as a T769 AND T989. There are a few ifdefs that exist purely to stop little snippets of the T989 code from taking effect.
I worked on my own time to try and hack together a kernel from the released sources for the T989 for ICS. Porting specific code from the T769 sources to try to come up with something that worked. Here's the problem: it was stressful and thankless, and at the end of it all I had a kernel that would compile and not boot. No one collected anything to help me attempt this and I was getting tired of having a non-functioning phone that pissed me off. So I ordered me a Galaxy Nexus. I received 2 in a row with screen issues and ended up returning them. I figured I would return to my efforts with the blaze, but at that point I was used to the big phone with a beautiful 720p resolution... so I shelled out the money for a GS3.
I have thought of returning and making a second attempt to port the kernel, and have actually started setting up to do just that. I think I made some mistakes my first time around, so the second time might actually work. But it is A PAIN.
chjema said:
Lol bugging xda mods for a forum is NOT the same a bugging T-Mobile for eta.
Click to expand...
Click to collapse
You're right, it isn't... but it's the last time I saw this community bug an outside source for something, aside from buying a couple of guys a phone
Yeah, a 720p screen would have been nice... thanks for the detailed explanation.
I still find it comical that my old HD2 is on the verge of having a fully functional JB rom but my brand new Blaze is still stuck on GB.
Honestly if I could've afforded it I would have probably gone the Nexus or S3 route but given my limited funds and needing to cover two phones (wife needed an upgrade) I thought this was the best value ($30 upgrade cost at Target).
Sent from my Samsung Galaxy S Blaze.
Yes lets please do this.
T-Mobile hasn't updated their page for a month now, and that was for the Gingerbread update they released when they could have been making headway on ICS. I can't find out how to submit any new pages, but I can see two requests for an update that were a couple months old (click on the link, then read on the right side in section "Incoming Links") source = http://support.t-mobile.com/docs/DOC-4182
I went to Samsung's page about ICS updates, and rated it "very dissatisfied," informing them they should have supplied target Year and Quarter (i.e. 2012 Q3) at the minimum, but preferably a specific month. source = http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00046726&fm_seq=49755
Let's continue to put pressure on these assholes, or they will sweep us under the bus while they pursue development of the Samsung Galaxy Supernova 4G Touchwiz Xtra 4.1.
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Dr4stic
If you need want help, testing, anything.let me know of beer more than happy to help.. we need to get ics to this phone
Sent from my SGH-T769 using xda app-developers app
heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem. I have ICS on a tablet and like it, but I never felt like I needed to light the torches and march on the castle because I didn't have the latest **** on my phone.
And honestly, if a delay of an update for a great phone that works perfectly fine is what keeps you up at night, just wow...
If I am missing something critical here that I should know about (phone will explode without ICS ROM installed, I have a higher risk of cancer if I don't have ICS on phone, etc) please let me know immediately. I have poster boards, Sharpies, and a willingness to assemble if needed.
Click to expand...
Click to collapse
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
I'll be the first to admit I've become a bit jaded because of my experiences with T-Mobile / Samsung and the Samsung Vibrant.
I heard promises about updates to that phone - they even set dates and pushed them back and back and back and finally... nothing.
If anything I think the release of the Blaze Q is a strike against us because our phones are now the "out dated" version of the Blaze and why put development hours into an "old" device.
I'm happy that I have a fully functional phone as it is now (the Vibrant never really had a fully working GPS). An update would be nice but I wouldn't lose any sleep over it because honestly, you may just be setting yourself up for a lot of sleepless nights.
Oh, and on the Vibrant Forum they started a twitter campaign #NeverAgain demanding the promised upgrade or they would never use T-mobile or Samsung again. No one listened.
I know this all sounds cynical but I've seen this show before.
Edit to add: If memory serves correctly this was also the case with the Behold on T-mobile.
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
L7ChrisL7 said:
Hey i know im new here, but i was wondering if you guys have only attempted to port ics roms from the SII? Ive tried to do the same and only recieved a glittery sparkly screen. I was wondering if anyone tried other devices with similar hardware like the HTC amaze 4g. I tried to port that one and actually got the boot animation to pop up. I havent tried to do any logcats or anything because i have been to busy and i need my phone for work, but if anyone else has tried to port from other devices i would like to know so i can know where to start if i do decide to try again.
Click to expand...
Click to collapse
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
heavenlydemonic said:
Not to be a **** ... but what's the rush? What's wrong with the software on your phone now? I've had this Blaze for a couple months and I don't think I ever had a problem.
Click to expand...
Click to collapse
What happens when more "cool new apps" are released to the market that require Android 4.0 API's or better? Chrome immediately comes to mind, and there are others with many more on the way. What happens 4 months from now when you are only 6 months into your 2 year contract and you're wondering why you can't realistically run things on your phone that has 1 gig of ram and a dual-core 1.5ghz cpu?
And honestly, btw... I had a myTouch 4G running CM7 that felt miles faster than my blaze. The samsung crapware is not only bloated, but breaks the system in a number of places. You can see this in the fact that you can't have a scrollable wallpaper, or that the system doesn't understand all the loop points in ringtones that work properly in other phones. I can't tell you how frustrated I get by an unlock and/or answer mechanism that can't track my fingers in real time like something as simple as CM7 does.
And don't get me started on the underutilisation of the video hardware.
AwesomeTurtle said:
Nope, just a league of people whining because that makes things happen faster. There really is nothing more to it.
Click to expand...
Click to collapse
No, this phone was released with a promise. When it was released, ICS had been out for 6 months or more, and I'm sure the OEMs had access to the system and API's well before the official release. By the time ICS is released for our phones (IF it is released for our phones), JB will have been out for several months.
This is a matter of support and broken promises. I am NOT just whining. I was sold a phone with a promise of ICS and it has NOT been delivered, and at this point the time has gone beyond reasonable.
If we don't make noise now, it WILL be forgotten and you're going to end up with a phone outdated well before it's time.
dr4stic said:
The reason you get a glittery screen when coming from roms that are like the SGS2 is because they use different display panel hardware than we do. I'd be careful porting things from different manufacturers unless you really know what you're doing. You'd hate to go and format some partitions you can't get back
Click to expand...
Click to collapse
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
L7ChrisL7 said:
Yeah the first time i tried to flash the rom nothing happened. ahah but then i went into the updater script changed some things and got it to flash. but since the hard ware is the same do you think i could use the display drivers from the amaze 4g and replace them in the SII rom and maybe it will work? well maybe i will have to do some logcats to see why the amaze rom isnt booting.
Click to expand...
Click to collapse
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
dr4stic said:
I doubt it. The drivers are baked into the kernel, they aren't modules or libraries. You'd have to get another compiled kernel working for our device, and you'll undoubtedly lose other drivers (camera, wifi come to mind). It's, of course, up to you to brick your own phone
Click to expand...
Click to collapse
Well cant you decompile a kernel? or maybe if i get the source of both devices i can use the code to compile a new kernel... hmmm all stuff to try. but compiling a kernel takes a while i think ill update my PC first haha. Im not necessarily worried about the other drivers not working, i just want to make progress, or at least help us make a push in the right direction. Im sorry if im being too optimistic or noobish, i just want to learn what people have and havent tried, so i dont waste my time on what has already been done.
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
here's a thread we can vent at!
spartanerik said:
http://support.t-mobile.com/community/phones_data_devices/android/blaze_4g?view=discussions
^--Post a thread in the T-mobile discussion forums! The most recent thread so far is asking for a status update, and if you guys can make more posts/threads about it, maybe we'll get a response from someone
Click to expand...
Click to collapse
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
anactoraaron said:
I already did - rather I saw a post and have decided to bump it daily so it remains at the top.
http://support.t-mobile.com/thread/31124?tstart=0
Create a support account and let's let them know they need to get this done!!!
Every post on the support forum discussing the ICS update will get a post (and bump) from me everyday!
Click to expand...
Click to collapse
http://support.t-mobile.com/people/tmo_erica
Try sending an email to [email protected] and ask (nicely) about a status update on the ICS update for our phone! I just sent one, and hopefully if we send enough we can get some traction
Hi there, I just got this tablet with its awesome screen a couple of days ago and as the title says I'm not sure if I should let the OTA run.
I already have a GS2 so I was aware of the eMMC bug and I also have an overly cautious nature so I said no to the updates and turned the auto check for updates feature off.
I got the P6810 version.
Currently it is on a ROM the firmware websites don't recognise:
2.6.36-P6810DTKL4-CL602212
I have no idea what version it will update to as if I ask it to check and agree to the disclaimers the download size is listed as less than a megabyte.
I have read quite a few of the threads here but none of them made things completely clear as to what to do in this situation. One of the posts said not to do a wipe with a Honeycomb based ROM which is what this is.
By the sounds of it we should get Jelly Bean in a month or so, well it is rumored and that would be great. I'm not sure I really need a rooted custom ROM but I definitely need to be off Honeycomb!
Thanks for your time.
I was having problems with my wi-fi connection and had to set it manually, I thought that perhaps the update might address that so I let it update.
It was 0.07Mb and has taken it to:
2.6.36-P6810DTKL5-CL604290
Now it says no updates available but the firmware sites say there are a few newer versions including an ICS based one. I guess I need to do that manually or via Kies, which I don't really trust.
I'll wait for advice from more knowledgeable people.
I would and have trusted Samsung Kies before for updates... not on this device, but on my Notes... and it did just fine...
good luck
jimmbomb said:
I would and have trusted Samsung Kies before for updates... not on this device, but on my Notes... and it did just fine...
good luck
Click to expand...
Click to collapse
Thanks for the reply Jimmbomb, I had a bit of a think about it and figured if it died I'd just be without it while it got fixed or replaced. Given I wasn't used to having it I probably wouldn't miss it so I gave Kies another try. This is unlike my phone which I need to work and, after it wiped and failed to restore my data and settings, I haven't updated my phone. I know I really should but once burnt twice shy.
I haven't used Kies for over a year, in that time it has improved significantly and actually did what it claimed to!
My initial reluctance to use it was based off my initial experience with it, it seems like Samsung have listened to feedback and fixed it up which is good news for us.
Now we just need to patiently wait for the JB release, hopefully it will be like the update for the GS2 and include the fancy features, smart stay being the one I expect will be most useful for a tablet.
I was wrong, Kies still has some problems.
I thought I'd plug my SGS2 in to see what would happen, it doesn't detect it although windows has no problems talking to it and letting me copy files via explorer.
I did the 'troubleshoot connection' procedure and all it does is reinstall the USB driver, since doing that neither device will connect to Kies!
Time to uninstall and try again I guess, SO frustrating given the size of company Samsung is.
Yep.
Samsung fraks it up on a number of fronts.
I think they need to learn that putting 5000 versions of devices on the market and then providing crappy support is an approach to business that leaves a bad impression.