yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Crucio_:
i havent flashed over the secure kernal yet but think im going too, have people said flashing the sercure kernal effects the battery life? could you point me to that post please :)

also yeah that buddies now thing is lol. i have frozen mine atm.
[Galaxy S II Original Android Development] :
just wanted to say thanks . seems to work great
[Galaxy S II Original Android Development] winwiz:
works great, thanks OP
[Galaxy S II Original Android Development] nickbarbs:
buddies now ftl?

Is there a way i can back up or extract my KDA kernel for backup?
[Galaxy S II Original Android Development] Burko:
My understanding is that this root method uses a modded generic kernel, rather than a Samsung official kernel modded to allow root.

I'm assuming that it's a matter of time before we can simply root without kernel replacements because it's not something i like doing with a phone i've only had for a day.
[Galaxy S II Original Android Development] Techno79:
Gotcha, I miss read bits of the first post and a few subsequent posts and managed to confuse myself :D

One thing I'm still not sure is why this is an "insecure" kernel?

How exactly is this solution insecure? Does this root method leave my device any more open to attack than a "secure" solution that Chainfire is still hoping to achieve?

TIA
[Galaxy S II Original Android Development] nickbarbs:
Yeah I'm on this level too.

I'm an advanced user, I've loaded tons of roms on my old Samsung Captivate, and I've mixed and matched many kernels/roms/etc. But I've noticed you can get varying results and it can be dicey at times.

Not willing to compromise on the excellent and stable performance of this phone so i'm waiting for a non - kernel flashing root method.

Buddies Now though, omg, the worst
[Galaxy S II Original Android Development] madmack:
This is not a modded generic Kernel. A generic kernel would never boot on your device without proper porting.

This is a Samsung S2 Kernel that has been modified (without recompilation, just by patching the binary) to be insecure. Thats what ChainFire does over at SGS. He releases stock ROMs that include recovery, root.. etc without ever knowing what the source code of these kernels is.

The closest thing we have to a modded kernel is Supercurio's compiled kernel. Someone tested it and said that it boots, so that one there has some potential for source code improvements, mods and hacks. but chainfire's is as stock as you can get.
[Galaxy S II Original Android Development] Chainfire:
People reporting bad battery life due to this root probably don't know what they are talking about. It is quite simply impossible that it makes any difference between KDD and "insecure" KDD. It may be KDD is worse with battery than KDA though, but both KDD and KDA are delivered on retail devices.

You need root to back up the kernel, so no. I do have the original KDA kernel around here somewhere though.

Wrong on both counts. This is an official Samsung kernel with the "secure" bit flipped from 1 to 0.

You could be waiting a very long time if you want root without kernel replacement, if it'll ever be available at all. (technically, you could do the same trick with a /system replacement instead of a kernel replacement, but that would be a 300mb hack instead of a 6mb one :))

It's called an "insecure" ("unsecure" ?) kernel because the "attack vector" (if you go so far as to call it that) to allow root is flipping the "secure" variable from 1 to 0. So the kernel is not in "secure mode", hence it's "insecure" ;) Apart from being able to do "adb root" to gain a root shell, there's no difference, though.

Re performance, battery use, etc, I always base my roots on stock kernels. You'll get the same performance and battery life as with the original kernel, unless you turn tweaks on (my SGS1 CF-Root kernel has a tweak utility that allows you to en/disable certain common tweaks)

Again with the waiting, a non-kernel method may never come at all.
[Galaxy S II Original Android Development] Burko:
Hey Chainfire, didn't realise you were using an official Samsung Kernel made insecure.

I thought as you didnt have the phone in hand you were using a generic kernel.

On this basis I'm more than happy to go ahead and do this.

Cheers mate.
[Galaxy S II Original Android Development] lukemo:
I've just received from Clove an English version of SGS2...the kernel is 2.6.35.7-I9100XWKDD-CL161513 root@DELL103 #2

So it's the same of the first post but secure, isn't it?

Thanks
[Galaxy S II Original Android Development] sconstan:
all ok

just finish rooting using initial instructions. everything seems to have gone as planned.

well done and thanks.
[Galaxy S II Original Android Development] lukemo:
Is it yours a UK retail version? Thanks
[Galaxy S II Original Android Development] ma10:
My SGSii came with KDD firmware as default from O2 the other day and I've successfully rooted as per the OP's post here.

Also, I even flashed the KDF firmware, rooted just as before and re-flashed just the KDF kernel and everything is still working fine!
[Galaxy S II Original Android Development] lukemo:
Thanks a lot, ok I'll try to root
[Galaxy S II Original Android Development] JJEgan:
Have you still got the O2 splash screen .

jje
[Galaxy S II Original Android Development] ma10:
When I first rooted with the shipped firmware yes, o2 splash screen was still present. When I then flashed the KDF firmware it had removed the o2 branding.
[Galaxy S II Original Android Development] JJEgan:
Thanks i am not going down any route that removes O2 branding until i have a full flash-able backup of the original O2 firmware .

jje
[Galaxy S II Original Android Development] tonime:
thanks! works fine.
[Galaxy S II Original Android Development] otester:
Worked like a charm.

UK SGS2.

Thanks!
[Galaxy S II Original Android Development] lukemo:
all ok, but not using osx+parallels (win7), only with a windows pc

thanks
[Touch CDMA Android Development] dude4:
i have a bell htc touch and have been running NFSFANS ROM and a 2.2 version of android(can't remember which one i tried many) but for the last while android has become unstable, randomly locking up or resetting.

is this common? because it never happened on my warm donut build.

could it be less stable because its running from the sd and not nand?

im afraid that if i switch to android only il have a complete unstable POS just because i want android 2.2 or better

thats why ive kept WM despite hating it because if there was a problem i know it will not crash on me making a phone call or something.

im also a lazy bugger and like that WM can be controlled by my PC, i do this to type longer SMS's and such is there a way to do that on android?

anyway im indecisive what build of android should i use? and are there any downsides to going pure android that i should know about?

and what app should i use to backup my contacts, sms, call history, etc. and is there one that works on WM aswell so i can merge my WM stuff with my adroid stuff and then back it up

thanks
[Touch CDMA Android Development] goducks3620:
I am running SuperFroyo and it's super stable. Maybe once a week or so it will freeze up but that seems better than WinMo.

I have not got in to sync with a Windows machine, but it does sync just fine with Ubuntu. The Google Voice works well for dictating texts and that's what I mostly use, it's pretty accurate even with my (mild) drawl.
[Touch CDMA Android Development] Theonew:
You can use "Funambol Sync Client" to sync with both android and windows mobile. You can also try gingerbread instead of froyo. The latest Gingerbread build is more stable to use, and also for the freezing part, you can overclock your processor to about 520Mhz (for complete stability) but I got it up to 550Mhz for more speed especially when playing games. Hope this helps.:)
[Touch CDMA Android Development] dude4:
is there a way to go nand without using windows?

if not is the stickyed guide " Easiest Step-By-Step Android Tutorial for the Vogue (NAND Method/Internal Memory)" actually the easiest way?

i ask because its older thus potentially out of date

if not i have a question

step 6 is "Download the latest NBH file that begins with "voguimg-240x320-..." (needed for all Vogue Android ROMs):"

but the latest one is voguimg-240x320-2.6.32-froyo-14-01-11_14.nbh and what if i was planning on running on trying a gingerbread? like Scoot CyanogenMod 7.0.2 RLS2 does it matter that the nbh is for froyo if not is that the best nbh to use?

thanks
[Touch CDMA Android Development] computerwiz_222:
I've been running Android on my device for more than a year now. I reflash every few months to one of the new releases to keep the device fresh and ensure that I have the latest bug fixes.

The device isn't SUPER stable, it crashes probably once a week but other than that, it's fine. I use it in my 2010 Kia Forte and it bluetooth syncs the address book.

I recommend it.

+1
[Touch CDMA Android Development] dude4:
i seem to have gotten it installed on nand :)

im running Scoot CyanogenMod 7.0.2 RLS2 but i noticed when i tried to download a

.zip file it mentioned that i dont have a sd card when i do

why wouldnt it show up and how can i fix it?

thanks
[G2 and Desire Z Q&A, Help & Troubleshooting] arorasa:
So picked up a T-mobile G2 from a guy on craigslist. I forgot to check out the camera before I paid up. I came home and cannot get the camera to work at all. the camera app crashes everytime and I have to force close it. The dedicated camera button also does nothing at all. Have tried doing a factory reset a couple of time and have no luck.

Any ideas for options? I am pretty sure the warranty is not in play as I am the second(third /fourth) owner.

Looks like its running the stock firmware

Android Version

2.2

Baseband Version

12.28b.60.140eU_26.03.02.26_M

Kernel Version

2.6.32.17-g9ab3677

Build Number

1.22.531.8 CL277427

