yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] gigge:
Just some speed test

Just some speed test. Battery life is ok for me :)

This this including i did install all apps i wanted.

Facebook instagram skype ect.. cant find the Torch app. i love that app :(

Play Store updated lot of stuff. ~ 29 megs off stuff.

Phone call time over 1 h. i run my own business and use the phone often.

No missed calls or number cannot be reached. * finaly !!!

Very fast switch from 4g to 3g / 2g when calls are made and sound quality is ok.

Slower switch back to 4g after recived calls. but dont know if that is normal.

used the camera and gps a lot. just to try if all works ok !

I did connect phone to usb to flash new baseband that i have not tried before

Speed test are done walking on the way home. so 4g i really working this way.

Did speed test over 480 megs, this is why battery dropped quickly.

phones gets hot in 4g and heavy data transfers.

4g is acctually faster, phone is clocked to 1088 mhz max. @ 1,5 gz is is ~ 10 - 15 megs faster.

but so much over kill in speeds this days. higher speeds more battery drain.

Dont understand google music player. but managed a 45 min of mp3 music.

Overnight almost no drain :]

One speed test is 4g activated and the other one is 3g / H+

3g/H+ is fast enough for me anyway..

Next time i do full drain and no stupid speed test to drain battery.

Thanks everyone :cowboy:
[Android Q&A, Help & Troubleshooting] Nutterpc:
Well I just got back before from my partners brothers wedding

Beers $3, Wine 20c a glass. Lost count how many I had

But then again, I was the designated wedding photographer as well. Was still the most sober person there

Got about 380 photos to go through now, lol

Sleep time now tho!
[Android Q&A, Help & Troubleshooting] chrisross:
I've been using 20121010 and want to use 20130213 but everytime I try I get 'Installation aborted'. The log starts:

assert failed get prop ("ro.product.device") == "GT I9210T"... and ends with "E:Error in /sdcard/cm-10=2013-213..."

I've downloaded several times, always having to revert back to 20121010. I also have the same problem if I try the 1.8 Dreamkernel.

Should I try a factor reset?
[Android Q&A, Help & Troubleshooting] oc74ne:
remove from the updater script

assert(getprop(ro.product.model == skyrocket) || getprop(ro.product.device == skyrocket) || getprop(...... ));

so that

mount("ext4", "EMMC", "/dev/block/mmcblk0p24", "/system");

is the first line

Important: u should use a editor like notepad++ on windows (to keep unix linebreak characters) not wordpad or notepad because they are using windows linebreak characters wich the recovery can not handle
[Android Q&A, Help & Troubleshooting] marthell:
Thank you for this report, definitely going to try this on my i9210.

Tack ;)
[Android Q&A, Help & Troubleshooting] chrisross:
Many thanks. I'd seen script mentions before, but was a) a bit unsure about doing them, and b) thought they related to other probelems.

Are there any limits on Linux editors? KWrite/kate ok?

EDIT: OK I've made the change. Being totally thick, how do I replace the script file in the zip? I can drag the new script over but it will only put it in at the top level, not replace the existing version.
[Android Q&A, Help & Troubleshooting] oc74ne:
the way i do it in linux, is just simply open the .zip find the updater script, open it within the zip without extracting it (just double clicking) file opens up (in gedit in my case) remove the lines and hit save then archive manager asks if you would like to update the zip with the changes click yes and your done :)
[Android Q&A, Help & Troubleshooting] bwp85:
Just going back a bit. What exact CWM Recovery did you use? Not just version but which device. I have a theory.
[Android Q&A, Help & Troubleshooting] bwp85:
Thought you might find this interesting. This is with ICS Megamix 1.31. The softkeys work.

<4>[ 0.342742] [TKEY] tkey_device_init: 8901_lvs2 On

<4>[ 0.343261] [TKEY] tkey_device_init: TKEY_L12 3.3 V Set

<4>[ 1.334808] [TKEY] touchkey_init START

