yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] mkasick:
Correct. Most of the time the ifdefs are config options that differ between a stock kernel and the source release. That's responsible for a lot of it here. I didn't time previously to narrow down the config differences and attempt to get a kernel as close to the EG30 config as possible, although I'm trying that now.

The dpram.c example above falls into this category.
[Samsung Epic 4G Touch] mkasick:
OK, I went through and fixed up the E4GT kernel config to compile a kernel as close to EG30 as I could get.

Attached is a patch with the changes to the E4GT defconfig to get an "as close as possible" compile, and also attached is a source-built kernel with the EG30 initramfs and that patch applied. Since it's intended to be "as close as possible" to stock, this kernel isn't rooted. Mind you, I don't have an E4GT so this is untested.

If there's a brave soul out there, feel free to flash this and report if (i) it works, and (ii) behaviorally it's noticeably any different from stock.

As for my earlier claims, I'm not sure what's up with the Westbridge driver, it may yet be modified, but the modification is subtle. However the "tty driver == NULL!" bit in dpram.c went away. It's not #ifdef'd, but perhaps one of the debug options I disabled allowed that code to be optimized away, or something. I'm not sure.

Anyways, with these kernel config changes in place, I can't confidently say that the open source release isn't EG30 anymore. Granted, what they released definitely doesn't include the same kernel config as EG30. And the changes to the config made in the source release (performance events, profiling support, tracepoints, debugging for preemption, mutexes, spinlocks, etc.) touches enough of core kernel behavior that, I suppose they could exacerbate some of the problems we see (e.g., LoS).

Mirror links:

EG30 fix_defconfig patch: fix_defconfig.diff

Source-compiled, EG30 kernel: kernel-opensource-1.tar.md5

Edit: Moved attached files to development thread.
[Samsung Epic 4G Touch] sfhub:
Sometimes you won't see the ifdef directly in the code. It'll be a pre-processor macro defined somewhere else. In general, many "asserts" are written this way so when you change the config to release from debug, the asserts disappear.
[Samsung Epic 4G Touch] mkasick:
The line in question is dpram.c:2907. The LOGE macro should be unaffected by the defconfig changes, but even if it is, there's other LOGE statements that were consistent in EG30 and previous source builds.

I suppose it could've been a strings foul-up.
[Samsung Epic 4G Touch] sfhub:
If the cause of LoS ends up being due to a race condition, then just changing debug printfs (let alone preemption, mutexes, and spinlocks) can cause the timing to be more or less favorable for the condition to hit.
[Nexus S Q&A, Help & Troubleshooting] mielke12:
hi everyone i heve a question about my nexus s gt-i9023 rom

is there a program out to reflash your nexus to stock rom like the one for the htc wildfire:

thanks for responding :)
[Nexus S Q&A, Help & Troubleshooting] frutelaken:
Sure, it's called ClockWorkMod Recovery.

Download a copy of one of the stock ROMs (http://xdaforums.com/showthread.php?t=1063664) and flash it through Clockworkmod.

We don't need no fancy applications!

Greetz
[Nexus S Q&A, Help & Troubleshooting] Rem3Dy:
Clearly you didn't take the time to think out your response. If he is not unlocked then your method wont work.

There are 3 common ways. First is flashing the partitions via fastboot. Second would be using the ODIN software. Third would be what was mentioned above. Unlock your bootloader and install a custom recovery such as twrp or clockworkmod. From this recovery you can flash any rom you choose whether its stock or custom.

Good luck.
[Nexus S Q&A, Help & Troubleshooting] ghost010:
is your nexus rooted,yes or no?

cuz your saying RE flash.

if so.

instal clockworkmod and download a rom.

if not.

than you got to unlock it. or ADB push the stock rom.

and ODIN is a last resort.

i my self do not recomand odin with the nexus s models(well not the 3G versions[i920/i923])
[Nexus S Q&A, Help & Troubleshooting] frutelaken:
Since he is talking about flashing ROMs, I figured it was safe to assume that he has an unlocked bootloader. But you're right of course in saying that he needs to be unlocked in order to use CWM.

Then again, I would never suggest to have him 'flash his partitions' through fastboot since he's asking for a GUI solution.

And I don't see or read anyone use ODIN on the Nexus S. I know it's developed with the Galaxy S in mind and I can't say how compatible it is for our phones. If it is- then ODIN would be the easiest solution.

My reponse might have been brief and cut to the chase, but it's the safest, most documented and in my opinion best way to flash a ROM for our devices.

Greetz
[Nexus S Q&A, Help & Troubleshooting] Rem3Dy:
I listed fastboot because most people coming from other devices wouldn't be familiar with it as on most phones it is locked down. Yes Odin does in fact work with the Nexus S, but I only recommend it as a last resort not a go to option.
[Nexus S Q&A, Help & Troubleshooting] are-red:
Why don't u use nexus s one click root? It also can unroot and restore device to 2.3.4
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] aryehzev:
How do i install a UOT Kitchen zip on my rooted archos 32 with sde and the bubu boot menu?

