yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] migueloma:
Kernel is perfect but is there anything for leds notification?

Its important for me

Thanks

Enviado desde mi GT-I9000 usando Tapatalk 2
[Galaxy S I9000 Android Development] kasper_h:
You can use the stock LED notification of your ROM. BLN has not been included (and will not be included).
[Galaxy S I9000 Android Development] kasper_h:
Small update version 0.39

Differences to the 0.37 in OP:

-less modules (only the six modules which are part of the stock kernel/stock ROM)

-module cleaning step during the install procedure (based on lippol's cleaning script)

Download:

https://dl.dropbox.com/u/69000552/Mackay_kernel_0.39.zip
[Galaxy S I9000 Android Development] kasper_h:
Just a small update :)

I'm currently working on the OC code again. My previous OC code implementation worked for some people, but for my phone it was unstable (my phone does not like OC at all, so I have a bad phone to develop OC for - on the other hand, if it is stable on my phone it will probably be fine for other users as well :)). But my most recent trials are much more stable. Still had a BSOD once, but not nearly as frequent as before. Difference is that I don't add any UV code, just fixed voltages for different frequency steps.

BTW for a different project, I was adding live OC to my mackay kernel. And this is actually very stable, running for a day now without any issues, even though it has voltage adjustment, so if implemented correctly, it should work :)
[Galaxy S I9000 Android Development] chiwou:
To be honest, I don't miss it at all :)

It's much smoother than most kernels with OC.

BUT if you implement the feature, would be happy to test it. With others I could overclock at 1200. And it was stable, even on very hot days.

Thanks for the kernel

Take care

-Chris
[Galaxy S I9000 Android Development] kasper_h:
Thanks. I am also not a big fan of OC...but some people seem to "need" it.

And for those, there is a new test kernel attached to this post. It has both custom voltage, liveOC and regular OC on top of version 0.39.

Download: <<REMOVED FOR STABILITY REASONS>>

To adjust custom voltage/liveOC you can use e.g. NSTools

To adjust regular OC you can use CM9 Settings>Performance.

Any people that would like to have Aroma filemanager in recovery?
[Galaxy S I9000 Android Development] GreenSGS:
First of all great work on kernel.I am now using Blueberry ROM which has your kernel. It works great but I get a strange screen Flickr more noticeable while opening white background apps. It's there for a moment. It's like pieces of apps joining....hmmm difficult to explain. Do you know if it's governor related or something in kernel or may be ROM? Do you also notice it?

I remember asking same thing in semaphore thread long time back but later it was reduced with ondemand smooth ui.

Again kudos for great work. Thank you.
[Galaxy S I9000 Android Development] chiwou:
File manager could be useful if no PC is available :)
[Galaxy S I9000 Android Development] kasper_h:
I have read about it quite some time ago but never noticed it myself. Seems to be a phone-specific issue....so it is hard for me to solve if I don't notice it. I would try a different governor first to see whether that helps.
[Galaxy S I9000 Android Development] chiwou:
Just testing the OC, now everything flies ;) everything is really fast

Great work

Do you compile the kernel with the linaro tool chain?
[Galaxy S I9000 Android Development] kasper_h:
Yes, the July version of Linaro + O3 optimizations.
[Galaxy S I9000 Android Development] chiwou:
Okay have to edit my review :)

After 20min of testing (texting, surfing, tapatalking ;) had a black screen and couldn't do anything anymore, had to remove the battery.

Maybe you should look at the glitch kernel, stablest OC for me so far.

Thanks for your work
[Galaxy S I9000 Android Development] kasper_h:
I just had a BSOD as well.

One day using liveOC without any BSOD.

So I guess the problem is in the regular OC code.
[Galaxy S I9000 Android Development] GreenSGS:
Same here BSOD in 5 min. On regular OC.
[Galaxy S I9000 Android Development] kasper_h:
Here is a new version, in which the regular OC has been reverted. So this one has liveOC + customVoltage (both can be set through NSTools):

https://dl.dropbox.com/u/69000552/Mackay_kernel_0.41.zip

I'm not yet sure this will be part of future Mackay Kernel releases...as I don't like the need for apps to set kernel options...

Download: https://dl.dropbox.com/u/69000552/Mackay_kernel_0.41.zip
[Galaxy S I9000 Android Development] chiwou:
Will test it later, it's 10pm now, time for the daily star trek dosage ;)

Take care bye bye now
[Galaxy S I9000 Android Development] kasper_h:
Watching olympic games now :)
[Galaxy S I9000 Android Development] chiwou:
Always watch it in the late afternoon, the 100m sprint was impressive

