yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] XpLoDWilD:
Hi there,

This is a development thread.

Don't ask for ETAs. Don't ask what's working. Don't ask how to use.

It is not yet in an usable state.​

This is an attempt to make a homemade 3.x kernel for our beloved Galaxy S II. I'm targetting the GT-I9100 only for now, if you wish to get it running on other variants (I9100G for instance), feel free to port it to your device and do a pull request.

I started it off Origenboard 3.0.4 kernel patched to 3.0.24, so that we get the most up-to-date opensource drivers, removing the need of porting Samsung drivers from 2.6 (gingerbread) kernel.

We'll be able to merge proprietary stuff from Samsung when they release it (audio and modem mainly), but thanks to what we'll already have we'll have a proper 3.x kernel without any Samsung crap (such as their MTP implementation that is borked it seems).

http://github.com/xplodwild/android_kernel_samsung_galaxys2

Keys GPIOs

Regulator and battery (it loads well but Android doesn't show it's charging)

Screen/framebuffer

Touchscreen

MFC (untested but should work from Origen)

RTC Clock

Touchkeys

Phone never wakes from deep sleep (<== We definitely need experts on this one)

ADB works only after unplugging and replugging USB cable (issue almost located)

Well, start forking, do stuff and make pull requests so I merge it and everyone enjoys. I'd need some help for the major issues above (especially the deepsleep issue).

If you're not a developer, well, buy me a coffee, there's a donation button on the left of this post :)

I'll keep you informed when it'll be ready for "public" use.
[Galaxy S II Original Android Development] Entropy512:
Phone never wakes from deep sleep

cpufreq is stuck at 200Mhz in ondemand governor

My guess is that these might be connected - or does conservative work?

Our device becomes very unhappy if it enters suspend when the regulators aren't set high enough to support 200 MHz.

As an experiment - if you set the default voltages for 200/500 to match 800 and it fixes things, that's the problem. If it still breaks - it's something else and I have no clue what.
[Galaxy S II Original Android Development] pulser_g2:
I was just thinking that :) Iirc it puts the device into 800 when waking, or something like that...
[Galaxy S II Original Android Development] XpLoDWilD:
I had the same issue when I haven't enabled the governors, so the CPU was stuck at 1200MHz but won't wake up either from a deep sleep.

I'll have a try with the voltage, but my guess is more that there's some steps missing (the default 2.6 kernel seems to have a "low power mode" in which the board gets before waking up, if I understood it correctly).

At the same time, I'm giving a try with the 3.3 branch at Linaro (check android-3.3 branch at my github). It's harder than 3.0 because there's no more s3c framebuffer, it seems to go directly to FIMD, and the LCD panel has to be setup through SPI.
[Galaxy S II Original Android Development] XpLoDWilD:
Some update:

- Touchkeys, clock and various things added/fixed

- Patched to 3.0.24 :)

Edit:

- Added sdcard mounting

Cool stuff should come very quickly ;)
[Galaxy S II Original Android Development] sam razzy:
Good work...

---deleted some post----

Sorry u can delete this post as it making thread very ugly.. :D

_____________________

Sent From My Phone
[Galaxy S II Original Android Development] luexi:
just buy u a expensive coffee! Work hard!:D:D
[Galaxy S II Original Android Development] iamnotkurtcobain:
Yeah do you smell sources? :)
[Galaxy S II Original Android Development] XpLoDWilD:
We'll do our best without them.
[Galaxy S II Original Android Development] Try4Ce:
True enough.

This kernel is the most exciting thing I'm watching lately.

Really excited about the outcome. Samsung Kernel is just not the way to go if you get an alternative like this, which is far more promising.
[Galaxy S II Original Android Development] Try4Ce:
Here comes your coffee:

33P346290U8160844

:) Keep it up!
[Galaxy S II Original Android Development] sam razzy:
Before your release ... Samsung Released their open source kernel.. guys Congo.. will wait patiently for your kernel... ;) Thank you.. love u Dev
[Galaxy S II Original Android Development] peterperfect:
he already know it...pretty sure xplod and codeworkx will bring some state of art kernel to us ;)
[Galaxy S II Original Android Development] XpLoDWilD:
Samsung kernel is really dirty : A lot of hacks, outdated drivers, ... The Samsung way, just the same they do with Android (adapt mainline code to their stuff, instead of doing it the other way...)

But we're going to bring everything to a clean 3.0 or 3.3 base soon ;)
[Galaxy S II Original Android Development] iamnotkurtcobain:
Isn't 3.3 bleeding edge? ;)
[Galaxy S II Original Android Development] endursa:
awesome, man

despite not owning a sgs2 I like your work! Samsung should definitely review their way of development, way cook your. own soup, when it. Is. already done by someone else :-)

they should just stay compatible and release the damn hardware drivers ;-)
[Galaxy S II Original Android Development] Entropy512:
What is your definition of "clean"? - since a "clean" 3.0 mainline can't run Android at all, and a "clean" 3.3 can barely run it.

I'm still wondering why you renamed mach-exynos back to mach-exynos4 - you complain about outdated drivers, but you revert progress in the CM codebase? https://github.com/torvalds/linux/commit/830145796a5c8f1ca3f87ea619063c1d99a57df5 (The aforementioned commit was part of the transition from 3.1 to 3.2 in mainline.)

Edit: Some of Samsung's drivers are clearly full of ugly hacks and need major work. However, an automatic judgement of "it's different, therefore it must be old" is clearly not appropriate - it has already led you to make the mistake of "fighting the future" and taking the mach-exynos codebase backwards, when all of the evidence says that in the case of mach-exynos, "different" means "much newer", not "older".
[Galaxy S II Original Android Development] XpLoDWilD:
Clean, meaning a clean 3.0 with Android additions in it.

If you take Samsung 3.0.15, there's not much files (if you exclude mach and specific drivers) that looks like "clean" 3.0.15, which causes a LOT of troubles if you want to patch it up.

In mainline 3.0, it's mach-exynos4. It's renamed mach-exynos afterwards. Samsung had BOTH, with duplicated files which could lead to thousands of headaches when patching and doing stuff too.

Take Samsung max8997 driver, it's clearly 2.6 one. Mainline got a different implementation, not much complete as of 3.0 unfortunately (MUIC missing for instance).
[Galaxy S II Original Android Development] Entropy512:
Makes sense, although unfortunately, some things are clearly backports of newer code, see below.

Not sure what codebase you're looking at, but in the I9100 source drop I've been working with, there was only mach-exynos, not mach-exynos4, and definitely not both.

No matter what you name it, you're not going to be able to track mainline with this unless you sacrifice MASSIVE amounts of functionality (such as ditching support for any idle state deeper than WFI), because at least in this particular instance, mach-exynos in the Samsung drop is simply lightyears ahead of mainline.

You're going to have to either forget about bringing in mainline patches that touch mach-exynos for a long time, or accept a major reduction in functionality - no matter how you do it, mach-exynos needs to differ significantly from mainline to be even remotely useful.

This one is, of course, a tough one - Is the different implementation in mainline actually newer or older? Determining new vs. old in Samsung drops can be difficult - it may just be taking forever to mainline the additional stuff in Samsung's driver, just like the features just mainlined in 3.3 have been in Android kernels for well over a year.
[Galaxy S II Original Android Development] XpLoDWilD:
My bad, after checking it must be codeworkx that merged it wrong (he put samsung on top of "stock" 3.0.15 to check the differences), I guess files weren't deleted.

I'm not talking specifically about mach-exynos implementation, but more all the other things that got touched around it.

If copyright header is right, Samsung's one is 2009-2010 whereas 3.3 is from 2011. One example is that the Samsung driver uses mutexes and locks, which are not needed anymore and are not present anymore in mainline. This causes deadlocks everywhere when trying to use them in a "clean" kernel.
[Galaxy S II Original Android Development] sp3dev:
My main concern is that in my 3.3 kernel (the one on gitorious - https://gitorious.org/i9100-proper-linux) suspend is not working, and this is the main thing to fix.

So what I think.

1. porting 3.0 is easier (suspend works, less difference). In 3.3 much stuff like FB has changed. But if we port to 3.3 we'll be able to easily update later

2. A lot of drivers in vanilla/linaro 3.3 are using standard interfaces (v4l2, LED api, sensors API) which differ from samsung's api for drivers. We'll probably have to rewrite the userspace libs a bit if we use more of mainline drivers

3. We need to decide on bcm4330 vs brcm80211 driver. First one is probably more stable and power saving, the latter one is mainline.

4. It may be hard to port sound driver, and ultimately it'd be cool to get rid of SRP (samsung reconfigurable processor) driver and non-standard ALSA controls

Let me know if suspend is working in 3.3. I hope I can help you with this project and also make my non-android kernel more complete, but till next week I'm busy with exams :( but after them I will start my tree at github and send pull requests to you (or vice versa)
[Galaxy S II Original Android Development] bluefa1con:
any progress so far ?
[Galaxy S II Original Android Development] beston94:
I hope for your sake, that you commented on the wrong thread....Otherwise..have you been living under a rock for the past 2 months or so?
[Galaxy S II Original Android Development] bluefa1con:
there is no discussion thread for this kernel

stop being a tard if you cant answer what i asked
[Galaxy S II Original Android Development] beston94:
Which part of "Samsung already released the kernel source code" do you not understand mate? Please specify this so I can get this through your thick skull....

Reading does not hurt..you should try it..
[Galaxy S II Original Android Development] TheSniperFan:
Calm down, there is NO reason to behave like this. He asked because the OP didn't update the thread in a while.

As far as I'm aware, his goal is to create a clean kernel. Something that can be easily updated when the Linux kernel receives an update. Samsung's kernel is "full of dirty hacks" according to xplodwild. This makes updating hard.

I think that I remember codeworkx saying that the kernel needs some months some time ago in the cm9 thread. And that was after Samsung released the sources for sure.
[Galaxy S II Original Android Development] :
Any news on this?
[Galaxy S II Original Android Development] sam razzy:
Read above post :p haha

TapaTalk Gnex Galaxy Sii
[Galaxy S II Original Android Development] :
Ups lol :p

Thanks mate :D
[Galaxy S II Original Android Development] TheSniperFan:
Look what I stumbled across today.

http://xdaforums.com/showpost.php?p=25638203&postcount=16

Sounds good doesn't it?

That means that work has started. (The keyword here is "started") So please be patient, as it'll take its time to finish or even release betas.

I'm sure that updates will be posted here once there are some.
[Galaxy S II Original Android Development] runedrune:
https://github.com/opengalaxy
[Galaxy S II Original Android Development] sam razzy:
Our s2 is added :)

TapaTalk Gnex Galaxy Sii
[Galaxy S II Original Android Development] bluefa1con:
kernel 3.4 is out :D http://kernel.org/
[Galaxy S II Original Android Development] gbohm:
are android and linux kernels allready merged under the linux branch?

sent from another galaxy
[Galaxy S II Original Android Development] bluefa1con:
yeah but xplodwild said specifically that he was waiting for 3.4 release
[Galaxy S II Original Android Development] :
*bump*

Is this dead? :(:(:(
[Galaxy S II Original Android Development] hawkn:
Has the work stopped ?

Moved on to SGS3 or Note?

Was really looking forward to some updates/releases of this kernel....
[Galaxy S II Original Android Development] iamnotkurtcobain:
Wait....

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] gbohm:
after a quick look git not updated for a month soooo make your guess

sent from another galaxy
[Galaxy S II Original Android Development] khawarspirit:
No more development? :( This would have made the CM9 development so much more awesome.
[Galaxy S II Original Android Development] Sourabh007:
Just askin if this port is ever successful :finers crossed:

Will the wakeup lag be vanished :? or it is jus the thing of exonys..can neva be cured:?
[Galaxy S II Original Android Development] TheSniperFan:
Maybe, no, yes.
[Galaxy S II Original Android Development] bluefa1con:
no update on git for months

look like the project is dead :(
[Galaxy S II Original Android Development] MemoryController:
There are newer projects and the 3.4 version looks more promising.

Sent from my GT-I9100 running CM10
[Galaxy S II Original Android Development] bluefa1con:
This thread was supposed to be updated for 3.4 or they moved to another thread?
[Galaxy S II Original Android Development] peterperfect:
Xplodwild has been involved in several other projects including CyanogenMod 10 for a bunch of devices and the whole setlist of TeamBBQ like BBQLog, BBQDroid and Opendesign. That obviously makes other things stop. Thats why this is not being moved. I didn't talked to him about it but AFAIK has no plans to be retaken right now.
[Galaxy S II Original Android Development] mesaj:
But if this kernel isn't developed and it's fairly old, who is archeologist and found it out these days? :P
[Android Q&A, Help & Troubleshooting] allan78:
hi every one

first i would like u 2 know my engilsh is poor ( im sorry )

here is my story. i have sensaion xe europe rooted & s-off but Yesterday i Received an update for ics android 4 sense 3.6 update size about 283 mb so i did download it and then the phone restart but its Freeze in this picture

so i I knew its because the root and s-off so i tried to get my device back to s-on and remove the root. from this thread http://xdaforums.com/showthread.php?t=1192300 but i think i didnt found my device software in filefactory link and also the filefactory link its not usefull its always says (All free download slots on this server are currently in use) check this link http://www.filefactory.com/f/c87a2330449af512/ and here the informaion from my Hboot screen.

Revolutionary

PYRAMID PVT SHIP S-OFF RL

HBOOT-1.17.1111

RADIO-10.14.9035.01_M

eMMC-boot

Jun 2 2011,22:31:39

am in great need of ur help asap please. thank u
[Android Q&A, Help & Troubleshooting] Adiost:
Hey guys.

I just want to know, where can I change key biddings? I mean, just for example, how to swap "home" and "menu" buttons.

Is it somewhere within kernel? Or is it somewhere in /system?

Thanks in advance.
[Galaxy S I9000 Themes and Apps] Jose_Paramore:
I would like to modificate orange parts of the framework of my rom and change orange colour to blue... I'm on eliterom 4r2, how to do this?

Enviado desde mi GT-I9000 usando Tapatalk
[Galaxy S I9000 Themes and Apps] rmean:
i second this :)

SlimICS - Semaphore 0.9.1 - GT-I9000
[Galaxy S I9000 Themes and Apps] s1m4an:
search for apktool, there's lots of threads explaining exactly what you are looking for.
[Galaxy S I9000 Themes and Apps] bhu1:
Most of orange **** is in systemUI. ;)
[Galaxy S I9000 Themes and Apps] dalton8:
I had the same problem, i searched and found this, working on SlimICS.

Apparently it works on all 4.0.3 ics (phone must be HDPI), however, as always, do a backup first.

It got rid of every bit of orange/yellow except the loading bars in some apps. I can live with that though, everything else looks nice. http://xdaforums.com/showthread.php?t=1517501
[Galaxy S I9000 Themes and Apps] Jose_Paramore:
Mmm... for me is in framework-res

Enviado desde mi GT-I9000 usando Tapatalk
[Galaxy S I9000 Themes and Apps] Jose_Paramore:
The problem is that I use 4.0.4 :/

Enviado desde mi GT-I9000 usando Tapatalk
[Defy Q&A, Help & Troubleshooting] polojpg:
Hello, could you help me please.

I have a defy regular with green lens and i have flash with defyplus u3_4.5.1-134

I can't donwgrade it with other sbf, always red M and reboot or black screen.

With this sbf i don't have speaker and can't download to the market.

What should i do ?

Thank's a lot for your reply.

mb526

version 2.3.5

v sys 45.0.1250.mb526retail.en.gb

epu93.u.00.60.00

v noyau 2.6.32.9

n build :4.5.1-134 dfp125
[Defy Q&A, Help & Troubleshooting] CodeRedXM:
I believe you got yourself in trouble here. You flashed a Defy + Rom on the Original Defy? Well now you can't downgrade. But dont worry because the official Gingerbread works fine but I can't be too sure about the camera..

If you want the link to the official Motorola 2.3.4 SBF just let me know
[Defy Q&A, Help & Troubleshooting] MainCourse:
Flash another sbf - the one that's meant for yours!

Check this thread:

http://xdaforums.com/showthread.php?t=966537

enjoy!

:)
[Defy Q&A, Help & Troubleshooting] polojpg:
Yes i did it !!! The problem is my speaker doesn't work.

Could you please give me the link for official sbf. Thanks.
[Defy Q&A, Help & Troubleshooting] polojpg:
I have tried a lot of these sbf but there's only the defyplus u3_4.5.1-134 whose boot my defy.

For all other sbf = black screen.

Sorry for translation...
[Defy Q&A, Help & Troubleshooting] bladerara1:
The one that worked for me is 3.4.2-107 TMobile US Blur. No problems what so ever. Hope it hepls.
[Defy Q&A, Help & Troubleshooting] droid_<3er:
That's a 2.2.1 sbf. He is on 2.3 full sbf with no downgrade so he can't use

that.
[Defy Q&A, Help & Troubleshooting] polojpg:
ok , i don't know why but most of function are ok.

Just the camera doesn't work : black screen.

Is there a issue for green lens for u3.4.5.1-134 ?

Thanks.
[Defy Q&A, Help & Troubleshooting] droid_<3er:
Arrrggggggghhhhh

With green lens defy you are not supposed to flash defy+ Roms and kernels. Because the green lens camera is not compatible with any Motorola gingerbread Rom.

You can use greenbread mod I think. Search greenbread mod by walter79 on xda. Fingers crossed.
[Asus  Eee Pad Transformer Prime] Atlas7:
I am not responsible for any damage and you are doing this at your own risk!

I found on youtube a very interesting video on youtube how to improve performance WIFI and GPS! My Prime is on warranty so i cant to try it and get the results!

VIDEO: http://www.youtube.com/watch?v=fsRqjG8i3Vw
[Asus  Eee Pad Transformer Prime] Erusman:
Good Job. Let us all know the results you get with this copper tape. You can see the thread in my sig as well. Alot of us have tried various methods. I have a feeling you aren't going to improve the signal that much. If at all. That aluminum backplate is a major signal killer.
[Asus  Eee Pad Transformer Prime] monkey10120:
def want to see your results. It looks good.
[Asus  Eee Pad Transformer Prime] palswim:
I tried to post this in the viperMOD Prime Tool thread itself, but I guess I don't have sufficient privileges to post there yet.

But, I want to mention that running a virus scan (ClamWin) on the tool shows a match for the "Trojan.Banker-981" virus in the tool.

Now, I know that code for rooting involves virus-like insertion or exploits, but I saw no mention or acknowledgement of this particular issue anywhere related to the viperMOD tool.

I post this for two reasons:

Obtain confirmation that the code's operation intends to use this specific exploit

Provide a reference for anyone else who may encounter this match in their Anti-Virus software and search for information about it
[Asus  Eee Pad Transformer Prime] Atlas7:
It is false positive. When you going to root your prime you must disable your antivirus program!
[Asus  Eee Pad Transformer Prime] palswim:
I can still run the root tool. The AV just told me it contained a virus.

And, you can't seriously tell someone to trust every file that purports to act as a rooting tool.

I would at least like an acknowledgement that a certain tool will cause a match for Virus-XXX before I simply discard the output of my virus scanner.
[Asus  Eee Pad Transformer Prime] aznmode:
Ive seen some kitchen tools do that too. But I trust Vipers work and have used some of his other rom. As far as his utility, I don't get any virus notice when I run his program at home even at my work computer which uses Norton Enterprise Antivirus edition.
[Asus  Eee Pad Transformer Prime] Atlas7:
I have Kaspersky and get alert, But i pm viperboy and he say to me it is false positive and he is really good developer!
[Asus  Eee Pad Transformer Prime] palswim:
Yeah, I don't believe he has put anything malicious in his code. I've actually run it (in a non-administrative shell) and rooted/unrooted my device.

But, I know that it would have given me some assurance if I had seen a post or something about a virus someone found, or even a list of virus matches to expect for the file(s) in the OP.
[Asus  Eee Pad Transformer Prime] lil-devil:
typically threads in the android development thread, if there are actual virus chances are that post would of been taken down within 24hours as people will be spamming the report button

so if it has like 20+ page chances are its good! :D
[Asus  Eee Pad Transformer Prime] youngnex:
i agree 100%.

Your point is valid. However, its been months that it was released. I would assume by now someone would of noticed and said something.

Thanks for letting the scene know, but i think as this point, it is safe. As no one has anything to say about malicous code or that app doing anything to them. I ran it myself and had no problem.
[Asus  Eee Pad Transformer Prime] scrufy:
I think you will find it reports positive because like op said, it modifies the boot sector. Which is a typical virus like activity.
[Acer Iconia Tab A100] SmokeyDP:
Is anyone else running Chrome Beta? For some reason when I go to settings the app crashes.
[Acer Iconia Tab A100] jeromel:
Yeah, that was happening to me too. Clear the Data from Settings->App-Google Chrome Beta

On your PC go to your Google Dashboard and

In the Chrome Sync section, Stop Sync and Delete Data from Google

Following the instructions at

http://support.google.com/chrome/bin/answer.py?hl=en&answer=1181035&topic=1693469&ctx=topic

to disable encryption and then re-enable encryption using either your Google password or a new paraphrase.

I'm pretty sure that those were the steps I took to get rid of the FC but I can't remember totally as I was really sleepy. Either way, I'm not getting that issue any more.
[Acer Iconia Tab A100] danifunker:
I tried this a few times without success. I was able to access settings immediately after signing in with the link at the bottom of the screen, but couldn't get to the settings through the menu
[Acer Iconia Tab A100] cheeb:
Same here...I just use either Maxthon Browser or Dolphin HD browser....they are both good...hopefully the Chrome will be ready soon.
[Acer Iconia Tab A100] SmokeyDP:
I never got it to work. I even tried deleting my app data and going to settings without logging in and it locks up.