<4>[ 1.335754] [TKEY] touchkey_init F/W version: 0x7, Module version:0x3, HW_REV: 0xa

<4>[ 1.335845] [TKEY] melfas i2c_touchkey_probe

<3>[ 1.335845] OKGA [TKEY] melfas i2c_touchkey_probe

<4>[ 1.336578] [TKEY] enter touchkey_auto_calibration

<4>[ 1.387817] [TKEY] touchkey_init END

<4>[ 69.598052] [TKEY] tkey_vdd_enable: enter

<4>[ 69.598480] tkey_led_vdd_enable 0

<7>[ 69.601257] [TKEY] touchkey is not enabled.W

after *#*#86824#*#* it notes current firmware 0x7 suggests 0x9
[Android Q&A, Help & Troubleshooting] matust:
Can you post a link?
[Android Q&A, Help & Troubleshooting] bwp85:
I would but there is still an issue.

You can not make or receive phone calls. The phone freezes and you need to pull the battery out.

For this reason I do not recommend installing any ICS ROM.

If you would still like to try it I will find the link and post it. You will also need a touch version of CWM installed to flash any ICS ROM.
[Android Q&A, Help & Troubleshooting] sc0ttf:
This being the case, if the soft keys are resolved flashing this ICS rom, will the softkeys work back in our original firmware if we flash back to the stock afterwards?

Scott
[Android Q&A, Help & Troubleshooting] bwp85:
I can not be sure of this. I have no problem with my Softkeys in my OEM rom.

Here is the link if you want to give it a try:

http://xdaforums.com/showthread.php?t=1576924
[Android Q&A, Help & Troubleshooting] TimTams:
are your referring to the ICS I played with? That was on a friends Galaxy S, not the I9210, I haven't tried an ICS rom on the 9210 yet.

As for the CWM i used on my I9210 I had 5.0.2.6, which seems to be different to what other used, but what I was told to use in this thread describing how to root it: http://forums.overclockers.com.au/showthread.php?p=14233218

Anyway that worked until I to used CWM to make a backup, that was when the soft keys stopped working. Prior to that I had not made a backup as I just kept the stock ROM and rooted it.
[Android Q&A, Help & Troubleshooting] Qasha:
I fixed it :) :) :) :) :) :) :)

To all my fellow GT-I9210T buddies who have a wonderful phone in their hands but are missing 2 much needed soft buttons.... your painful wait is FINALLY over!!!

Finally a fix for our dreaded soft button issue - guaranteed to work (on my phone anyways)

I've managed to un-brick my GT-I9210T that lost its soft buttons (literally on the first day the phone came out!) during the 'infamous' CWM v5.0.2.6 root.

Let me show you how!!!

WARNING: do this at your own risk!

Assuming you've got CWM v5.0.2.6 on your I9210T and a most recent backup zip on your SD (doesn't have to be pre-superuser i.e. your first ever back-up)

1. Copy your back-up file from SD to your computer (just in case)

2. Install ICS Megamix 1.31 EXACTLY THE WAY IT TELLS YOU TO (MAKE SURE YOU INSTALL DARKSIDE SUPERWIPE)

Install ICS Megamix 1.31 - http://xdaforums.com/show....php?t=1576924

DARKSIDE SUPERWIPE - http://xdaforums.com/show....php?t=1477955

As you reboot, you will notice it (ICS) being unstable and unable to make calls.

3. Now press *#*#2663#*#* and confirm Phone's Touch is 0x9 and Part's Touch is 0x0. If this is so, now press Touch Key FW Update which will upgrade your Part's to 0x9

4. Reboot