Just tested the new version, didn't last :) After 2min BSOD, well maybe next time

So good night

-Chris
[Galaxy S I9000 Android Development] kasper_h:
What OC value did you use?

For me regular OC is very unstable, but live OC at 110 works quite well and feels better than 1200MHz....
[Galaxy S I9000 Android Development] ddd613:
When I try unlock, freeze whith black screen. Used live OC 120%, 110% as usual with other kernel.

At live oc phone never use the lower Hz.

Sent from my GT-I9000 BlueBerry ICS with Mackay
[Galaxy S I9000 Android Development] sUsH667:
thx once again for your awesome work!

regarding extra-app for kernel-settings: what about the possibility of a init.d-script to set the needed values? mackay-kernel could ship such a script with standard-settings included and the user could change it to his needs if wanted. shouldn't be too difficult cause it mostly is "echo VALUE > /PLACE/OF/FUNCTION" to set the most stuff, so that an init.d-script should definitely be possible. and it would be a real good alternative to an extra-app, cause it would work out of the box with standard-settings, but is customizable, too.

greetz,

sUsH
[Galaxy S I9000 Android Development] kasper_h:
Which kernel you used before? It may be related to voltage...

Which governs do you use?

LiveOC should only change the frequency-values, but which frequencies are used (more).

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] ddd613:
Used before mackay 0.39

Used max. Freq 1000 with oc 120, 110 didn't changed the voltage

Govenor wheatly with deadline or sio

Worked fine, problem only when I try unlock

Sent from my GT-I9000 BlueBerry ICS with devil3
[Galaxy S I9000 Android Development] kasper_h:
Could you try with another governor. For me, SmartassV2+OC 110% works fine.
[Galaxy S I9000 Android Development] ddd613:
Ok I'll send report till late afternoon.

Sent from my GT-I9000 BlueBerry ICS with devil3

---------- Post added at 09:37 AM ---------- Previous post was at 08:43 AM ----------

Seems smartassV2 better to live OC, but had to add more voltage ( +25mV ) at every freq.

I think the reason of freeze at unlock is low voltage at lowest freq. too.

You shoud make a normal OC version, at this case don't need to up voltage at all freq. only at max.

I had never problem with normal OC.

I don't prefer OC at all freq., as live OC does.

Live OC crash at 120%, 115% even if voltages are higher.
[Galaxy S I9000 Android Development] chiwou:
I used 114, works well with semaphore, devil, glitch

FYI: used Wheatley

Normal OC 1200 stable in semaphore, devil

1300 in glitch

1140 in midnight (not exactly OC, though)

My idea was just that you just copy the OC features from Glitch, with the automatic voltage settings, my guess the wrong voltage settings is causing the BSODs in your kernel

Or is just too hard to implement it with Wheatley governor?

Well as I said before, everything works great. With Wheatley everything is really smooth, OC would just be a great bonus.
[Galaxy S I9000 Android Development] kasper_h:
I am actually thinking to remove OC completely. Although it is nice, it also adds instability (I also had instability issues with stock CM7 kernel with regular OC code back in the days). And I want the Mackay kernel to be as stable and simple as possible. And if OC decreases stability, it should not be in :)

I have also looked at Glitch's CM7 kernel, which had different leakage version to increase stability of OC for different types of phones/chips, as phones are all slightly different. This is a basic problem of any OC implementation.

And in the end, I also don't feel an enormous performance increase with OC, so I doubt it is worth the effort at all :)
[Galaxy S I9000 Android Development] kasper_h:
I have previously implemented the code of Midnight in my kernel. It worked, but had some stability issues.

Like I said above, I also looked at the Glitch kernel. It is not that easy to copy his code, but I'll give it a try. But it will be my last try at OC, if it doesn't work I'll stop trying.

I will also take a good look at the voltages Sema&Glitch are using for liveOC, maybe I use slightly lower values to start from.

I also don't know how well Wheatley handles OC at all.
[Galaxy S I9000 Android Development] Rimmer1966:
Not that my opinion counts for anything but I agree with you, there are already two kernels that satisfy those who like playing around with settings, the thing that sets this kernel apart is that it's quick and stable out of the box without the need for scripts or separate apps. I for one hope it stays that way..
[Galaxy S I9000 Android Development] kasper_h:
Thanks. My original idea for OC was to have a clean implementation which would mean no OC for people how did not change any settings, and only a choice in CM9-settings for a higher max frequency, with no additional settings (so basically the same type of OC implementation the stock CM7 kernel had). That would be fine with me. Any more complicated implementation does not fit with the philosophy of the kernel :)
[Galaxy S I9000 Android Development] sUsH667:
and it would be totally sufficient to have just one (1140mhz, or maybe two 1100 and 1200mhz) normal-oc-options, i think.