thanks,

aryeh.
[XPERIA X10 Q&A, Help & Troubleshooting] dadsnobest:
I turned my phone on and had no service, it had been working fine on WB's

V 4.0 GB, stock kernel.

My questions are:

1: Has my X10 somehow lost some files needed for network communication? And if so, what files are they, and how can I replace them?

2: Does anyone know how to check to see if the radio is operable, or not.

My notifacation bar shows an X over grey bars. I have downloaded settings for APN via wifi.

I have downgraded to 2.1 and back to 4.0 and to 6.0, no change. Also flashed kernel again.

I keep thinking it's a software issue, the phone has always worked flawlessly and it's never been dropped, wet, or mistreated in any way.

Everthing else works fine.

I could use some help

Thanks
[XPERIA X10 Q&A, Help & Troubleshooting] acerulz:
did u check whether the baseband is ryt ??
[XPERIA X10 Q&A, Help & Troubleshooting] dadsnobest:
Yes... 2.1.71

Thanks
[G Tablet Themes and Apps] narddawg314:
ok, so I pulled the launcher.apk and decompiled with an apkmanager4.9 then I replaced the existing wallpapers with new ones keeping the same names, dimensions, and file types as the original. I recompiled and all that..then I loaded the apk back onto the tab, ran the apk..but it won't install. It starts, runs, completes, but then says "not installed".

Would that be because:

A) I'm trying to install while running ADW?

B) The apk is signed incorrectly?
[Nook Color Q&A, Help & Troubleshooting] atulb:
Hello i m following the instructions here http://xdaforums.com/showthread.php?t=1275859 but on step 12 i get an error sdcard/prep-dualboot. I appreciate the help.
[General Questions and Answers] Dr.Kapotas:
Hi! I have an Ideos X5 and I tried to install extended settings and icon switcher using clockwork recovery mod then when i tried to reboot stucked on the IDEOS icon i dont know what to do...PLEASE HELPPP!!!!

P.S. I have used wipe data/factory reset and still does nothing

Problem solved :)
[Android Q&A, Help & Troubleshooting] jgweiss:
Are there message boards where I can find developers for hire? If you are interested read on:

I have a great idea for a mobile app, and am looking for a developer to join the venture. If you are interested please email me at jgwapps@gmail.com; this is a serious 'out of a garage' project, but I think that with the right help, it has the chance to be something special.

You will need to sign a non-disclosure agreement. I am looking for people with time to work towards this goal; I am an unemployed college graduate looking to start a business, and i'm very committed to making this happen.

Thanks everybody
[Fascinate Android Development] Enyo.:
This is the ICS SDK port for the fascinate.
​

This is a work in progress and is not finished yet.​

Whats working-

Touchscreen (Problem, Have to use 2 fingers, will be fixed)

Multi-touch

Audio

Network (Some Problems)

Bluetooth (Some Problems)

Whats not working-

3G Audio

Download Link will be posted later today.​
[Fascinate Android Development] Zacisblack:
That's a decent list of working functions. Thanks for giving this a go =P.
[Fascinate Android Development] jvincent08:
Are phone functions working? Calling, SMS, etc. And why is audio listed under working and nonworking?
[Fascinate Android Development] shobon:
Thank you Enyo! I'll give this a shot once 3G gets working :D
[Fascinate Android Development] bigwilly90210:
*excited* sweet. I just have to beat my wife to ICS since she's getting the Nexus Prime. Ha. Thanks enyo, i'd love to give this a shot. Wtf does "3g audio" mean???
[Fascinate Android Development] Enyo.:
Streaming doesn't work. I Should edit that.
[Fascinate Android Development] daskydivr:
whoa!