Thanks in advance
[G2 and Desire Z Q&A, Help & Troubleshooting] ratchetrizzo:
Did you try a 3rd party camera app to make sure the camera works?
[G2 and Desire Z Q&A, Help & Troubleshooting] arorasa:
No third party camera app works either. I think they all use the base app in the background or something.
[G2 and Desire Z Q&A, Help & Troubleshooting] ratchetrizzo:
At this point since you cant get your money back you might as well root it and install a different rom and see what happens.
[G2 and Desire Z Q&A, Help & Troubleshooting] eunkipark92:
Well I ibuy all my phones off craigslist and I can get replacement from tmobile. Worked for mytouch 4g and worked for g2.

Please click thanks button

U must be willing to spend sometime on this...

Won't work unless ur a tmobile subscriber.

1.go on tmobile website, log in, go to contact us and online chat.

2.find the one that says trouble shooting

3.fill out ur info

4.tell them you recently bought a g2. (Don't say like 2 weeks ago or anything like that, tell them you bought it yesterday) and obiviosuly don't tell them you bought it off ebay or craig. Act like you bought it off tmobile store.

Tell them you have a friend and he had his g2 for a while and he's firmware version is different than yours. Tell them he received an ota upgrade sometime ago. and you still haven't received your ota update. So you took it to the store and everything and they told you to contact tmobile and see if your imei number is in their system. Now they will require your imei number. Give them your imei number and they will tell you they updated in and ur imei number is now in their system.

At this point their system will think you just bought the phone as it just registered on their system. So its like your on tmobile 14 days remorse return thingy. I forgot what its called.

Now exit the online chat.

Now this time choose phone acce then warranty exchange.

And tell them you are experiencing weird reboots problem. Tell them the phone reboots by itself like 5 times a day. And you found a dead pixel on the screen idk make some stuffs up

And tell them you already took it to the store and did hard reset and eveything and your still experiencing problems.

(This is a must part or they will walk you through hard resetting the phone steps and tell you to contact again if you're still experiencing problem)

Ur done. They will say they will send you the replacement phone at this point.

Just make sure you still have the void sticker and u don't have any water damage. Or you will get charged.
[G2 and Desire Z Q&A, Help & Troubleshooting] eunkipark92:
Oops double.post
[G2 and Desire Z Q&A, Help & Troubleshooting] shortlived:
Just out of curiosity how much did you pay for it
[G2 and Desire Z Q&A, Help & Troubleshooting] -PoXx-:
Strange, some others have mentioned it, have you tried rooting and installing a custom rom? Or is that something you didn't have interest in doing?
[G2 and Desire Z Q&A, Help & Troubleshooting] daboma:
Hiw sure are you that this will work on a G2 that was purchased back in October? I have a legitimate problem....traded my N1 for G2 on craigslist and now the screen is white w/black lines. I have a custom ROM installed (but didn't tell them that). I called and they said it's not under warranty (since I'm not the original owner). I'm guessing that conversation is in the system, but I'm willing to try this method. This seems incredibly sketchy and it seems like they would have the phone in the system on the original owner's account.
[Atrix 4G General] spacev:
I did aroot on 26, and retain root for 57. No other mods. I don't really want

to use gingerbreak if I don't have to.

So did anyone try the old retain root for the new 1.8. 3?

Thx
[Atrix 4G General] s1mpd1ddy:
I tried. didn't work for me though. I read other people had success though
[Atrix 4G General] sunshine1982:
It worked for me, I flashed a fresh 1.26, then ran gladroot, updated to 1.57, then updated to 1.83, then ran afterupdate. Rooted on 1.83 and running fine.
[Atrix 4G General] rpolansky:
yes:

http://xdaforums.com/showpost.php?p=13063994&postcount=182

(but I typed the commands; I didn't run the batch file...you will have to confirm on your phone the su request before you type the commands)

imho at your own risk

thanks to neotekz and fido!
[Atrix 4G General] ECdOc:
+1 on typing the commands, worked like a charm. Webtopmod works just as well.
[Atrix 4G General] nsaia:
This method also worked for me.
[Atrix 4G General] clark222:
didnt work for me, im not rooted now
[Atrix 4G General] Jiggah:
It didn't work for me either. I had to gingerbreak it.
[Atrix 4G General] clark222:
would gladenable work?
[Atrix 4G General] MacAlert:
Did not work for me either.....did you loose any data when using gingerbreak?
[Atrix 4G General] seapickle:
started with 1.2.6 sbf, ran retain root and typed the commands. updated to 1.57 also running retain root and typing the commands again. updated to 1.8.3 ran the afterupdate script and worked for root.
[Atrix 4G General] stl-soldier:
Gingerbreak has wiped my internal SD every time I run it. Make sure you save your data somewhere else. It has not done anything to my external SD, but it does require that you have an external installed to work.
[Atrix 4G General] ceo.mtcl:
Which update did you use for going from 1.5.7 to 1.8.3, the 1.5GB sbf file or 30 mb update.zip file?
[Atrix 4G General] squarejp:
It is very simple. I came from 1.2.6 and ran GladRoot before OTA 1.5.7. I then ran afterupdate.bat. It has lasted me for a month.

Today, after upgrading to OTA 1.8.3, I simply run the afterupdate.bat again to recover the root. Titanium Backup is now working again.

If you already have rooted 1.5.7, simply upgrade to 1.8.3 and run afterupdate.bat.
[Atrix 4G General] spacev:
Thanks guys.

Funny thing is, now that I am finally confident to upgrade, my phone doesnt even want to yet..... I thought it was avail to everyone already?

Also went to the website and downloaded the updater. The Atrix website still says 4.1.57 is the latest update.
[Atrix 4G General] seapickle:
if you are daring i think someone has posted the .83 sbf.

the 30mb OTA
[Atrix 4G General] jimmer411:
I used the update.zip thru android recovery and retained root in 1.83.
[T-Mobile LG G2x] hill180:
Ok. I have the G2X from the GS4G.

Does anyone notice really bad wifi calling quality?

When I was on my GS4G, the call quality was awesome. I mean, no problems, fast connection, no jitter.

With the G2X, the jitter is almost unusable.

Should I wait for the 2.3 update to see if that fixes the issue or should I just return the G2X for my old GS4g. The only thing I would miss would be the flash.. I know.. crazy, but I really just use my phone for business and rarely need that much CPU power.

Thoughts?
[T-Mobile LG G2x] Lootes:
I use wifi calling in my office since the reception is horrible. I haven't had any issues with call quality, more or less smooth and crystal clear. Not sure what could be causing the jitters with yours.
[T-Mobile LG G2x] ikaden:
I'm using wifi calling in my office and at home and haven't had any issues with call quality.
[T-Mobile LG G2x] hill180:
if you are not having problems, what the network type you are using.

A/B/G/N

Are you using a bluetooth,etc,?

Thanks!
[T-Mobile LG G2x] jland22:
I can attest to my wifi calling being poor. The call starts out with good quality then slowly diminishes and either drops me or says my wifi lost connection. It definitely isnt my router and I shouldnt have lost connection... Not sure what the deal is.
[T-Mobile LG G2x] Lootes:
Home and offfice are both N, not using a BT headset.
[T-Mobile LG G2x] BarryH_GEG:
I use Wi-Fi Calling a lot. On the G2, the call quality was good even with a moderate signal. Sitting five feet away from my Netgear N600 n-speed router with 0 dbm the G2X flakes out on Wi-Fi calls. It'll start out great then voices start to drag and muddle and then goes back to great. I don't think it's the Wi-Fi Calling app, I think it's LG's F-d up implementation of Wi-Fi which is causing the signal to fluctuate. The router's bullet proof and the G2 performed flawlessly (as do other telephony devices hanging off the router) so I know it's the phone.
[T-Mobile LG G2x] profresh:
I've had issues with wifi calling as well. static not clear. Turned off the wifi calling and it worked perfect. I'm not high on wifi calling right now
[T-Mobile LG G2x] cbowens:
My experiences with wifi calling have been mixed. Sometimes I get absolutely perfect calling, and other times its completely unusable due to stutters. Based on this and what the rest of you are saying, I'd agree that its LG's wireless drivers that are the problem. The hardware itself seems to be capable, and its not the router, so the software is the only thing left. And if people have been able to use t-mobile's wifi calling app on other phones, that leaves this phone's particular software, ie the stuff LG provided us with, since the wifi calling app is the same throughout the different phones. Hopefully gingerbread or even better cm 7 will fix this.
[T-Mobile LG G2x] ctt0002:
wifi calling on my g2x is awesome! Way better than what it was on my old blackberry 8900.
[T-Mobile LG G2x] C0dy:
Wifi calling was horrible on my SGS 4G, while it's great on my G2x.
[T-Mobile LG G2x] Chainar1:
I'm definitely getting better call quality on my g2x than I did on my mytouch 4g. However, I do occasionally have a problem with the app failing to register on T-Mobile's network. However, a quick restart of wifi and the wifi calling app always seems to rectify the problem.
[T-Mobile LG G2x] hill180:
I had the MyTouch 4G, MT4G with CM7, GS4G, and G2X

Here is my experience.

At first I did everything, Linksys, Netgear, Apple Router, N/G/A/ 2.4/5(for the 4g that had that), QOS, WMM, Blah blah blah..

It was never my network.

My phone calls are not short, they can be 1-2 hours long with tech support/customers

MT4G - Jitter.

MT4G(CM7-RC) - Better But Occasional Jitter

GS4G - Almost Perfect, some jitter but we are talking 1 time a day, not 20 times during a call.

G2X - Jitter, similar to the MT4G

Well.. sigh..

Because I used Wifi Calling exclusively when I am in my home office (all carrier have a problem because of the houses around me and a basement Office - (Sprint/VZW/ATT/TMO)), I exchanged my G2X back to my old Galaxy S4g. I loved the G2X but the wifi calling was critical for me. I agree with someone who posted Cm7 might help, but my gut is telling me it is a wonky wifi chip/card, not the wifi application.

I know software will update, but by then I might be getting the HTC sensation and Android will fully support the dual core procs and more improvement time for the wifi calling.

Why I had to return it:

Wifi Calling Bad for me, Had to do a battery pull a couple times, reboots didn't bother me every once in a while, I notice with wifi calling it would many times not release the router, in other works, I would leave my house and even though I was on 4G full bars - I could not complete any calls - Bug in Wifi Calling software?, Battery wasn't by far the worst (i think the thunderbolt has that honor :) ), but with the galaxy I could go through my 5am-11pm day. Bluetooth not connecting automatically, (I noticed this with an LG Optimus S - Buggy?) I like the touchwiz (shoot me).
[T-Mobile LG G2x] DebauchedSloth:
I notice that Wifi calling goes south when the screen goes off. Cyanogen includes a program called GANOptimizer which, for Gingerbread, uses a new API to disable wifi power saving.

The built in gingerbread SIP stack also disables wifi power saving on its own, BTW.
[T-Mobile LG G2x] oilfighter:
My wifi calling is flaky. Sometimes it's great, sometimes it's very poor. I just went ahead and disabled the wifi calling using Titanium Backup Pro.
[Vibrant Android Development] zbt1985:
THIS IS NOT FOR VIBRANT!!! IT IS MEANT FOR DEVS TO INCOPERATE INTO 2.3 ROMS!!!!

DO NOT FLASH!!!!!​

Since nobody has put it up, I figguerd i would, and help some of the devs out!

http://android.clients.google.com/p...749.signed-soju-GRJ22-from-GRI40.a14a2dd0.zip

go dl the new gingerbread 2.3.4 and hopefully we can get video calling working fully via gtalk on our phones!

if you do have it ignor this, if not, well then your welcome!

:D
[Vibrant Android Development] adampdx:
Has anybody braved this? Do we dare flash it?
[Vibrant Android Development] adampdx:
Wait, what is this? It's only 12mb. Is it supposed to be the updated Gtalk?

Oh, I see. It's new Gapps? I think I'll back up and flash, just for kicks.
[Vibrant Android Development] T.C.P:
thanks bro, but this is the wrong section, you will get flamed because this isnt for out phone, and for posting in development, this should go in general.
[Vibrant Android Development] adampdx:
Oh it's not for our phone, eh? Glad I read that. Oh and you up top there, watch what you post dude.
[Vibrant Android Development] zbt1985:
That's why it's for the devs to port...i guess i need to change the name, but it does have to do with development...
[Vibrant Android Development] bearsfan85:
considering that only a fraction of the people have an FFC on a vibrant video gtalk would be kinda pointless unless you plain on setting up a mirror type thing or tv out. For one person either you or the chat partner it would end up basically being a phone call. So while it may have something to do with dev in general, it really doesnt for our phone.
[Vibrant Android Development] zbt1985:
well I have a ffc, and it's really easy to install, and with all the dev i see on ffc's and everything, i would assume that a lot of us do...if you don't have one, you should it's worth it and very easy to install!
[Vibrant Android Development] jhepoy:
i would like to see this happen.. i have FFC v2 and been video chatting using Tango and Fring..
[Vibrant Android Development] M_T_M:
Fixed your first post mate ;)

What is the source for this program/leak/software? :confused:

Cheers,

M_T_M
[Vibrant Android Development] fishman0919:
Most likely for the Nexus S LINK
[Vibrant Android Development] zbt1985:
That it is!