yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Hacre:
Ah ha, USB plugged in? That explains it. I changed a parameter in the kernel config that allows the phone to pull up to 500mV over USB when charging, as opposed to the pithy 2mV it is configured with by default. Naturally this raises the temperature as a higher energy exchange is occurring, however it also drastically shortens the charging time over USB compared to normal.

EDIT: It looks like I've fixed the nandroid issue, I'll update the OP with the fix once this nandroid finishes successfully (it wouldn't even start for me before).
[Galaxy S II Original Android Development] Mr_Q:
No, version 1.0 I guess.. Will update to the latest 1.1 and see if this screen issue is resolved. Thanks for the support so far! :)
[Galaxy S II Original Android Development] buxz777:
loving the sound of this kernel :-) just waiting for my phone to fully charge and iam going to flash it via odin :-)

Hopefully it works ok with the wicked rom lemar75 iam using at the minute then i think my phone will be complete for a while :-)

thanks for the hard work mate :-)
[Galaxy S II Original Android Development] Major_Sarcasm:
Typo? 200?

Have you altered anything to do with AC charging as well, just out of idle curiosity? My in-car charger registers as AC when plugged in. The fact that you've altered either will likely make this a popular kernel choice ;)
[Galaxy S II Original Android Development] mach0boi:
Ooh i see. Thanks man. Your fast. This is my favorite line from you:

" Anyone who claims otherwise or says that noop or deadline or CFQ is better, they're wrong. Why? Because I say so and I'm right."

LOL! :D
[Galaxy S II Original Android Development] Hacre:
No typo. From Samsung's defconfig:

grep CONFIG_USB_GADGET_VBUS_DRAW arch/arm/configs/c1_rev02_defconfig
CONFIG_USB_GADGET_VBUS_DRAW=2
[Galaxy S II Original Android Development] kalpik:
Have you also altered the current intake from AC charger? Cause my phone seems to run hot even on that!
[Galaxy S II Original Android Development] EarlZ:
After several testing, I can conclude that the CF-Root KG1 does a good job of compensating for the yellow tint, its actually gone. Flashing to this kernel puts it right back.. Maybe Hacre you can look into this?
[Galaxy S II Original Android Development] Major_Sarcasm:
Hmm, mine just died in sleep.
[Galaxy S II Original Android Development] Pacifiste95:
Hello all,

what are the best settings in setCPU with this kernel for correct performance and best battery life?

thx
[Galaxy S II Original Android Development] mach0boi:
I noticed this too. When I was on cfroot I took a couple of shots to see if the yellow tint/darker left side is still visible and it isn't anymore. Now that EarlZ mention this on cfroot thread, i looked at it and i can confirm the yellow tint is much more noticeable.
[Galaxy S II Original Android Development] KaliKot:
Same here, flashing 1.2 now to see if this fixes it.
[Galaxy S II Original Android Development] Major_Sarcasm:
Since this kernel was only released this morning, why don't you try some different settings and tell the rest of us? Personally, I'm using similar OC/UV settings to what I was using with Tegrak.
[Galaxy S II Original Android Development] veyka:
HALP after flashing this kernel my phone wont make me a cup of tea and some lunch! Also it gave birth to an iphone and I think it just winked at me.

Some benchmarks for the epeen lulz:

Vellamo Score: 925

Quadrant Standard: 3055

CF Bench:

Native MIPS: 1009

Java MIPS: 213

Native MSFLOPS: 552

Java MSFLOPS: 297

Native MDFLOPS: 339

Java MDFLOPS: 205

Native MALLOCS: 21091

Native Memory Read: 3211

Java Memory Read: 480

Native Memory Write: 1825

Java Memory Write: 673

Native Disk Read: 577

Native Disk Write: 191

Java Efficiency MIPS: 21%

Java Efficiency MSFLOPS: 60%

Java Efficiency Memory Read: 14%

Java Efficiency Memory Write: 36%

Native Score: 11066

Java Score: 3166

Overall score: 6326

(the comparison SGS2 score is 11255,3234,6442)

Linpack Multi threaded: 78.204 (2.22e-16 precision), 79.038(2.22e-16)

Linpack Singel threaded: 56.32(2.22e-16) 56.952 (2.22e-16)
[Galaxy S II Original Android Development] nobnut:
That wasn't a wink. You were looking at it's bottom.
[Galaxy S II Original Android Development] Hacre:
Read the damn thread.

I honestly don't see this issue with my phone and I've asked designgears he doesn't see it either. Is there an optimal way to make it stick out so I can reproduce?
[Galaxy S II Original Android Development] nobnut:
Confirmed, I don't see it either.