man i was just talking to a friend about getting ice cream sandwich on Fascinate, do you think samsung will port it?
[Fascinate Android Development] Enyo.:
Not likely. Hopefully. But The galaxy s ii will get ICS Though.
[Fascinate Android Development] Dj-Dubster_TN:
Holy **** I'm ready :D
[Fascinate Android Development] Dj-Dubster_TN:
Is this mtd?
[Fascinate Android Development] droidstyle:
yep sure is
[Fascinate Android Development] Tkun:
Very cool! I think I'll try it out when you post the link. :D

Btw, I thought this was more than just an SDK port, can I get some clarification about whether it is or not?
[Fascinate Android Development] zantopad:
Thanks for the port enyo. I will try it as soon as the link is posted!
[Fascinate Android Development] tripacer99:
Guess it's nandroid time, gonna test this out asap.
[Fascinate Android Development] Zacisblack:
How about reading the title of the thread and the first sentence of the OP? It's not even possible to have anything more than an SDK port right now since we don't have source.
[Fascinate Android Development] sarkozy:
Which also means this is functionally non-functional. If you've seen the nexus s ports, it's a waste of time until source is released.
[Fascinate Android Development] Tkun:
I'm more than aware of what it says in the OP, I have eyes. I asked the question because the Ice Cream Sandwich thread on the General board just made it seem like it was more than just an SDK port. It's still definitely an exciting development, no doubt.
[Fascinate Android Development] bigwilly90210:
Come on man! Just release it! Idc how much actually works I just wanna brag that i already have ICS! Lol. Thanks man, super stoked.
[Fascinate Android Development] Dj-Dubster_TN:
I feel ya but at the same time I don't wanna brag about my broke ass piece of **** with a cool is that doesn't work lol
[Fascinate Android Development] boldfilter:
Thanks alot, this would be great on the fascinate!
[Fascinate Android Development] shilohdrummer:
yay, I hope it's not too long when we'll have a stable ICS.... unlike GB.

and if it makes us fassy users happier, the nexus s users don't have ANYTHING working. GO FASCINATE!
[Fascinate Android Development] Schmarvin:
Will your other rom be able to upgrade to this? Runnymede SIII?
[Fascinate Android Development] akellar:
There's no proof anything works on this either....
[Fascinate Android Development] mkropf:
I want to believe all this is true but why no screen shots?

Link was supposed to been up yesterday.
[Fascinate Android Development] nitsuj17:
the nexus s (and many other phones have sdk ports) and whether or not the fascinate has stable/functional aosp ics anytime soon after source drops is mostly on whether or not jt tackles it
[Fascinate Android Development] CHANGiism:
What is so significant with a non-functioning SDK ports? JT got a booting ICS port to his tab already. Just because we get SDK port doesn't mean we will have full functioning ICS rom when it comes out. Just as nitsuj17 said, it all depends on whether or not JT and the teamhacksung guys tackle it.
[Fascinate Android Development] zerofighter1:
Maybe "later today" means something other than what I thought, and I don't want to sound impatient regarding something I know I can't do myself, but I think I speak for more than just myself when I say it's aggravating when you set a deadline about something that will hype people up (an ICS port for example), and then fail to keep people updated when something has clearly gone astray. Can we have a little more communication regarding the delay? Thanks in advance.
[Fascinate Android Development] akellar:
Pretty sure everyone should just relax about getting a broken, non-functioning SDK port anyway. In my mind this thred should be removed as its not development related until there is a link. At this point its just a general post.
[Fascinate Android Development] sneakysolidbake:
Will this have touchwiz since its for the fascinate? I hope so, if not I don't think I'm gonna test it.
[Fascinate Android Development] skynet11:
Which seems likely to me, unless he gets a Galaxy Nexus right away (sbrissen too)

Also, I would like to point out that nitsuj17 said "after source drops" - SDK ports are notoriously unstable and mostly non-functional, since they inherently create a mismatch between apps and framework
[Fascinate Android Development] zerofighter1:
It takes very little effort to post a reply, and even less to follow your own post. I'm not asking for a functional port - I'm asking him to follow up, which seems to be a fair request considering the hype he knew a post like this would create. I agree about deleting/moving though - he can repost if/when he has something to show for it.
[Fascinate Android Development] vdot:
@OP (enyo) - Ignore those who are insulting your potential to compile a good SDK release, and complaining that you haven't posted a download link yet. As a dev with 36+ years experience, I know what it's like to try to make folks happy with something, be optimistic on the target, and then get nothing but flak for it.

