yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] ParthG:
Nightlies are on hold because buildbot is dead right now. Nightlies will be built when buildbot comes back online. I don't believe it's because of CM9 and ICS.

Anyway, questions like these are supposed to be the Q&A thread, not here.
[Galaxy S II Original Android Development] gkahd:
What is the Andoid System battery reading?

I get a continuous 13-16% CPU.
[Galaxy S II Original Android Development] Johnny.Bravo:
Mine is 4-5%
[Galaxy S II Original Android Development] brack11:
Mine is almost the same 5-6%

Sent from my GT-I9100
[Galaxy S II Original Android Development] gkahd:
battery or CPU?
[Galaxy S II Original Android Development] brack11:
I don't know, it's info from battery usage screen, so, I guess battery.

Sent from my GT-I9100
[Galaxy S II Original Android Development] joelteixeira:
Guys, all the last posts are supposed to be on Q&A (just like this one). Let's be fair and respect an area dedicated to devs only.

If we can't help coding, let's help keeping this topic organized.
[Galaxy S II Original Android Development] brack11:
Sorry, you are right.
[Galaxy S II Original Android Development] sennah:
I use nightly #116 with SiyahKernel 2.2. runs like a dream
[Galaxy S II Original Android Development] atinm:
Great, happy for you. How is this related to "DEVELOPMENT ONLY" like the thread topic asks?
[Galaxy S II Original Android Development] Qu@rk:
Since the weekend I have built my first Kangs of CM 7.2.0-RC0.

A very little suggestion. Please add date/time stamp to the version string ro.modversion in common_versions.mk also for Kang (and maybe release) builds.

Nothing really important, I know, but a little bit more comfortable when checking build versions.

ifdef CYANOGEN_NIGHTLY
PRODUCT_PROPERTY_OVERRIDES += \
ro.modversion=CyanogenMod-$(PRODUCT_VERSION_MAJOR)-$(shell date +%m%d%Y)-NIGHTLY-$(PRODUCT_RELEASE_NAME)
else
ifdef CYANOGEN_RELEASE
PRODUCT_PROPERTY_OVERRIDES += \
ro.modversion=CyanogenMod-$(PRODUCT_VERSION_MAJOR).$(PRODUCT_VERSION_MINOR).$(PRODUCT_VERSION_MAINTENANCE)$(PRODUCT_VERSION_DEVICE_SPECIFIC)-$(PRODUCT_RELEASE_NAME)[COLOR=Blue]-$(shell date +%Y-%m-%d.%H.%M)
[/COLOR] else
PRODUCT_PROPERTY_OVERRIDES += \
ro.modversion=CyanogenMod-$(PRODUCT_VERSION_MAJOR).$(PRODUCT_VERSION_MINOR).$(PRODUCT_VERSION_MAINTENANCE)$(PRODUCT_VERSION_DEVICE_SPECIFIC)-$(PRODUCT_RELEASE_NAME)-KANG[COLOR=Blue]-$(shell date +%Y-%m-%d.%H.%M)[/COLOR]
endif
endif
[Galaxy S II Original Android Development] codeworkx:
send a patch? gerrit?
[Galaxy S II Original Android Development] Qu@rk:
I still have to learn how to use git. That's why I posted my suggestion here and marked the changes (blue) in the code window of my post.

Edit:

I have found the "Howto: Gerrit - CyanogenMod Wiki" (http://wiki.cyanogenmod.com/wiki/Howto:_Gerrit#Source)

I will setup my accounts & system and I will create a correct Gerrit.
[Galaxy S II Original Android Development] codeworkx:
http://wiki.cyanogenmod.com/wiki/Howto:_Gerrit
[Galaxy S II Original Android Development] arif-ali:
Please delete
[Galaxy S II Original Android Development] RockRatt:
Got a question as I don't have and haven't used a i9100 but first off with your i9100 CM7 builds do you have built in video calls? Did the i9100 have it on stock samsung roms if it doesn't on CM7?

I know the I9000 samsung roms had video calls from the dialer and our captivates didn't due to no ffc. So is why I was wondering if the i9100 has it. If is does on stock, does it with your version of CM7?

I know with my i777 I can use Google talk, Skype, etc. But if your version of CM7 has it why would it not work with ours. Thanks for your thoughts.

Sent From My KickAss ATT SGS2 SPORTING CM7
[Galaxy S II Original Android Development] netchip:
1. Its not developing related ;)

2. I777 has it own forum, at&t galaxy s ii, there is the CM7 for the I777

Sent from my GT-I9100
[Galaxy S II Original Android Development] RockRatt:
Thanks for your help, as I am very aware of the i777 CM7. I was just looking for info IF the i9100 bad the dialer with the video call button on it. Sorry if I posted in the wrong section as I didn't think about checking/looking for the q&a thread. So again THANKS for your help netchip.

Oh ya, I can see why Atinm didn't want your help with things as far as CM7 went. But thanks again for your nice reply.

Sent From My KickAss ATT SGS2 SPORTING CM7
[Galaxy S II Original Android Development] netchip:
No offense BTW in my previous post :D
[Galaxy S II Original Android Development] atinm:
C'mon man, you know the rules. Go to the correct thread at

http://xdaforums.com/showthread.php?t=1286192 and ask questions there unless you are coding or debugging the I9100 and/or variants (the thread title has "DEVELOPMENT ONLY" in caps to make it easy to tell if you are in the correct thread).
[Galaxy S II Original Android Development] ambar_hitman:
Since we dont have a separate forum, what are the chances that Cyanogen will be released for Galaxy S2 I9100G? Its having TI OMAP 4430 chipset and PowerVR 540 GPU (same as Galaxy Nexus, Moto Razr etc). Samsung has stopped I9100 and replaced it with I9100G in few countries in Asia.
[Galaxy S II Original Android Development] netchip:
I'm busy with it :-)

Sent from my GT-I9100
[Galaxy S II Original Android Development] ambar_hitman:
Awesomeeeeeeeeee Cant wait. Maybe your release will make me want to root my I9100G.
[Galaxy S II Original Android Development] atinm:
It is a different processor, and might as well be a different phone. Codeworkx is working on an OMAP version - but no idea how far it is. It is actually easier to develop for than the Exynos because TI has opened the OMAP source. This isn't the forum to ask about it though - try the Q&A thread.
[Galaxy S II Original Android Development] netchip:
Yeah, arcee has said TI is the best Soc vendor at the moment. The source of TI is that the OMAP source of galaxy Nexus?

Sent from my GT-I9100
[Galaxy S II Original Android Development] ny-hardcore:
Did anyone succeed in building this on 32bit ubuntu maverick?

I get errors/broken pipe at the image creation.

Will post logs if needed,but wanted to know if it possible at all.

I followed the xyanogen wiki for setting up repo and sync etc.
[Galaxy S II Original Android Development] hayspat:
You have to use x64 build for compiling cyanogenmod.
[Galaxy S II Original Android Development] crachel:
CyanogenMod will build on 32-bit, only AOSP will not.. This isn't the place for this discussion though. Use wiki.cyanogenmod.com or any number of other threads on XDA opened specifically for building CM
[Galaxy S II Original Android Development] madmack:
it would be great if you guys can post a link in the OP to the git repo hosting your latest sources for the cm7 shipped kernel.

having quickly looked at the git manifest cm7 file, this repo gives a precompiled binary.
[Galaxy S II Original Android Development] atinm:
https://github.com/CyanogenMod/samsung-kernel-c1
[Galaxy S II Original Android Development] pinsb:
Does anyone know which version of the Network Card driver is included in the standard build?

The BCM4330 driver seems to have two or three different version depending on the Kernel used.

The reason I ask is I need to enable Monitor mode for some network defence testing and understand only certain version of the driver include the capability, either directly or patched.

Is the driver installed as part of a Samsung Binary Blob (due to the NIC being part of a packaged samsung solution) or is it using the standard source?

Thanks in advance.
[Galaxy S II Original Android Development] atinm:
The driver is from the kernel, but the firmware is a blob.
[Galaxy S II Original Android Development] pinsb:
Thanks. Has the blob not worked with any Kernels to your knowledge?
[Galaxy S II Original Android Development] atinm:
Which blob are you talking about? The only bcm4330 blob we're using is the firmware for the chip - the rest is the kernel driver because we have the source and we always prefer to use code rather than blobs if we can. We do not use the binary blobs for initializing the chip either - rather than using the proprietary blobs like btld etc, we use brcm_patchram_plus that also has the source. The chip is the same as the one for the Google Nexus, so the same source works for it.
[Galaxy S II Original Android Development] unrealtb:
Atimn are you working on ics? If not why not?
[Galaxy S II Original Android Development] atinm:
WTF, seriously? I don't answer questions that are demanding answers from me. Check for yourself what I am working on by checking what threads I have started recently or participated in recently, XDA allows you to do that for yourself.
[Galaxy S II Original Android Development] pulser_g2:
If the next words out of your mouth are not a profuse apology, then I don't think you'll get far with this kind of attitude.
[Galaxy S II Original Android Development] NeoS:
On topic, development only in this thread. I've warned in here before. Next non-development related post in here gets an infraction.

Besides, CM7 is reaching it's end, and so will this thread probably.
[Galaxy S II Original Android Development] mynameisjon:
I've been getting reboots, and I'm trying to narrow down the cause. Was wondering if anyone could take a look at my last_kmsg and give me a clue as to what's wrong?

I'm trying to see if it could possibly be because of a faulty SD card.
[Galaxy S II Original Android Development] Diamond Dallas Page:
Heres my tip an golden advise for anyone who has problems.

And yes i used cm all the time but not on samsung.

Use another ROM there are many out there, and yes they work.

Cyanogen isnt for samsung looking at the latest rls.

maybe a better rls will solve all the problems but i doubt it.

If you could make this post a sticky, allot of problems can be prevented ;-p
[Galaxy S II Original Android Development] Vaedryn:
Cyanogen Mod 7

RC1 7.2.0

http://download.cyanogenmod.com/?type=RC&device=galaxys2

SGS II Cyanogen Mod 9 Tapatalk
[EVO 4G Q&A, Help & Troubleshooting] luieavila:
I'm using Net 4.3.4 with HDMwIn and it has stopped mirroring. I plug in the cable and my phone freezes and needs a battery pull. I started clean with full wipe and re loading ROM, Warm 2.2 RLS5, and Kernel, Net 4.3.4, yet the problem continues. I'm having the same issue on my wife's evo as well.

Does anyone have a possible solution for this? Better yet, what kernel/HDMI app combo is being used? Any help would be greatly appreciated. Thank you.
[EVO 4G Q&A, Help & Troubleshooting] playya:
Try the FullHDMI software in the market and see if it works well for you. I have noticed that this one plays better with the Evo. If not try a different rom kernel setup. Go Stock 3.70 with Netarchy
[EVO 4G Q&A, Help & Troubleshooting] timmins77:
Hi All,

I've been happily using the old version of Amon Ra's recovery for at least six months. I'm wondering if it's really necessary to to the update? I'd father not flash a new recovery unless I have to.

If it is recommended, I know that ROM Manager doesn't support 2.3 yet, so is the best way to update placing the PC36IMG.zip in the base directory of the SD card?

Many thanks!

Tim
[EVO 4G Q&A, Help & Troubleshooting] nivron:
ROM Manager may still show 2.2, but it flashes 2.3.

If you aren't having any problems with 1.8, there's no reason to upgrade to 2.3. The new main feature is you can select which parts of the system you want to back up in a nandroid (data/system/wimax/sd-ext, etc).
[EVO 4G Q&A, Help & Troubleshooting] timmins77:
Thanks Nivron!
[EVO 4G Q&A, Help & Troubleshooting] Papa Smurf151:
Up to u to upgrade or not but it also has new feature to wipe specific parts of phone ie .. system, data,...plus a few others that wernt in there before
[EVO 4G Q&A, Help & Troubleshooting] xchompondizx:
Its worth it to upgrade 2.3 has a tad more features when it comes to backing up.:p
[EVO 4G Q&A, Help & Troubleshooting] playya:
Not sure but if 1.8 dont backup your wimax keys then you need to get ye to 2.3 as fast as possible.. Yes it is worth it...
[Thunderbolt General] dvigue:
i just for the TB today. i returned my X2 which was laggy and im happy with the TB. i see all kinds of posts bout how people are bricking there phones so i would like to ask all of you,

is it safe to root and install a custom rom? if so what is the safest way to do so?

Thanks so much...
[Thunderbolt General] Beastclaw:
Its all up to you if you feel comfortable rooting your phone or not, there will always be some inherent risk involved.

I have mine rooted and I have had no problems with it and thoroughly enjoy it.

Follow JCase's root method that's stickied in the development section if you choose to root.

A lot of the concern about bricking is from the leaked GB radio that some people are using so you could always stick with Froyo if you want to avoid that risk.
[Thunderbolt General] craneface:
I rooted my Thunderbolt after I had it for a week. The first week being unrooted was terrible. The battery life was horrible, and I contemplated returning it for an iphone.

Then I rooted, which was easy as long as you follow the directions posted in the threads. Now I can easily get a full day of use with my stock battery... off the charger for 17+ hours with 4G, bluetooth and wifi always enabled, and GPS enabled sporadically.

I'd say read up on the root process. Then read up on different roms. I use Das BAMF 1.7, and Imoseyon's 2.6 lean kernel. If you determine that root isn't for you, there's easy ways to unroot.
[Thunderbolt General] sublimaze:
It's not the rooting process that is bricking phones. Rooting is perfectly safe, as long as you follow the steps. The bricks have occurred after flashing the recent Gingerbread leak. If you stick with a Froyo-based rom, you will be fine.
[Thunderbolt General] microdot:
That was also always my undertsanding, that all rooting does is give you permissions that would normally not be available. What you choose to do with those permissions once you have root is the risky part.
[Thunderbolt General] bp328i:
Mine was one of the few that did brick and I had to send it off for 2 weeks before it was replaced.

The first thing I did when I got home with my new Thunderbolt was root it and flash a Froyo ROM.
[Thunderbolt General] sublimaze:
@bp328i

But you were running the leaked GB for a few days prior to bricking, right?
[Thunderbolt General] bp328i:
I was running the leaked GB when my Thunderbolt bricked.

I meant to quote the OP just to let him/her know it IS safe to root.

I just got my new Thunderbolt a few days ago and the first thing I did with it was root it, and this was after my first one bricked.
[Thunderbolt General] TSerge:
As someone who bought a TB a week after it came out, screwed up my first root attempt, got it the second time after "unrooting" and has since loaded a ton of different ROMs, radios, and kernels, I can safely say you have nothing to worry about.

As long as you're following the instructions, that is. Can't account for human error, after all :D
[Thunderbolt General] ddgarcia05:
All these bricked phones are being bricked by people who flashed the newest leaked gingerbread (gb) radio onto their devices in order to run the leaked gb rom. Even flashing the newest gb rom+radio didn't mean your device was going to be bricked to sure, it was just a few whos were bricked. If perfectly safe to root as long as you follow instruction and I don't see anything risky about installing apps with any permissions as long as you get the app is from a creditable market place.

The long way of rooting seems easy for me all I did was get adb running and copy pasted the commands on the command prompt.
[Thunderbolt General] SamZzz:
Yep. Definitely safe as long as you follow the directions and stay away from the Gingerbread radios.

I rooted mine two weeks after I got it. Hubby finally caved and let me root his after seeing the differences.

Grab you an md5 checker and give it a shot! :)
[Thunderbolt General] dvigue:
thanks everyone for your help...i appreicate it.

i am rooting it now!

what radio should i stay away from as far as causing the reboots?
[Thunderbolt General] EEdaesung:
Rooting your thunderbolt will cause a mass alien invasion over the city of Los Angeles.
[Thunderbolt General] Silvus:
What everyone else said there is some risk(minisule) if you stick with froyo you should be fine, if you end up with the reboot problem post rooting flash the radios to the old versions and your tb life will be much more sweet.
[Thunderbolt General] iastonish:
The gingerbread radio. Any froyo rom will be good to go.
[Thunderbolt General] bendystrawboy:
rooted and flashed a new kernel with no issues thus far.yay.
[Thunderbolt General] timp123:
Couple questions. First, which is the easiest and safest root method? Droid 2 rooting was a simple one-click affair. I see lots of methods around, including automated, one-click roots. Jcase's post ([ROOT] MR1/OTA PermRoot + Unlock Bootloader - Safer/Easier 5/12/2011) looks pretty complicated. Is this the one I should do?

Second, I am really tempted to flash a gingerbread rom (th3ory b1.7), and I've flashed several GB roms to my droid 2 before recently getting the TB. If I carefully follow the instructions in the threads, am I pretty safe, or is the GB radio thing still pretty risky?
[Thunderbolt General] sublimaze:
1. The easiest is the one-click method. However, if you are not familiar with adb, I highly recommend doing it the way described in jcase's thread. That way you get experience with adb. Anyone even considering rooting needs to know basic adb commands.

2. To my knowledge, there have been no bricks with the GB radio posted here. But remember there are no 100% guarantees when rooting/flashing your phone. Good luck
[Thunderbolt General] satseaker:
wish people would stop blaming the radio,my first bolt bricket on stock froyo after the first ota update,never had gingerbread on it. as far as rooting goes if you eant the phone to work to itd potential you need to root it and flash a custom rom that or wait tol vzw and htc decide to update it to gingerbread or even icecream for that matter

sent via my bamfed out tbolt
[Droid Incredible Q&A, Help & Troubleshooting] cn0421:
hey i had skyraider then used chad's kernal and it got stuck in the boot loop. so i just restored it using the clockwork. now everything is back to normal just rooted. so...if i ever decide i want to go back to stock rom and kernal when i have custom roms and kernals cant i just restore it back to normal? does this make sense?
[Droid Incredible Q&A, Help & Troubleshooting] RMarkwald:
Is the backup you have of SkyRaider or a backup of the Stock ROM you made after rooting? You can always restore backups of anything you make to the point in which the backup was made. You should backup before flashing something new, in case you don't like it...saves lots of work.

If you want to go back to complete stock, un-rooted and all, you'd have to use the RUU. This would be putting the phone to the point just like it was when you unboxed it and turned it on.
[Droid Incredible Q&A, Help & Troubleshooting] cn0421:
ah ok i get it. yea i backed up before i flashed skyraider and the kernel. Thx
[Droid Incredible Q&A, Help & Troubleshooting] RMarkwald:
No problem, just some added info: the backup you make will also keep the kernel, so if you flash a custom kernel and backup the ROM, it'll keep that kernel too. So there's no need to reflash that if you restore a backup.
[Droid Incredible Q&A, Help & Troubleshooting] 06stang:
And s-on patch to unroot. Dont get in the situation like me where you can't s-on and use your warranty
[HTC EVO 3D] nkstn007:
So the Service Credit for switching to Sprint says it ends on 6/23. AND the Evo 3D of course comes out on the 24th. I will be coming from TMO and wanted to get this credit.

Could/Should I just get switched on the 23rd or sooner and just get like an Evo or similar phone and also buy the $50 dollar reserve for the Evo 3d. Then on the 24th switch my phone to the Evo 3D and return the other phone?
[HTC EVO 3D] nate420:
Yea as long as you keep the number your porting active for 61 days...

I'm also doing this with two port in numbers from tmobile. So make sure if you start the contract or service at a sprint store you preorder it there....

Or go to radio shack start service and pre order there

Same with best buy....

DO NOT go to sprint to set up service and then pre order from a radio shack or best buy... Pick one of the three and do all of it their or you will lose the port in credit

sent from anything but an iPhone
[HTC EVO 3D] vinterchaos:
don't they charge restocking fees or something, i was telling my wife we should do this and she was like it's gonna cost us 70$ per phone to do that.
[HTC EVO 3D] nate420:
No restocking fee for new customers that exchange a phone in 30 day time frame...

Trust me coming from tmobile I asked about everything

sent from anything but an iPhone
[HTC EVO 3D] derek826:
So you won't have to pay the restocking fee if you are a new customer. Are you sure about that? And I also have another question, if you do this will you lose yourpreoder spot because I saw someone post that you would lose your preorder sport?
[HTC EVO 3D] ebolamonkey3:
Not sure about losing your preorder spot but for new customers, there are no restocking fees. Otherwise it's $35/phone.
[HTC EVO 3D] nate420:
You won't lose your spot at radio shack or best buy... I hear you will at a sprint store but I doubt it... Is just ask them

sent from anything but an iPhone
[HTC EVO 3D] toxicfumes22:
so, Im just going to put this out there. In order to save $125 per phone, if it costs you $70 then awesome you still save. So tell your wife that would be a worst case scenario just like my att ends the 27th of June and well If I have to cancel early that costs $60 (Im still working on it being free) but I still save money.
[LG Revolution] majorpay:
I still don't have the long press search fixed, but the search key, I do.

1. If you haven't done so already, remove or rename BingSearch.apk and BingVoiceRecognitionService.apk (I renamed mine by adding .bak to the end just in case).

2. Uninstall Google Voice and Google Search if you already have them installed (or delete them from the /DATA/APPS directory).

2. Find a Froyo ROM (I used Kaos Froyo because I was an Eris user), unzip, and pull "QuickSearch.apk" and "VoiceSearch.apk" from the SYSTEM/APPS directory and put them into your Revolutions SYSTEM/APPS directory (I used "Root Explorer" to do this).

3. Reboot, hit the search key and watch the magic happen!

If anyone has thoughts on the long search key press, let me know. As of right now, I'm still looking into it.

Something to note is that this doesn't work properly with the stock home interface. I found that interface laggy and crap anyhow, and I think most of you have changed it already, but just throwing that out there. If interested, I'd give GO Launcher EX a try (that's what I'm using).

Edit: The long search button functionality is buried in the android.policy.jar file. Until we get a recovery going, I don't think I'm gonna go there :D

If you have any issues with bad voice recognition, try this:
[LG Revolution] majorpay:
New update to this procedure: DON'T UPDATE voice search after this. If you do, uninstall the update because the voice recognition goes nuts on the latest version.
[LG Revolution] Triskite:
Got it working as well.

Also used Root Explorer. Didn't uninstall anything- used the preexisting APK for googlequicksearchbox.apk or whatever it was called, renamed it to QuickSearch.apk and put it in /system/app after mounting the folder.

Worked on reboot.
[LG Revolution] nick99wj:
Yup, this works. Copied and pasted both into system/app, changed the googlequicksearchbox.apk and the voice search one to QuickSearch.apk and VoiceSearch.apk. , deleted from data/app, rebooted and all good.
[LG Revolution] Triskite:
so does voicesearch activate with longpress search button for you?

if so, can you post your voicesearch.apk? it's not working for me for some reason