i have one question: if oc of any kind makes the kernel unstable, how do semaphore,devil,midnight,etc achieve oc and stability? don't they use the same kernel-base (pawitp's) you use, too?

greetz and thx for all the effort you put into this (and your rom and older kangs, of course)!!!

sUsH
[Galaxy S I9000 Android Development] DerTeufel1980:
There is no automatic voltage setting in glitch kernel. Only stratosk uses this for liveoc above 110%.

Also feel free to take some code from me. I have made some changes to the pll freq. Normally the pll only changes, when previous freq was above 800 mhz or actual freq is above. This is not working very well, because the detection sometimes failes and then the freq is getting wrong pll.

Ezekeel has modified this a bit, to avoid this. I have modified the code more, to be independent from fixed levels as 800 mhz for example. My code is checking, if the pll needs to be changed and changes it then, or not.

edit: you also could take a look at the oc code which was implemented to pawit kernel for about two days. it wasn't working, because the apll was not set. if you do set this correctly, the code also should work

edit2: add this to the apll config at the beginning:

#define APLL_VAL_1200	((1 << 31) | (150 << 16) | (3 << 8) | 1)

and for less confousing: fix this line:

/* OC0 : [1000/200/100][166/83][133/66][200/200] */

it has to be 1200 instead of 1000. this is just an information about the code below, but could be confusing if you look at it later.

edit3: another issue in the code from pawitp's kernel:

if (index <= L0)

__raw_writel(APLL_VAL_1000, S5P_APLL_CON);

else

__raw_writel(APLL_VAL_800, S5P_APLL_CON);

at this point you need to edit the code to switch to __raw_writel(APLL_VAL_1200, S5P_APLL_CON);

if index == OC0

and:

if (index == L0)

__raw_writel(APLL_VAL_1000, S5P_APLL_CON);

edit: this is the last part fixed:

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] kasper_h:
This is exactly what I did yesterday to add OC to my kernel, I used the cm10 code + prevented the errors in the code which you also pointed out in your post (the commit is in my github).

Edit: I now see one mistake I overlooked: the /* OC0 : [1000/200/100][166/83][133/66][200/200] */ should have been [1200/200/100]

Should the code at the bottom of your post be:

if (index == OC0)
__raw_writel(APLL_VAL_1200, S5P_APLL_CON);
else if (index == L0)
__raw_writel(APLL_VAL_1000, S5P_APLL_CON);
else
__raw_writel(APLL_VAL_800, S5P_APLL_CON)

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] androkurd:
Where can I download version 0.39? In this thread there's only a link to version 0.37 but in Mackay's ROM thread there is version 0.39 but I can only download the entire ROM not the kernel itself. Thanks
[Galaxy S I9000 Android Development] DerTeufel1980:
Sorry, did not look at your github. The one you overlooked is just cosmetic

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] kasper_h:
http://xdaforums.com/showpost.php?p=29723231&postcount=147

I know it is cosmetic. I'll take a look at your OC code tonight. I tried it before, but didn't get it to work (trying to disentangle the liveOC from the staticOC :)).
[AT&T Samsung Galaxy Note I717] P-Men:
I'm getting this dead spot on my screen that appeared out of nowhere and it's starting to annoy me real bad. It only affects the s-pen for some reason. I can touch the spot with my finger and it works normally.

Has anybody else experience something like this?

Here's a screenshot showing what were supposed to be lines.

Notice the white spot to the right?

What could be going wrong?
[AT&T Samsung Galaxy Note I717] theROMinator:
Reboot and try the S-Pen test for me, please.

*#0*#

Also, if you have some sort of magnetic case, that may be the problem. It's a known issue.
[AT&T Samsung Galaxy Note I717] P-Men:
Thank you for taking your time to help me!

Here's the S-Pen test thing.

Don't know if I'm doing it correctly.

Is that what you were looking for?
[AT&T Samsung Galaxy Note I717] DarknessTM:
Could you try another pen?
[AT&T Samsung Galaxy Note I717] theROMinator:
Yup, do you have any sort of case/protector on it?

Have you dropped it or pressed that area too hard?

Try removing all accessories.

Other than that, if the problem still persists, definitely contact Samsung.
[AT&T Samsung Galaxy Note I717] erick161:
Is the screen scratched? My screen protector is scratched is sometimes messes up right at the scratch.
[AT&T Samsung Galaxy Note I717] rangercaptain:
@P-man:

Hey, you should reply back unless you died. Your reply helps hundred's others with the same issue.
[Galaxy S III Q&A, Help & Troubleshooting] rossm1873:
hi, im just wondering if checkrom has many bugs and is it stable enough to use as a daily rom?

also what is the battery life like as im on stock rom just now and i would lile the battery life to be atleast as good as stock

thanks
[Galaxy S III Q&A, Help & Troubleshooting] rossm1873:
because id rather see if there's any issues instead of wasting my time
[Galaxy S III Q&A, Help & Troubleshooting] bala_gamer:
Instead of wasting the time by creating this thread you could have easily read the feedback in CheckROM thread.

《tapatalked from galaxy s3》
[Galaxy S III Q&A, Help & Troubleshooting] norpan111:
Yeah why do you expect users to waste their time to answer your thread if you can't even bother to do some reading yourself? It's like standing in a red light and ask the car beside you like "dude.. Is it green yet? I don't want to waste my time to look.." you would do that? Or sitting in a restaurant and ask the table side of yours if it's any good because even if you have the plate with the exact same food on yours.. You are to lazy to just try?
[Galaxy S III Q&A, Help & Troubleshooting] ehalai:
Lol...
[Galaxy S III Q&A, Help & Troubleshooting] Mr. Droid:
Lmao nice, well said good sir
[Galaxy S III Q&A, Help & Troubleshooting] Mr. Clown:
Thread locked.
[Galaxy S III Q&A, Help & Troubleshooting] yana209:
Hi

Just got my S3 yesterday and I tried setting my my corporate mail on it. The account is set up fine but right after it finishes the settings it shows "Error connecting to server (<mailbox name>). I have stock rom and I am using stock email client.

Other clients works fine.

Thanks.
[Galaxy S III Q&A, Help & Troubleshooting] PLIYAN:
i9300 Mailbox Connection Error

View attachment 1264495

View attachment 1264496

This is the 3rd i9300 where I am setting up corporate email, it went very well on the first 2, on the 3rd one, no way, I get the following warnings.

I did the following steps:

1. Removed the ActiveSync account from the phone

2. Access Baha's Exchange 2010 mailbox via OWA then click on 'Options->See All Options->Phone->highlight the Samsung entry then press the X to delete the association.

3. Launch the Outlook application that is configured to synchronize with the mailbox by clicking on Start->Run then typing the following and press Enter (note: Outlook's AutoComplete offers suggested email addresses to use from previous correspondences - this is what will be cleared):

outlook.exe /CleanAutoCompleteCache

and although I don't get anymore the security update warning, I am getting "connection error" and "error connecting to server"

It is a brand new handset, not rooted
[Android Q&A, Help & Troubleshooting] Techno79:
One of the applications I have installed is creating an Internet shortcut on my home screen that takes me to some online app store at http://partners.handago.com/smartphone/home.jsp?siteId=2790&androidid={really long number}. I have attached the shortcut icon to this post.

Any applications that chooses to do this is extremely bad and I would no longer use the application. It is even worse than those applications that put adverts into the notification bar.

I do not know which application it is but it keeps creating it every so often (may be once every few weeks). I have no idea how to find out which application it is, does anyone have any suggestions on how I can find out?
[Android Q&A, Help & Troubleshooting] ServeTT:
Try to install app, that control access to internet, and find the bad app in log, also you can try to find it in settings - applications, I think this app will be recognized with you in a first attempt.
[Galaxy S I9000 General] hippopig:
Has anyone had problems and had to change their home button?Mines really unresponsive (even on standard roms so its not a software issue)you have to press it really hard to make it work....and idea where to get one?eBay i guess.......also while im at it my rear cover has split too so is it ebay for that too?
[Galaxy S I9000 General] Manvendra05:
Which phone are you using ?
[Galaxy S I9000 General] hippopig:
sorry sgs gt-i-9000
[Galaxy S I9000 General] lani100:
you can change it but you will need to change the whole bottom button frame it's not that hard to do but you need to take the screen off and that can be a little tricky
[Galaxy S I9000 General] Pezmet:
Just take it to warrany if you still have it and they will replace it for free. You can find videos on youtube about how you cand do this your self but take care takeing off the screen may leave dust under it if not proper mounted so mabye check at an official service for how much it costs.

Best of luck
[Samsung Galaxy Nexus] Damian8a:
Does anyone know how to put the G Nexus Jelly Bean in Diagnostic Mode, like for flashing it for another carrier, you know, QPST, and all that stuff.

I really need it, like 2 weeks ago i bought a GN and its f*cking awesome, just flashed Jelly Bean, and i cant get it into DIAG Mode.

By the way, ,the following doesnt work:

*#*#8778#*#*

*#*#DIAG#*#*

##DIAG#

##8778#

Anything else?
[Samsung Galaxy Nexus] JaiaV:
Have you tried the default Android testing menu?

*#*#4636#*#*

*#*#INFO#*#*
[Samsung Galaxy Nexus] Damian8a:
Ok, I flashed the Cyanogenmod 9.0 and the *#*#DIAG#*#* actually worked, i get into the menu that let me select between PDA and CDMA MODEM conection.

BUT!! It kinda doesnt connect like a Samsung Modem or anything like that, it shows me two new devices in the Device manager:

1) In the modems it shows a "VIA Telecom USB Modem"

2) In the Other devices shows "INTF2"

And when I try to connect it to DFS or QPST it doesnt work.

Im shure i need some drivers or something, but i dont know which ones.

Any clue?
[Samsung Galaxy Nexus] JaiaV:
Oi, hit thanks instead of reply. O well.

I doubt you'll be able to 'flash' the phone for any other carriers through any menu available through the device itself, if that's what you're intending to do.
[Samsung Galaxy Nexus] Damian8a:
Well Its just matter of changing the MSL and the PRL and modifiying the Data parameters and sh*t like that.

And Ive done that like a thousand times with several HTC's Samsungs and Motorolas(Thats actually my second job, seriouslly, i get paid for doing this), I just need to connect it in diag mode and have the drivers.

Which is beeing really hard to do right now

Obviously using my laptop to change the parameters
[Samsung Galaxy Nexus] marjohn1000:
Same problem

I have been struggling with the same problem for 2 weeks. Have any one found an answer. Can use 'better cut' to write prl, however can use qpst to make internet work.
[Samsung Galaxy Nexus] Damian8a:
Uhh, Well I found an answer, but its not a solution yet.

Check out this thread http://xdaforums.com/showthread.php?t=1696621

It explains why we can't use QPST...

Well it actually doesnt dierctly explain, but we have VIA Chpisets on our phones, instead of the common Qualcomm Chipset, who owns QPST.

But it also give some instructions about a program for VIA chipsets, ETS i think.

I was also reading in a Droid Charge thread (also VIA chipset) that there is a programm named VPST and VPCT or something like that, its like the "QPST" of the "VIA telecom" chipsets.

I'll try it tonight.

Is your gnex Sprint or Verizon?
[Samsung Galaxy Nexus] marjohn1000:
Have you tested? Did you get it working? I tried but 'getprop' not showing my MSL code.
[Samsung Galaxy Nexus] Damian8a:
I've just made the MSL change to 000000, and switched the PRL to my carrier, but just that. I havent had time to work on anything else.

Is your nexus Verizon or Sprint?

If its Verizon your MSL is already 000000, if its Sprint you can get the MSL code with a script made by Viperboy
[Samsung Galaxy Nexus] marjohn1000:
I have a Srint. Searching for ViperBoy now.
[Samsung Galaxy Nexus] jaron7_11:
has there been more progress on this? would love to update prl on cm10
[Samsung Galaxy Nexus] Damian8a:
Dont know man, I dont have the Nexus anymore, but for the PRL updating theres an app that makes shortcuts, I cant remember the name right now, i think it something like bettercut or something like that.

You can also flash an ICS rom and update the PRL like you would normally do.

Hope i helped
[HTC One X] esapekka:
I recently installed Android Revolution HD 7.1.0 on my HTC One X and got stuck in a boot loop. I have tried getting out of the loop by emptying the cache, but it hasn't helped.

Now I'm trying to recover my phone using ClockworkMod Recovery v5.8.2.7. The problem is that my recovery folder name contains spaces, so I'm getting the "MD5 mismatch!"-message.

So my questions are:

1. Is there some way for me to rename my backup file?

2. If not, can I transfer another backup file from my computer to my device when in ClockworkMod Recovery or fastboot?

3. Is there some other way to get out of the boot loop?

I need to go to work in an hour so I would really appreciate quick answers! Thanks!
[HTC One X] esapekka:
Typical. I search for a solution for 2 hours without luck, and as soon as I post a thread I find a solution. Well, here it is for future reference:

http://xdaforums.com/showthread.php?p=25557817#post25850720

EDIT: The solution answers the questions 1 and 2.
[HTC One X] B055M4N:
usually wiping dalvik cache solves most boot loops.
[HTC One X] forumhookersdotcom:
Flashing the boot.img of the respective Rom will surely recover from bootloop.