5. Now laugh as you see your phone having a psychotic episode. Your soft buttons should be lit up and your screen should be wacky (like you're repeatedly and continuously pressing the soft menu button). NOTE: although your buttons are lit up now (brought tears to my eyes), they are not working yet but are close to working

6. Now, reboot into CWM v5.0.2.6

7. YOU MUST FOLLOW THIS TO A TEE (INCLUDING DARKSIDE ERASER):

* Wipe Data

* Wipe Data

* Wipe Cache

* Flash DARKSIDE SUPERWIPE

* Wipe Data

* Wipe Cache

* Flash Recent back-up (or whichever back-up you have chosen)

8. Log into your restored phone

9. If all worked well, your Part's FW should be 0x9 and your screen should be all funny like with the ICS (menu soft button repeatedly being pressed out of your control)

NOW THE TRICKY PART (took the longest to do)

10. Press the Pone button (as though you're trying to make a call), immediately press somewhere your screen, away from the number buttons and close to the black digit area, in order to stop the phone from entering that psychotic loop. As you are holding down on the screen with one finger, press *#*#2663#*#* and, if done right, you should enter into the Part's FW update screen, IF YOU'VE DONE IT RIGHT. Confirm your Touch is 0x7 and Part's Touch is 0x9 and then press the Touch Key FW Update which will downgrade your Part's to 0x7

11. Reboot (no need to remove battery)

12. Press *#*#2663#*#* and your Touch should be 0x7 and Part's Touch 0x7

13. Now smile and shed a tear or two and think of me

NOTE: I then rebooted into CWM v5.0.2.6 and did nothing but exit by rebooting. When my phone rebooted, my Part's Touch returned back to 0x0! All I had to do was press the Touch Key FW Update button and when done, rebooted. BUT when I power off the phone via CWM v5.0.2.6 and then turned it on normally, the buttons were there and working perfectly.

Regards,

Qasha
[Android Q&A, Help & Troubleshooting] bwp85:
I also used the one from the OCAU thread and had no issue. I'm now running 5.8.1.3 Touch and have no problem.

I think that the version of CWM has a lot to do with the problem.
[Android Q&A, Help & Troubleshooting] bwp85:
Did this step take long for you? I'm updating from 0xf to 0x9 and it's taking a long time. been going for 5 min.
[Android Q&A, Help & Troubleshooting] Qasha:
A few seconds actually.

Try to go back to the main screen and re-enter the firmware update screen.

Sorry to ask but did you follow the ICS instructions to a tee? (Flash ICS 2 times, wait 5 minutes before reboot etc.)

I'd suggest you reboot a few times and try again. If all else fails, re-flash ICS rom.
[Android Q&A, Help & Troubleshooting] bwp85:
Sorry I misunderstood what you were using the guide for. I thought it was to successfully install ICS. My soft keys work fine in my backup.

Also, mobile data network was not working in step 3. at home on wifi at the moment. Still want to continue on to second your result.
[Android Q&A, Help & Troubleshooting] Qasha:
I found a way to resurrect the soft buttons (0x7)

Sorry, my bad. My excitement got the best of me as I've been going crazy without my soft buttons.

Just to clarify, I've been able to recover my missing soft buttons and have tested it 2 times to make sure it works. So a note to everyone out there who have lost their soft buttons due to cwm brick..... If you want them back, follow my instructions (at your own risk) and you'll have them working again in no time!!!
[Android Q&A, Help & Troubleshooting] bwp85:
I have confidence in your method, I will try this tonight with a 3rd party GB rom if I get a chance.

Great work.

Regards,

Brian
[Android Q&A, Help & Troubleshooting] sc0ttf:
Hi guys,

I would just like to confirm this is working :D my softkeys are now finally working, im over the moon now i dont have to take my phone back :)

Thanks you so much Qasha :cool:
[Android Q&A, Help & Troubleshooting] roosta:
It seems like a very long winded and 'tingly' process to follow when a devo could step in, tell us whats actually happening through these steps and would probably be able to skip half of them, but if its working for a few now, its a step in the right direction.

Qasha, when you say 'Reboot' Do you mean manually turn off phone, or battery pull? I only want root access for a stock rom, no custom rom - can someone else test and see how well it works?

I dont know why WHICH version of CWM used would matter either in this guide or others, as i have only ever used the program download from the link the author who wrote the procedure in the first place.

RoOSTA
[Android Q&A, Help & Troubleshooting] bwp85:
I did exactly as robxau explained and had not one single issue. I'm with him in not understanding why it is so hard for some.

I'm sure the technical side of this will be worked out soon enough. Although the interim solution is long winded, it works and if you want root now rather than later, you now have a fix.
[Android Q&A, Help & Troubleshooting] bwp85:
Just found this on SamMobile

I9210TDVLD1 2.3.6 Gingerbread

New firmware :)