Some of us are patient, realizing you can't ever truly estimate something with anywhere near complete accuracy when it comes to these sort of things. In fact, more often than not, the things you thought would be the easiest end up being the hardest, and visa-versa.

Some of us

are

appreciative of

just your effort

and attempt to produce this ROM. So just ignore those who haven't even a clue what you're doing, and have never produced a free product for others in their life. It's so easy to complain...a few strokes by fingers that are accustomed to that sort of thing. Keep working as you have the time...and the rest of us are really looking forward to seeing the product of your labors.

If I had the time, I'd help you myself, but I need to concentrate on making money. Thanks again for your donated time and effort, successful or not, sooner or later...
[Fascinate Android Development] Enyo.:
Sorry for the delay but it totally started bootlooping after an hour of booting. I keep trying and the same result keeps coming. So just a little longer. Sorry for the delay again
[Fascinate Android Development] Enyo.:
The latest will be Saturday. So hopefully ill get it done earlier.
[Fascinate Android Development] zerofighter1:
I reread the replies just to make sure, and didn't see anyone really complain nor insulting like you're suggesting. I know what you're suggesting, but your post was needlessly long, so I'll refrain from doing the same by telling you what I think of it. It's not unreasonable to ask what's up when something is in a section inappropriately.

And thank you Enyo for the reply, that's what I was looking for.
[Fascinate Android Development] Enyo.:
I understood what you were saying. Its just I was just about to upload it a few days ago and it failed. So I'm making it again hopefully no problems this time.
[Fascinate Android Development] Enyo.:
It boots. For like 5 minutes. So I guess ill just port a sdk build from the nexus one. But I know now its the gingerbread .libs, and bin folder I used.
[Fascinate Android Development] Enyo.:
And ill make up for it. I really will. Its just that I don't have alot of time as I did when I started this port. So thats another reason contributing to the delays.
[Fascinate Android Development] zerofighter1:
Take your time. I was just curious as to why you didn't update after your initial time frame had expired. And despite what some would have you think, I'm sure we ALL appreciate your work, impatient though we can be.
[Fascinate Android Development] kidserious:
What exactly does that mean "unlike GB"?

Sent from your mom's bed
[Fascinate Android Development] suppliesidejesus:
There is a marked difference between "not fully functional" and "I guess we'll take your word for it."
[Fascinate Android Development] hawk687:
Not all of us want/expect it to be fully functional at such an early stage. Additionally, such an early port, especially considering the lapse of other non-fully-functional ports to other devices... may entice other and/or older fascinate developers that have since moved on to come back and dev for the fascinate.

All around there is no reason to put off this port as stated. Even if it is an SDK port, knowing it won't be fully-functional without source, its still beneficial not only for us end-users, but to the devs who will be working with this software for the foreseeable future. /rant

Keep up the good work enyo and get stuff done when you have time, dont rush because us moochers are impatient. At the end of the day, regardless of how long we have to wait... we still owe our experience with this phone to you and other devs like you. Thanks!
[Fascinate Android Development] calebv2:
Apparently this is a fully working port well some what and yes it is also a nexus but this may help. http://xdaforums.com/showthread.php?p=18764641
[Fascinate Android Development] skynet11:
Yeah I changed mine to "froyo" earlier so I could install Madden '12 on my phone while running GB Pool Party :D
[Fascinate Android Development] droidstyle:
already been posted in the thread in general section;):p:D
[Fascinate Android Development] mkuehl06:
Well put good sir. As long as I have touchscreen, phone, data, sms and mms, I could give a **** less whatever else works. Don't use gps, don't use bluetooth. But then again, some people expect everything to be perfect. Which is almost impossible since this is an SDK port and not a source code rom. But sadly people have to ***** about everything.

Sent from my SCH-I500
[Fascinate Android Development] droidstyle:
it's alive...IT'S ALIVE!!Lol
[Fascinate Android Development] mkuehl06:
Looks sick droidstyle

Sent from my SCH-I500
[Fascinate Android Development] shorttripp86:
I'd love to see a working version (heck, I'd even take just a mostly working version) of this, but I must admit that this is beginning to feel awfully "birdman-porting-gingerbread-ish" with these sudden total system failures hitting right before it's supposed to be ready...
[Fascinate Android Development] shilohdrummer:
what works for you droidstyle?

---------- Post added at 09:55 PM ---------- Previous post was at 09:55 PM ----------