Maybe some of these will stop me missing out on this yellow craze.

EDIT: From what I have read, some handsets are predisposed to this. Hardware issue rather than software issue.
[Galaxy S II Original Android Development] veyka:
My eyes, they burn (i wrote something else here, but it was in bad taste :( )

Anyway, so far so good, screen scrolling doesn't have the annoying slight lag that it had on CF-root, no problems coming in and out of sleep.

So far A++ kernel, as described, would flash again. 5 stars.

ps I assume JIT is turn on in this? How would one check

I also dont seem to have any problems with anything being yellow, that shouldnt be.
[Galaxy S II Original Android Development] mach0boi:
There's thread in the general section discussing this. I can see it clearly when you pull the notification bar. You can see the yellow tint on the gray background. The left side is much darker especially the bottom part. I can see it also visibly when I'm typing using stock samsung keyboard. The leftmost side is yellowish. I don't know what CF did to his kernel but i really noticed the issue's gone when I'm on his.
[Galaxy S II Original Android Development] Hacre:
Well unless it's something in the initramfs CF didn't do anything to "fix" it, Samsung did, CF to my knowledge doesn't change anything in the kernel itself, it's from whatever stock ROM he pulled from (eg KG1). I'll try and reproduce then track down.

Thanks.
[Galaxy S II Original Android Development] schrickm5:
Fantastic kernel, running on Cognition 1.13, right now since the morning, am downloading 1.2 as we speak.

Undercooked the voltage by 50 on each step, may go further if no problems arise.

Phone is currently making a cup of tea, and its not even awake.
[Galaxy S II Original Android Development] mach0boi:
Thanks. I'm sorry for bringing such issue. I know it has been discussed in the general thread for so long now. If you have time, maybe you could look at it. Some of my sgs ii buddies are very affected on that yellow tinting issue. Although it isn't a big deal for me, I really want it to be fixed. I just find it weird because I also know cf didn't change anything to his kernel. But I can confirm that my yellow tint issue is gone/lessen. Thank you for your time :)
[Galaxy S II Original Android Development] veyka:
I pulled down my notification bar, I cant see any yellow in the gray! O-o
[Galaxy S II Original Android Development] mach0boi:
Better not discuss this anymore here mate :) there's a long thread in the general section with so many images proving it :)
[Galaxy S II Original Android Development] Yanardag:
Hi,

I found a bug... with the 1.1 kernel is no problems with

this site www.haberturk.com but with 1.2 closed the browser !!!

I dont know why? I think the kernel has a bug.
[Galaxy S II Original Android Development] canglan:
On Cognition 1.14 (1.1 kernel), watching a YouTube video for about 10 minutes and the phone rebooted... :(
[Galaxy S II Original Android Development] tonysac:
I tried it..I'm with 1.2, and it's working fine...

Cognition 1.3..may be it's something with your rom?

Sent from Galaxy!
[Galaxy S II Original Android Development] Yanardag:
I am on stock KG1 with 1.2 flash on...

Edit: now its ok...hmmm i think there was a problem on the web server of this page

now its ok.
[Galaxy S II Original Android Development] veyka:
My phone went to sleep and didnt wake up, and I cant do logs at the moment as the java JDK, its crashing my router everytime I try to download, so its coming down via my phone.

logs will arrive when java does.
[Galaxy S II Original Android Development] Hacre:
People that are having issues/crashes/sleep deaths can you provide your CPU speed settings/voltages please?

Thanks
[Galaxy S II Original Android Development] gee2012:
Random reboots

Good kernel but i`am having random reboots on 1.2.
[Galaxy S II Original Android Development] veyka:
Stock settings, I had only just installed setCPU.

All I had done is change the scaling to conservative.

using 1.2
[Galaxy S II Original Android Development] Mr_Q:
And the second sleep death, but now with v1.2.

I have not changed any voltages, I did install setcpu with standard values (200/1200) while I didn't have this installed with v1.0 when it happened.
[Galaxy S II Original Android Development] tonysac:
Cognition 1.3..oc to1600..ondemand ...everything else is untouched no problems till now...

Sent from Galaxy!
[Galaxy S II Original Android Development] roisagi:
has anyone tried this with LeoMar75 Rom?
[Galaxy S II Original Android Development] xan:
Kernel. Looks. Awesome!

I've seen that on your latest github you are adding support for VoltageControl, are those changes which will be released into the wild?

I find motivating to push the app a little further, SGS2 support is something great.

What interface you use to talk with SetCPU voltage tab?

I might just build an alternative, but need to know how to talk with it :D
[Galaxy S II Original Android Development] Hacre:
People experiencing random reboots and sleep deaths, I need logs or I can't troubleshoot...the OP outlines exactly what I need.

Also when it happens are you connected to charger, usb, or running on battery, etc etc.
[Galaxy S II Original Android Development] canglan:
Stock settings (didn't even have SetCPU installed).
[Galaxy S II Original Android Development] xan:
Not connected to charger, just flashed, launched SetCPU, oced to max... tested, some benchmarks (went well!) left to write a post.... checked back on device:

SOD.
[Galaxy S II Original Android Development] kalpik:
Hmm.. Just rebooted when typing a tweet using swype.. Let me remove all UV first and see if I can reproduce the reboot.
[Galaxy S II Original Android Development] veyka:
Running on battery(I think)

SetCPU installed

Running 1.2

Stock apart from I changed the scailing to conservative

I will leave my phone plugged in with logcat and kmsg running to see if i can catch it doing it.

Here are my logs:

http://www.4shared.com/file/v1ROoHDj/Veyka-logcat.html

http://www.4shared.com/file/5bQcWa0b/Veyka-kmsg.html

They are to big to upload to XDA :(
[Galaxy S II Original Android Development] KaliKot:
I was running 1.1 when the phone rebooted

Was on Cognition 1.13, no setcpu. I am plugged in and charging and it suddenly shut down
[Galaxy S II Original Android Development] Hacre:
Did these logs run right up until the crash?

Also, use zip or something! Text compresses very well and will then attach to the post, just FYI.

EDIT: If this runs right up to the crash I have an idea what might be causing it. Could do with a confirmation on if that log ran until the phone died though and a few other logs to compare it to.
[Galaxy S II Original Android Development] veyka:
Im afraid to say they where started after the crash, I dont normally have my phone chilling out connected to adb ;)

And tish and pish, common sense is not wanted here.

As a rule, should we wiped the cache and or the dalvik cache after/before each kernel upgrade, as the crash happened after i upgraded from 1.1 to 1.2 (not right after, like 15min. I wiped after moving from CF-root but not after upgrading.
[Galaxy S II Original Android Development] Hacre:
Oh I see. Well then those logs are pretty useless. The only way to troubleshoot a random death is for the death to happen while it's logging you see.

A wipe of dalvik -shouldn't- be necessary but like with all things, it doesn't hurt to try it if you're having problems.
[Galaxy S II Original Android Development] veyka:
Bugger, it would be good if android kept logs between boots :(

Ill wipe the dalvik, then leave it plugged into adb to see if it dies.
[Galaxy S II Original Android Development] Hacre:
adb shell cat /proc/kmsg > Veyka-kmsg.log is probably the most important once since it's related to kernel issues.
[Galaxy S II Original Android Development] nikzDHD:
Oh goody another kernel for me to try out :D Will flash and test.
[Galaxy S II Original Android Development] kalpik:
Ok, it just rebooted on stock voltages while the phone was just sitting on the desk doing nothing.. Wasn't connected unfortunately :(
[Galaxy S II Original Android Development] thegangsta:
I had a spontaneous reboot too while it was sleeping. I did a wipe after upgrading from 1.1. to 1.2 so it mut be something else. I have setCPU installed but all left at default values. No tegrak or anything like that. Sorry no logs done either.

This Kernel really looks promising. Keep up the good work!
[Galaxy S II Original Android Development] veyka:
Running, I bet it wont do it now ;)
[Galaxy S II Original Android Development] kalpik:
Yea, **** never happens when you expect it to happen :D
[Galaxy S II Original Android Development] EarlZ:
Some units are not affected, it may not be yellow in your perception but something like the left side is darker than the right, different units have difference intensity on the tints, theres a 140+ page discussion on it.
[Galaxy S II Original Android Development] veyka:
My phone just rebooted itself!

But the good thing, I have logz!

See attached
[Galaxy S II Original Android Development] kalpik:
YAY! You're our hero :D
[Galaxy S II Original Android Development] veyka:
I have never been more excited by my phone doing something wrong to be honest, I actually yelled "YAY I HAVE LOGS"

I need to go outside and re-examine my life now :D
[Galaxy S II Original Android Development] Hacre:
Marvellous, thanks for that. That's quite a crash in the kmsg log! I'll start debugging.

In the meantime, I've updated the OP with version 1.4 and as it goes one of my guesses -might- have been on the nose, judging by the quick look at your log. Give it a try, see if the issue goes away.

Thanks!
[Galaxy S II Original Android Development] veyka:
I will update and hook my phone back into its logging life support!

Thanks ;)
[Galaxy S II Original Android Development] veyka:
Another lockup+reboot

This time with 1.4

I did not wipe the dalvik cache this time.

Logs attached
[Galaxy S II Original Android Development] nightranger73:
Please don't use conservative governor. On market description of setcpu it's written that conservative may prevent phone from waking up

Edit:

From market description of setcpu:

Sent from my GT-I9100

If you find this post usefull please press the "Thanks" button
[Galaxy S II Original Android Development] Annihlist:
So far so good :-) no lock ups 1400mhz in SetCpu with stock voltages :-) been running for 3 hours :-)
[Galaxy S II Original Android Development] veyka:
Okies, I swapped over to ondemand.

Still logging and will see what happens.
[Galaxy S II Original Android Development] nikzDHD:
So far so good as well for me, no lock ups no reboots running v1.2, flashed via CWM Recovery did wipe cache and dalvik. Maintaining on stock voltages & ondemand stock will leave for 24 hours before playing with voltages. :)
[Galaxy S II Original Android Development] kalpik:
No reboots so far with 1.4 here!
[Galaxy S II Original Android Development] EarlZ:
Are all the lock ups related to CPU overclocking or under volting ?
[Galaxy S II Original Android Development] Hacre:
Just had my first reboot so there's definitely something off. I appreciate the feedback I'm getting on this folks and thanks for your patience. :)
[Galaxy S II Original Android Development] kalpik:
No.. They are not.. The phone was rebooting even on stock voltages..

1.4 hasn't rebooted on me so far..
[Galaxy S II Original Android Development] Hacre:
Ok I'm gonna grab a few hours sleep (been up all night with this, it's now 1:30pm here). If I'm not back before, netarchy should be around and I'll leave him a message to make sure he sees this thread.

Keep the feedback up folks and thanks for helping to track this issue down.
[Galaxy S II Original Android Development] kalpik:
Thanks! The kernel is no doubt the best out there.. Have a good night's sleep :)
[Galaxy S II Original Android Development] veyka:
Cheers mate, ill keep logging with the changed CPU governor and ill post up logs if the problem keeps happening.

Nope, not touched voltages or clocks.
[Galaxy S II Original Android Development] Nebucatnetzer:
Nice to see you netarchy loved your kernel on the Nexus S

Greetz Nebucatnetzer
[Galaxy S II Original Android Development] blu3angel:
Quadrant test is not very high with v1.4... Set at 1600mhz I'm only getting about 3700+ with Ondemand profile...

Edited: Just got my 1st reboot after 3 hours using v1.4.. Governor set at ondemand 1600mhz max and 200min.. No other profiles was setup..
[Galaxy S II Original Android Development] veyka:
The really really high Quadrant scores use a scrip to load the benchmark into a ramdisk to cheat on the disk benchmarks and thus the total score.
[Galaxy S II Original Android Development] elrazerx:
Installed via the zip file .tar does not work for me

Control voltages works fine

Thanks for this kernel
[Galaxy S II Original Android Development] geistteufel:
Wow, so perfect, flash with cwm, custom voltage with setcpu, work perfectly, bravo!
[Galaxy S II Original Android Development] aussiebum:
That's interesting. I've been using Conservative governor is every single kernel that I've flashed on my SGS2 and none of them have had sudden reboots/SOD's etc that *weren't* related to undervolting.

I'm still using Ninphetamine 1.0 atm (flashed via CWM) and so far (1hr 22mins) I've experienced no sudden reboots, SOD's or lockups. The cpu is -25mv undervolted on all cpu clocks up to 1200mhz but not overclocked via SetCPU. Didn't even bother clearing the cache or dalvik either.

The only issue I've noticed so far is my phone lost signal twice within the space of about 20mins, which is unusual because it almost never happened with the Cognition 1.12 kernel.
[Galaxy S II Original Android Development] geistteufel:
Could you add interactive and smartass governor?

I have 7650 with cfbench and I don't go over 1400, to hot otherwise.

I love this kernel
[Galaxy S II Original Android Development] nikzDHD:
Ok I've had my first reboot, got a whatsapp message, but then tried opening dropbox and boom restart.
[Galaxy S II Original Android Development] Pacifiste95:
Post your log files
[Motorola Droid 3] shad0wdawg:
Since the 12th, I have been trying to find an unlock for the phone, and stumbled upon a seller who goes by Swiftunlocks. He has provided excellent service, and his unlock code for the Droid 3 works 100%. I would recommend his service to anyone who wishes to have their phone unlocked. He charges a fee, but he's also the only one around to unlock phones for people who aren't with Verizon.

If you go on eBay and search this

verizon droid 3 unlock

You can find his services :) His support was excellent as well because even when out of business hours, he sent me my unlock codes minutes after paying.
[Motorola Droid 3] raydm:
But i dont think we can use this phone here in us with gsm even after unlock.
[Motorola Droid 3] CLB-NL:
And why shouldn't GSM work after an unlock in the USA, you think?
[Motorola Droid 3] bsweetness:
The T-Mobile and AT&T bands are locked out, even with the SIM slot unlocked. Verizon does this with pretty much all of their global Android phones. It's presumably because they're the exclusive carrier for them in the US, so they don't want anyone being able to use them on another major US carrier.
[Motorola Droid 3] CLB-NL:
Hmm weird stuff out there in the USA =)

And if I buy a Droid 3 in the USA, buy an unlockcode and unlock this Droid 3.

Can I use it on GSM-network here in Europe (the Netherlands) or isn't that possible?

Here we also have T-Mobile as a provider, will that work? And Vodafone? That's what I have...

I'm gonna start a topic here on XDA about the best 'version' of the Droid 3 for using in Europe / The Netherlands. You have the Motorola XT883 version in China, you have the Droid 3 version in the USA and there is the Motorola XT860 4G in Canada..

But that's offtopic, I'm gonna start a new thread about that!
[Motorola Droid 3] shad0wdawg:
I'm not an expert at this, but they should work if the bands are the same. They locked out the AT&T bands on the Verizon Droid 2, im not sure about the droid 3.

pocketnow.com/android/verizons-droid-2-global-locks-down-att-bands-stateside

Droid 3 supports - All–Digital, 800/1900, CDMA EVDO rev A and GSM 850/900/1800/1900 UMTS

Found on -

verizonwireless.com/droid-3-motorola.shtml

Droid 3 will work on FOREIGN sim cards when unlocked, but will not work on AT&T USA and T-Mobile USA. I read somewhere that they are making a Droid 3 or something similar for AT&T though. I left links, from where I found this information if you would like to see for yourself :)
[Motorola Droid 3] nhtu:
DROID 3 - Will my phone work using other GSM SIM such as AT&T or T-Mobile in the United States?

Will the Droid 3 work using other GSM SIM such as AT&T or T-Mobile in the United States?

Your phone is designed to be utilized with the pre-installed SIM card. You will need to enable international roaming AND activate your pre-installed SIM card in your phone when traveling outside of the U.S.

The GSM and UMTS bands that are supported in Droid3 Global will not work in the United States. The GSM and UMTS bands are only able to be utilized outside the U.S. A GSM SIM card such as AT&T or T-Mobile will not operate in the U.S.

Contact Verizon Wireless for more information dial *611 from your cell phone or call Verizon Wireless @ 800-922-0204.

Note: GSM and UMTS-based global services work only with SIM card supplied by Verizon Wireless® or by another non U.S GSM or UMTS service provider. When you set your phone to use a GSM 900/1800 or UMTS 2100 network, you may be prompted to enter a subsidy code. To get this code, contact Verizon Wireless.

From Motorola

https://motorola-enterprise.custhel...ing-other-gsm-sim-such-as-at&t-or-t-mobile-in
[Motorola Droid 3] xstrike9999:
I need to know if the phone will be unlocked for International use if bought from the Motorola store.
[Motorola Droid 3] rweb:
I can tell you in about one week...
[Motorola Droid 3] xstrike9999:
I will hold you to that then. A week it is...
[Motorola Droid 3] bsweetness:
No, it won't be.

If it has the Droid 3 name (which means it's the Verizon version of the phone), the SIM slot will be locked regardless of where you buy it. Some versions released in other countries (like the XT860 4G in Canada) may or may not be SIM locked. That remains to be seen. But anything called the Droid 3 will be SIM locked out of the box from any retailer, even Motorola.
[Motorola Droid 3] CLB-NL:
An unlockcode will cost you about $30,- so that isn't a problem
[Motorola Droid 3] rweb:
I suppose it will be locked, too, but I'm not sure. On the Motorola store site, nowhere Verizon is mentioned -- moreover, when needed, they generally refer to "your servive provider". And nowhere anything is said about a locking, not even in the "Product Disclaimer" link.

I will eventually know when I got the phone. Of course I'm prepared to pay $30 for unlocking, but if I have to, I'll write a complaint to Motorola. :-)
[Motorola Droid 3] xstrike9999:
Could someone please provide a link to a reliable service for unlock codes. I couldn't find anyone on Ebay with the name swiftunlocks...