Probably only minor. Will check it out when it's downloaded.
[Android Q&A, Help & Troubleshooting] Qasha:
Great to hear the good news and to share your joy.

Qasha

---------- Post added at 03:25 PM ---------- Previous post was at 03:21 PM ----------

Thanks Brian,

It's the best I could do.

Qasha

---------- Post added at 03:41 PM ---------- Previous post was at 03:25 PM ----------

I totally agree with you. I'm more than willing to work with a developer on this, just PM me and we'll take it from there.

'Reboot' is all done either in CWM (reboot/restart phone) or when in ICS (step 2), holding down power button will display a 'reboot/restart' option. No battery removal was required. Sorry about that.

I mentioned my version of CWM just in case there were others out there who may have a different version of CWM and just in case this intricate fix was specific to that CWM (bad habit I picked up when I was a software tester)

Qasha

---------- Post added at 04:19 PM ---------- Previous post was at 03:41 PM ----------

I thought I should combine my 'boot.img' and 'recovery.img' together in a 'tar' container which should/will work in Odin (pda option). I haven't given it a go but I think (assumption only/please confirm) it should work and if so, will be a much much easier fix.

Am I right in saying theoretically it should fix the softkeys issue, add CWM while leaving your phone data untouched?

Please say yes :)

Qasha
[Android Q&A, Help & Troubleshooting] bwp85:
CWM and root done. No touch key problems at all. This is another option and an update as well ;)
[Android Q&A, Help & Troubleshooting] chrisross:
Thanks, that sounds good, but when I double-click the zip it says "Could not open the file, probably due to an unsupported file format". I don't think I've ever seen that message before. I can open it with Ark, and then open the script, but it's not editable.
[Android Q&A, Help & Troubleshooting] oc74ne:
what editing program are you using?

are you running the lastest recovery? as 20130213 should flash without editing it.
[Android Q&A, Help & Troubleshooting] chrisross:
Currently running 3.0.43Dreamkernel-GTI9210T-v1.6CM10_RC1+

CM 10-20121010

ClockworkMod 5.X.X.X ROM Manager v5.5.2.3

Not getting to the point of editing the file (unless I extract). Normally use KWrite but sometimes Vi. But if simply doubleclick the Zip it gives that error, so can't even get at the contents. I have Zip and Unzip installed, but if I point the file at these I just get the never-ending bouncing cog wheel.

Sorry to be going off-topic and showing my ignorance.

EDIT: something strange going on: just tried double-clicking the other zip files my i9210T folder and they all open fine - except for the two versions of CM, which both give the same error.
[Android Q&A, Help & Troubleshooting] oc74ne:
are you opening the zip with archive manager? i just used kwrite to open and edit the file saved and then archive manager prompted me for update the zip.
[Android Q&A, Help & Troubleshooting] Nutterpc:
Well Ive finally bitten the bullet

My new CM10.1 Kernel, is currently WIP

Theres a few special changes in place, so watch this space :)
[Android Q&A, Help & Troubleshooting] chrisross:
Yes, that's the only way I can currently open it.

Well Ark displays the files within and I can double-click the script to view its contents but there's no option to use an editor.
[Android Q&A, Help & Troubleshooting] chrisross:
OK well I've finally done it, but only after numerous attempts and got to edit the script through Xarchiver. Now running 20130213. But it hasn't restored my touch buttons (they disappeared again during one of my earlier aborted attempts at installing 20130213 and having to go back to 20121010) so will still have to work on that.

BTW, doing a recovery backup and it's reporting CWM v6.0.1.4.
[Android Q&A, Help & Troubleshooting] Tallustus:
AW: Galaxy S 2 GT -I9210T Development?

The easiest way to work arround that issue is installing a recovery made for your device .. And it should be up to date e.g. latest TWRP build wich works flawless and will install cm10/10.1 builds without any errors etc

Also for cam issue i will look t the logcat provided a bit earlier may we can find out something usefull :)
[Android Q&A, Help & Troubleshooting] chrisross:
Ah! Ok. That explains it. Unfortunately TWRP requires the use of Windows.

I've had to go back to the 20121010 version as the latest was flickering then though I added the latest gapps I was getting error messages about Google Play and other apps not working, so did a restore. I'm more concerned for now to get the soft keys back.
[Android Q&A, Help & Troubleshooting] Tallustus:
AW: Galaxy S 2 GT -I9210T Development?

Ok finaly it seems to be facebook app fault

qdmemalloc(231): ION_IOC_ALLOC failed with error - Out of memory
03-21 08:12:36.962 E

Seems to fill up memory till the device is out of memory

Possibly du lag of full support for 4.2.2 but i'm not sure right now cause i'm at work and just had a quick view over the log

Will further look at it when back home later

---------- Post added at 11:35 PM ---------- Previous post was at 11:32 PM ----------

No need for windows to flash your device there is heimdall avaible for linux wich works just perfect

Also just flash back a stock rom or propper dreamkernel and your keys should be back at life
[Android Q&A, Help & Troubleshooting] chrisross:
Had forgotten about Heimdall. Looked at it before but didn't get very far, but just now installed it for my distro (Mageia) and looks like it should be easy to use.

I had flashed the 1.8 DK after 20130213 which I'd hoped would cure the buttons (I posted on the Whirlpool forum that that's what worked for me with 20121010) but no joy this time. Will play with Heimdall tonight.

EDIT: quick try with Heimdall and the TWRP Recovery gives firmware.xml missing?
[Android Q&A, Help & Troubleshooting] Nutterpc:
Ok for all those interested

My kernel is now operational. Finally got the camera issue going *Curses & swears*

Im starting to add some of my touches to it now before I ask for people on IRC to try testing it for me
[Android Q&A, Help & Troubleshooting] oc74ne:
Did you update to cm10.1?

Let me know when you need testers I'll give it a run :)

Sent from my CM10.1 running machine of a GT-I9210T
[Android Q&A, Help & Troubleshooting] Nutterpc:
just currently trying to add some features to the kernel i want atm, will let you all know on irc
[Android Q&A, Help & Troubleshooting] Nutterpc:
New kernel is now ready

Just waiting a few hours to see how it goes before I hand out the links
[Android Q&A, Help & Troubleshooting] panther788:
Why is apollo version 1 in the pack instead of apollo version 1.1?
[Android Q&A, Help & Troubleshooting] Nutterpc:
That would be to do with kingbeatz, and I've seen that people have made azn aware of that on the thread in the skyrocket forums

He is going to work on it but did say he's gotten busy atm
[Android Q&A, Help & Troubleshooting] Nutterpc:
Btw oc74

I think I've finally solved the idle issues you were helping me test yesterday

Pretty cranking atm
[Android Q&A, Help & Troubleshooting] panther788:
Is this for me? I don't understand what you are saying.
[Android Q&A, Help & Troubleshooting] Nutterpc:
Yes it was for you.

Just quite simply means the developer of kingbeatz knows of the issue and will look at it when he's not as busy
[Android Q&A, Help & Troubleshooting] panther788:
The issue that apollo 1.1 is not included on talustus' cm10 rom?

Is there anywhere i can find the newest apollo?
[Android Q&A, Help & Troubleshooting] Nutterpc:
Don't know man, I found Apollo rather boring to use
[Android Q&A, Help & Troubleshooting] Nutterpc:
For those interested:

Kernel has now gotten to a stage where I'm just monitoring for issues

If you want to test my latest one, post on the thread and I'll upload it when I get home
[Android Q&A, Help & Troubleshooting] oc74ne:
Apollo is useless in my opinion, much prefer Google Play Music, similar to Apollo but easy to use and market updatable. I found Apollo back button doesn't work either.
[Android Q&A, Help & Troubleshooting] marthell:
I would very much like to try out your kernel :)
[Android Q&A, Help & Troubleshooting] chrisross:
Well I tried Heimdall under Linux. The GUI launches and it says 'detected' but doesn't actually seem to be (no phone identified). In addition, when I try to get Heimdall to get the TWRP it says 'firmware.xml not found'.

So I used my old XP laptop to run Odin. Managed to get the TWRP recovery installed, but when I tried to install the Softkeys_Fix Odin seemed to do it but when I re-boot the phone it gets stuck at 'Samsung' (no phone model logo) and I have to use Recovery to restore a backup.

So still no soft keys. I've also re-installed the Dreamkernel. What do you mean by a 'proper' Dreamkernel?

Seriously looking at the i9305 as it is more widely supported.
[Android Q&A, Help & Troubleshooting] Nutterpc:
Marthell, I'm just at the hospital atm with my partner, as her best friend is just in surgery ATM having a baby

Will upload it when I get home
[Android Q&A, Help & Troubleshooting] sddurand:
I think he means the one from Here:

http://android.dream-irc.com/index....kernel-gti9210t-v1-8-4cm10-20130113033955-cwm

Give this a try.
[Android Q&A, Help & Troubleshooting] chrisross:
Which is what I have installed. Still no soft buttons :(
[Android Q&A, Help & Troubleshooting] sddurand:
I'm sure you've tried already but thought I'd mention anyways... have you tried installing the prerooted stock ROM?
[Android Q&A, Help & Troubleshooting] chrisross:
Funny you should mention that: I installed the latest Swedish JB ROM last night. Worked fine, but still no softkeys. But this time was able to use the touch key code to correct, and the buttons were back (could get none of those hidden codes to work while running CM). Now I have to work out how to root again. The standard solution here is to use ICS Megamix but a) the ROM links no longer work and b) when I tried flashing two versions of ICS previously I got aborted installs.

What's the best way to get root with the latest ROMs? TWRP?
[Android Q&A, Help & Troubleshooting] sddurand:
You should be able to just install TWRP using ODIN. I used the .tar file accessible on the downloads page linked in this thread OP. I'm not sure if you will have problems since you don't have the same model (I think you have the GT I9210). I am using GT I9210T... once you have a custom recovery just flash SU or SuperSU for root. That's it.

---------- Post added at 06:23 AM ---------- Previous post was at 05:47 AM ----------

I need clarification... is the 1.8.x dream kernel for cm10 or cm10.1 or does it not matter? The OP says use 1.8.x kernel with the link which takes you to the skyrocket cm10.1 nightlys. This doesn't agree with the download links page. Thanks.
[Android Q&A, Help & Troubleshooting] chrisross:
Well I'd already used Odin to flash the Odin .tar and I regained root (yes, I have the i9210 which had a HK ROM originally).

I've now done a backup of my rooted setup. I'm a bit wary of going back to CM, tbh (and it's nice to see the phone correctly reported as an i9210!) but if I try that is there still a risk of losing soft keys again? And would I simply be able to revert to the stock ROM using TWRP and the backup?
[Android Q&A, Help & Troubleshooting] Nutterpc:
As long as you flash everything properly, and in the right order, you'll be fine

I did have the buttons issue a while ago, not now though
[Android Q&A, Help & Troubleshooting] chrisross:
Thanks, that helps.

One other issue though: when I boot into TWRP Recovery it only shows the backup I made using TWRP today - it doesn't show all the backups and other files I have in the phone and SD card, which I've just proven are still there by exploring via the PC. Am I missing something?
[Android Q&A, Help & Troubleshooting] marthell:
No worries, upload it when you got time. I hope everything went fine at the hospital :)