hear droidstyle's voice
[Fascinate Android Development] droidstyle:
Ha Ha na man it's not true android 4.0. The screen shots are just the new ics 4.0 launcher w/ ics 3d theme for cm7 from syndicate. Looks decieving tho don't it?
[Fascinate Android Development] Schmarvin:
Does messaging (SMS/MMS) work? Also, what do you mean touchscreen (2 finger)?
[Fascinate Android Development] xgunther:
The ICS launcher by Syndicate is so cheesy/gimmicky IMO. Plus it's always crashing for me. I prefer CM7 ICS theme with themed ADW launcher.
[Fascinate Android Development] droidstyle:
I was on that setup previously... syndicates ics launcher works pretty good for me. not quite as snappy as adw but its new, it will get better with updates.
[Fascinate Android Development] jt1134:
This.

More interesting things to do right now. Like fapping.
[Fascinate Android Development] joshkoss:
ok peoples. Enough flaming! This is ridiculous....

I'm locking the thread till I get to work. Then I'm gonna issue some warnings for all the immature flaming and clean this thread.
[Verizon Droid Charge] Hughes4123:
So I have the Charge, it's stock. I've added a few apps but that's it. Here in the last couple of weeks when playing Pandora or the music loaded on the phone it just stops. It doesn't exit the player, just stops. At first I thought it was just Pandora, so I tried to listen to my music loaded on the phone and it does it as well. Does anyone know what's going on? It didn't do that before. I don't know what's changed, Maybe an upgrade?:confused:

Any thoughts?

Thanks

Bryan

Oh, and this will happen with the screen on or off.
[Verizon Droid Charge] jupo:
Had the same issue on stock, Pandora would act as though I had paused it. I would just tap pause and it would resume playing again.

Oddly, I have not had the same issue since flashing the EP3HA debloat & updated kernel.
[Verizon Droid Charge] Sabersix:
Same issue here. Just hit play and continue listening. It doesn't happen all that often.
[Verizon Droid Charge] Hughes4123:
I went to the last place on earth to get answers A VERIZON STORE, and they called the tech people and there have been no known complaints about this. They suggested a hard reset. I've been listening to my music (loaded on the SD card) and it's stopped at least 5 times. I think it's the player. IDK.

I wander? I know that if you unplug the speakers/headphones it will pause the music. I wander if the connector on the phone isn't getting hot or something and disconnecting. I'm gona listen to it on the speaker and see if it still happens.
[Verizon Droid Charge] Kryptonian_Knight:
I get it all the time
[Verizon Droid Charge] anoninja118:
sounds like it could be a number of things: bad audio chip, bad 3.5mm connector (either in the phone or headphone plug is defective/not enough rings or whatever on connector to work properly), could be the Pandora app or music player app being retarded... you would have to try different headphones, different apps, using your headphones on another Charge if you could and see if it still happens, clearing app data/cache or uninstalling/reinstalling the apps... idk just my 2 cents, I've never had audio problems on my Charge
[Verizon Droid Charge] Hughes4123:
Normally I'd agree, however like I said this just started. I've used this particular speaker set from day one. I bought this phone the day they came out and I've used the music player and pandora from the day I bought it. I just started having this issue last week. To day, on the way home (hour drive) I let the mp3 player play through the speaker. By the time I got home it stopped. But not in the normal way. There was no sound but the player was still playing. I stopped it and then restarted and it still had no sound. I made a call using the speaker and that worked. After the call I tried the audio again and what do you know, it worked. So that really doesn't tell me anything lol.
[Verizon Droid Charge] Hughes4123:
So I gave in and did the hard reset. And as I thought, nothing changed. It still stops playing. The only difference is now I have to redownload my apps. I think I'm going to set up my video camera and let it record it and then take it into the store. That way they can see that it does it with both internal and external programs. Then see what they say. I do have the insurance, I wonder if they would change it out?
[Verizon Droid Charge] anoninja118:
sounds like its defective hardware then, maybe the sound card's going out... and they should be able to switch it out under warranty so you don't have to pay the deductible or whatever for Asurions insurance claim

blazing through on my 4G Droid Charge
[Verizon Droid Charge] Hughes4123:
Samsung wants me to send it in, but this is the only phone I have. I do have the insurance from VW so I guess I'll be seeing them this weekend.

Oh, here is a funny.

So I e-mailed Samsung and explained my issue. I was told to transfer the music to the phone that way we could see if it wasn't the SD card.:eek: