yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] SirGatez:
Kernel hacking is very similar to any other reverse engineering effort, an under standing of asm is needed, as well as the file layout of thr target binaries.

Although technically reverse engineering by way of of binary decompilation is copyright infringement and a breach of most software usage licenses, but so is sharing binaries from one platform to another dispite the purpose.

Either way that isn't something I will be working on just yet unless an opensource driver for this surfaces we will use sammies for now and concentrate on making what we have stable. Fixing the radio and testing the other hardware are priority since the current binary froyo graphics driver does work atm. We will get an opensource version working later, if not then we worry about the the black box problem.
[Fascinate Android Development] SirGatez:
About 2 hours more research later I learned that a portion but not all of the PowerVR SGX/MDX drivers are open source, they are released like binary blobs with the open sourced portion of the driver enclosing the closed sourced blobs to function (much like how NVidia and ATI began their Linux Driver crusade), I will attempt to contact TI / Imagination for the open source portion of the drivers, they do not have them posted for public consumption but should have no problem providing access under the OSS/GPL. If anyone has these already they can send me a PM and it will save some time, likely the closest port that should work will likely be TI's OMAP34xx PowerVR SGX with modifications as it is already Linux compatible. There are about 3-4 versions of the driver, the external installer version does not match the internal library versions, v1/v2 is Pre-Samsung-Eclair/Samsung-Eclair, and I have downloaded v3 and attempting to get it to work with Froyo, I am not sure what version Froyo uses, v4 is avail for OMAP3xxx developers from TI linked to a development board that they sell. Not sure what version is available by request. I downloaded v3 but the problem I'm having with v3 is compiling has a data type conflict that I am attempting to resolve between the portions I pulled from v2 for Samsung compatibility.
[Fascinate Android Development] saps:
Go SirGatez go
[Fascinate Android Development] Terror_1:
Good go, appreciate the effort for the greater good.
[Fascinate Android Development] StDevious:
is there like a link to guide or a book to learn ?
[Fascinate Android Development] GizmoDroid:
I know it's too early for feature requests... so I'm just going to leave this here... you know, for fun.

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

No pressure. :cool:

Nearly all of the innovators that make beautiful things happen with technology are in violation (or at least a gray area) of the law. It really is a shame.

I wonder how much bribe money it took to get the DMCA passed? I'm sorry, I meant "political funding".
[Fascinate Android Development] SirGatez:
Source is online now! Sorry for the delays, Enjoy!

http://www.github.com/sirgatez

I'm working on porting some features from Blazed into Froyo now, git will be updated once I verify everything works. To compile Froyo use the Fascinate_Blazed_defconfig. You will need need to use the stock modules pvrsrvkm.ko, s3c_lcd.ko, s3c_bc.ko for graphics to work. Use of hotspot_event_monitoring.ko, dhd.ko, dpram.ko, dpram_recovery.ko may also allow for operation radio and wifi although I have not tested this, so consider radio operations to still be broken, I am working on the issue.

I did manage to compile versions 2 (From Eclair, did not try Eclairs older EGL libraries with Froyo), 3 (Had android EGL libraries 1 subversion lower than stock Froyo) and 4 (no android egl libraries were included) of the PowerVR drivers and something is amiss and still results in a boot loop, something doesn't seem to be compatible, seems like I get missing library defines no matter how I try.

If someone has intimate knowledge about the PowerVR 3D and EGL on android and could PM me I would like to get some help on getting a fully working compile from source of the drivers that works. Any TI/OMAP3 experience with this driver should be applicable to this situation. I have not posted these drivers on git because there is a clickwrap license on the, you can get them from TI's website, some of them require a login to download, some of them are instant with no login.

I expect full source working drivers for all other devices except graphics within 7 to 14 days once the bugs and incompatible code is resolved, again the dhd wifi drivers are NOT compiling to the same size as the one provided by Samsung, so something seems fishy. If anyone from the internal Samsung Froyo dev team would like to help shed some light on why dhd.ko, pvrsrvkm.ko, s3c_lcd.ko, s3c_bc.ko all compile from the posted source to files 3-8 times the size of those included in Samsung's stock roms it would help progress greatly. Oh yes and I will not reveal any identifying information in exchange for your help unless you request it :-)
[Fascinate Android Development] SirGatez:
Making progress with dpram/gpio control lines. Once I get this right the radio will be working like a charm. Dpram also controls operation of other major hardware such as camera, bluetooth, wifi, in addition to cellular. These devices all work independantly of each other but the dpram module handles the traffic and control i/o.

The galaxy phones while all sporting similar hardware have slightly different ways of controlling them.
[Fascinate Android Development] prometheus1010:
Samsung released the source for froyo for the epic today.

http://www.androidcentral.com/samsung-releases-source-epic-4g-eb13-froyo-update

This is most likely of limited usefulness but hopefully a sign we wont have to wait long for the fascinate source.
[Fascinate Android Development] SirGatez:
3G data is now working but voice/media is on the fritz... Still working on it will try to post new alpha today with and without voodoo.
[Fascinate Android Development] tapout27:
awesome news SirGatez....
[Fascinate Android Development] akaine2001:
gj man

i smell the 1st custom kernel on the horizon:cool:
[Fascinate Android Development] SirGatez:
My goal was a working Froyo with source before Samsung. I might still make it 8-)
[Fascinate Android Development] tapout27:
yea man i think you can...
[Fascinate Android Development] s44:
Did you sort out the video driver issue?
[Fascinate Android Development] NOsquid:
Definitely don't give up, I keep hearing about new leaks so I think Verizon will be a while...
[Fascinate Android Development] skynet11:
A "working" Froyo? VZW/Samsung will be several months yet... you got nothing to worry about ;-)

Another Fascinating post by my XDA app...
[Fascinate Android Development] SirGatez:
Trying to write a replacement for param.ko, we are going to need to drop Samsung modules and have an opensource replacements, these will eventually be needed by GB or any other fully aosp rom/kernel.

This module is responsible for reading and writing 7 varibles that need storage between boots incuding if the phone needs to boot default kernel or recovery kernel on next boot.
[Fascinate Android Development] SirGatez:
Just letting everyone know I am not dead, still working on resolving the voice issues, it never attempts to place the call but its pulling garbage from somewhere possible a wrong gpio setting..
[Fascinate Android Development] rmtobler:
rooting for ya SirGatez!
[Fascinate Android Development] Thrillhouse847:
Show that code who's boss, dawg!
[Fascinate Android Development] SirGatez:
I rendered my source unbootable the other day. Always remember when testing new options try a few at a time.. Not 30 at a time :-P It only complicates debugging...i'm still having flashbacks...arggg

Data on boot is getting more reliable but it more often reports as 1x when in fact it is operating as 3g, going to attempt to debug eclairs stock ril command set and froyos for comparison, I has a feeling more strange things maybe found..
[Fascinate Android Development] tjthebest:
Thanks for the update!
[Fascinate Android Development] GizmoDroid:
Lot's of bugginess to be found in that data connection. From what I see around the net, it's a pretty widespread issue.

But really, with coders like these, it's no surprise:

/system/etc/init.gprs-pppd

#!/system/bin/sh
# An [B]unforunate [/B]wrapper script
# so that the exit code of pppd may be retrieved

# this is a workaround for issue #651747
#trap "/system/bin/sleep 1;exit 0" TERM

That's rather "unforunate" spelling there, sir....

Or my favorite from the Samsung Moment source:

#ifdef __KILL_PPPD_ON_MOD_RESET static int check_pppd(void)
{
unsigned long flags;
// FIXME
// Temp code for instinctq bug in data reconnection after modem is reset
// When the modem is reset, pppd doesn't close ttyCDMA nor does it clear
// the exclusive flag. When this happens other apps can't reopen ttyCDMA
// device. And if even if it did, data connection can't be re-established..
// So for now, let's just kill pppd here for an easy fix...
local_irq_save(flags);
if(strcmp(current->comm, "pppd")==0) {
pppd_pid = get_pid(task_pid(current));
printk(__C "pppd pid=%d" C__, pid_vnr(task_pid(current))); //
} else {
if(pppd_pid && pppd_reset_needed) {
int err;
struct pid *p_pid = pppd_pid;
pppd_pid = NULL;
pppd_reset_needed = 0;
err = kill_pid(p_pid, SIGTERM, 1);
printk(__C "Killing PPPD(%d) err=%d" C__, pid_vnr(p_pid), err);
} }
local_irq_restore(flags);
} #endif

Heck, if I was going to be lazy at my job, I don't think I'd actually write it in plain English in the source comments. I guess they forgot to go back and write a proper fix before shipping? So much for it being "Temp code"...

On top of coding issues, we've got a ton of noisy devices crammed onto a tiny board, that is being mass manufactured with as cheap of materials as possible. It's no wonder that there are so many reports of spotty GPS/data/bluetooth, with all that interference.

I'm not saying only Fascinate, or even only Samsung. I'm just saying that this is the current mentality. Cellphones are essentially supposed to be a disposable device, every 1-2 years. Why try to make them excellent when you can make them "good enough"?
[Fascinate Android Development] onionz:
Will this source code allow voodoo sound and video to be compiled once its complete?
[Fascinate Android Development] GizmoDroid:
Anything that SirGatez wants to add to the kernel not only can but will be added, 'cuz he is a beast.
[Fascinate Android Development] ace518:
I don't even have a fascinate, but think this is awesome.. Good luck on this. Seems like you are making some great progress.
[Fascinate Android Development] navenedrob:
It pains me that you have to work through such garbage. I'm glad that you have the willpower necessary to fix the code! It looks like you are trucking right along with progress here. You'd know better than me, but from the way it sounds we might have a kernel to test once data and voice issues get worked out. Very exciting :eek:
[Fascinate Android Development] bwheelies:
SirGatez, how is the project going?
[Fascinate Android Development] SirGatez:
As of this morning I have a working back key but also a broken home key :-) hopefully i'll figure it out tonight and get this thing updated.
[Fascinate Android Development] SirGatez:
This is almost like a complicated game of whack-a-mole. Missed my release because of complications in the compile, going to do some more testing and experiment with some previously untested code...hoping for the best.
[Fascinate Android Development] GizmoDroid:
I just read the edit in the OP from 3/10... and now I'm drooling.

Where do I send the bill for a new keyboard?
[Fascinate Android Development] iofthestorm:
Wow yeah that sounds awesome. SirGatez ftw. Unfortunately I never tried your Eclair kernels because by the time they came out I got bored of flashing a new kernel every day and then Froyo leaked out. I wish I could hack on kernels, but the time investment necessary and being in college prevents me from seriously reading up on this stuff. But I still enjoy reading all the technical posts from SirGatez and GizmoDroid! If we can become fully independent of Samsung with AOSP OS and kernels based on i9000 source, it will be glorious.
[Fascinate Android Development] nemesis2all:
I'm still looking forward to what you come up with. Keep up the great work!!!
[Fascinate Android Development] GoogleAndroid:
Wow, same here. If you can get this working, that would be awesome. Maybe there's still some hope for this phone.
[Fascinate Android Development] onemotodroid:
Outstanding work!!

As a dev please keep the can-do sprit - this is what the fascinate badly needs
[Fascinate Android Development] GizmoDroid:
I hope this latest release of source code from sammy is enough to knock this kernel into beta status without having to wait for verizon to get their act together.
[Fascinate Android Development] SirGatez:
It is, both used identical kernel in Eclair :-)
[Fascinate Android Development] GizmoDroid:
Anyone else excited? I'm excited.

Wish I could get involved... but senior year crunch is squishing my phone hackin' time down to nearly nothing.
[Fascinate Android Development] SirGatez:
Haha I never had any phone hacking time...just been scrapping up time when I find it to afford minutes for my habbit lol :-) Spare some minutes for an addict down on his time? LOL
[Fascinate Android Development] GizmoDroid:
I know this is way too forward thinking given that a stable froyo custom kernel isn't even out, but the jump from froyo beta to cm7 compatible beta is a large jump? Or something that you will be working on in parallel, making it an easy jump? Or is cm7 not a goal?

I think you discussed your roadmap before, but my memory is bad, and I know how roadmaps have a way of changing over time.

This is how I feel, except I'mma need a lot of learnin' to even get into kernel stuff. I've always been a chicken and stuck in windoze land, so I don't even have most of the rudimentary knowledge of how *nix/android handles most things. That and my programming skills are poor. No one should expect to see GizmoDroid kernels for at least a year (or more likely, never. Or if so, on a different platform). :rolleyes:

I'll be the guy going "Hey, I have this idea, can we do this?" and all the real devs will be going "What do you mean 'we'? You got a mouse in yo' pocket?" And then I'll write it in my braindump thread just to feel like I accomplished something :p

Man... I just have too many interests and hobbies to be good at any single one of them and still actually have time for friends and family.
[Fascinate Android Development] SirGatez:
CM7 is alongside our Froyo work, the good part is most of the CM stuff for other Galaxy phones is drag and drop with fascinate code. Ginger after but someone is going to working on it while we get Froyo stable and Feature packed :-)
[Fascinate Android Development] s44:
Just occurred to me to wonder -- have you been testing with i9000 Froyo ROMs or our own?
[Fascinate Android Development] SirGatez:
The leaked stock, EB01.
[Fascinate Android Development] s44:
Wouldn't it make more sense to see if we can get their JS8 running? The i9000 has a *lot* of ROM devs and multiple official updates every month.
[Fascinate Android Development] DiGi91:
Damn if we got i9000 roms running!! *OMFG* :D

./me whispers darky.. ;]
[Fascinate Android Development] Huntredgo:
*Bump

How's the project coming?

I'm sure I'm not the only one supervision excited for a sirgatez froyo kernel :).

No rush, of course :)
[Fascinate Android Development] SirGatez:
Still trying to merge the apparent spaghetti string codes together from the EC 10 changes in to what I'm working on, I have the code base merged but for some reason it was decided for this release unlike all prior galaxy s phones except the epic that platform specific code in the files should be externalized....why this one and the epic...I do not know, but progress is good. I am finding it hard to dedicate alot of time to it so that is hindering my speed some. I also picked up a Thunderbolt for my daily use which may help speed up Fascinate tests because I will not be tying up my primary phone when testing. Later I do plan to do some Thunderbolt work and already it looks alot friendlier than what Samsung left us to deal with.
[Fascinate Android Development] s44:
NOOOOOOOOOOO!!!!!!1!!

Um, keep up the good work. ;)
[Fascinate Android Development] TheHobbyist:
I'm beginning to think that the thunderbolt was far worse for the fascinate dev scene than anything samsung or Verizon did lol!

SirGatez you're my hero, please don't leave us for the tbolt!

Thanks again for all of your hard work! It's fascinating!
[Fascinate Android Development] GoogleAndroid:
:( Just don't quit your Fascinate work. There's a lot of us stuck on a contract. I wish I could get a TBolt, but I can't. I think, quite literally, every dev we have has gotten a TBolt.
[Fascinate Android Development] StDevious:
I think so too.

I think so beacause of the ease to work on HTC devices i think. But I think with his attention divided, fascinate is bound to suffer.
[Fascinate Android Development] rmtobler:
Yup I've pretty much lost all hope for any significant progress to be made for the Fascinate. The experience since purchasing the phone in October has been pretty sub par on the development side as a whole. Watching others get new goodies and being patient has come and gone and despair and resignation has set in. Oh well... overall I am still content with the phone and whatever the devs have cooked up so far. When I purchased the phone the only thing I really wanted was froyo and we have that.
[Fascinate Android Development] GizmoDroid:
Sometimes I feel like people don't realize that in the open source world, the "devs" are everyone who own the phone. There's no "team". It's just people like you and me that volunteer to spend their time working on the phone. The Samsung "dev team" are the one's getting paid (and dropping the ball).

It's similar to going to a car forum and being let down by the lack of free mechanic repair.

I've always been confused by where someone would get any other idea.

EDIT: This is not a flame, and it's not directed at anyone in particular.
[Fascinate Android Development] ajd88:
Lol that was a satisfactory response. Thank you kind sir. Looking forward to the future.

Sent from Fascinate SuperClean 2.9.2 Voodoo Using Xda Premium App
[Fascinate Android Development] kidserious:
Sir Gatez you are a class act sir. Thank you for the reaffirming and inspiring words. They have given me somewhat of a renewed hope for the fascinate (not that I lost it but it was looking kind of dim with all that is going on). Thank you for staying with us. You and kaos and others of course are keeping us alive.
[Fascinate Android Development] rmtobler:
Great post SirGatez!

Gizmodroid and SirGatez have been two of the better posters in the development section. Glad they are still around and making the phone even better Looking forward to the continued work and information.

Oh and I haven't heard much from navenedrob until the new rom, but add him to the list too.
[Fascinate Android Development] xjestersdeadx:
VERY much appreciate the long post. You took the fears of many who were thinking that the Fascinate lost another volunteer Dev to the Thunderbolt, and explained a lot more than was required or asked for. Thanks for your hard work!!:D
[Fascinate Android Development] kennydied23:
Thought I should mention that VZW froyo source has dropped.
[Fascinate Android Development] SirGatez:
Appreciated :-)
[Fascinate Android Development] hoppermi:
Because you probably need more on your plate:

i9000 GB source released

http://opensource.samsung.com/
[Fascinate Android Development] s44:
Actually, given that we have multiple i500 Froyo kernel source drops now, I wonder if it isn't time to move to maybe backporting this to the Fascinate...

Not sure how much relatively harder that would be, though.
[Fascinate Android Development] imnuts:
It may help someone get the .35 kernel working for us, but not without some work. I downloaded the source to look at it quick, and there isn't any atlas/victory junk in it, but it also doesn't contain any config file for the Fascinate. It may be able to be made to work, but it could take some time.
[Fascinate Android Development] s44:
Well, remember that this thread is about SirGatez backporting a i9000 .32 kernel (from before there was CDMA source). So, sunk costs aside, I'm not sure trying for Ginger instead of Froyo would be necessarily harder.
[Fascinate Android Development] imnuts:
Yeah, it will definitely be much easier with official .35 source to work from as far as getting GB working.
[Fascinate Android Development] boostedjti:
Doesn't pk use the .35 kernel for cm7? Regardless, birdman had .35 booting
[Fascinate Android Development] chopper the dog:
Are you basing that off of a 3am tweet or is there a thread that I missed? :p

good day.
[Fascinate Android Development] OldManJames:
I think he is talking about back in like december when bird had .35 booting. Nothing worked but it booted
[Fascinate Android Development] 8855944:
good work
[Fascinate Android Development] boostedjti:
This.

But I haven't heard much since
[Fascinate Android Development] OldManJames:
That's cause he gave up on it
[Nook Color Themes and Apps] Clienterror:
Hey all, just got a nook color and got it rooted (Love it). I have titanium backup and quite a few apps on my SGS phone and was looking to love over my backup folder and License file to my nook to install a few of them. When I put the folder and license in my internal memory (5 gigs) it doesn't see the folder or my license file, I've also tried putting it on my external SD. Where should I put this folder/license file so it will be seen by my nook/Titanium? Also when I start Titanium backup it only shows my internal app memory space (750-800megs) and my external (8 gigs), where the heck is my internal 5gig storage at?

Thanks a ton, as it seems the nook is set up a little different than my SGS phone and any help is appreciated!
[Nook Color Themes and Apps] Clienterror:
99 views and no one knows where to put the titanium license file?

Sent from my Nook Color.
[Nook Color Themes and Apps] philburkhardt:
If you have market access, just move the Titanium backup folder to the nook and redownload titanium and the license key from the market. That's how I did it.

EDIT: If you don't have market access, use root explorer to pull the apks from your phone. There is an apk for titanium, and another one for the pro key in data/app.
[EVO 4G Q&A, Help & Troubleshooting] kidram:
OK so like topic said Wich one do ya like better myn or mikfroyo rom?
[EVO 4G Q&A, Help & Troubleshooting] jacoballen22:
I like myn's, BUT I am currently having a problem flashing the radios for it. Worked on clockwork but not amon.
[EVO 4G Q&A, Help & Troubleshooting] Danthony428:
i've never used myns rom, but i know that mikfroyo is pretty bad ass, i used it for quite some time before switching to Kings UltraFroyo Unleashed, and then ultimately learned how to make my own roms for personal use, now i can use what i like from everybody's roms if i want to, If you have trouble sticking with one rom because of the features, i suggest you try this, but never publish it as your own work, because it most certainly is not.
[P3400 General] BOOTMGR:
today i tried my own cooked ROM to flash from my kingston 4GB SD card.After 10 minutes i got message SD Update Failed! now my GENE is bricked:mad:.

My real problem is that my camera key isn't working hence it is not possible to go to bootloader.And also it is impossible to repair it.I have many experience flash ROMs but this time i need your help urgently.Please notify me if you have any other method to go to bootloader.I had put wince.nls in my ROM.

Thanks in advance

This forum is my last hope:confused:
[P3400 General] isDQ:
can't go to bootloader?

what a tragedy!