yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] pntballer505:
Really? All right, must have missed that..
[Fascinate Android Development] ssewk2x:
Well, ****. :(

Not really. It might be radio interface code, which has always between flaky. According to jt, who had done pretty much all of the RIL work for this phone, Samsung has a pretty bizarre way of talking to the modem firmware.
[Fascinate Android Development] sageDieu:
As far as I have been able to tell from reading info from jt's posts and things about drivers over the past year of having this phone, Samsung SUCKS **** at writing drivers and things in a comprehensible way... that's just my observation as I haven't seen for myself but it seems like they're pretty bad at it. Or they don't want people figuring out how to modify them.
[Fascinate Android Development] ssewk2x:
Yeah .. it makes me think there's a Korean software developer somewhere over there who is coding job security into the software. Whether it's intentional or not, though, you're right: it does suck a bucket of dicks.

Edit: I think next time I'm bored, in going to go through and fix all the compiler warnings in the kernel source. That should be fun, and might fix a few things too.
[Fascinate Android Development] stalls:
I still get the random buttons every so often with the latest shot at it... It seems to be even less then normal though. A LOT less!
[Fascinate Android Development] k_nivesout:
Flashed the new test kernel earlier today, and the phantom presses seem to be much less frequent, but still present. When I experienced it, it was right after an SMS came in so possibly data related? One strange thing that happened afterwards that I hand't experienced before was the soft buttons becoming unresponsive. It was strange, I was having data issues and then the capacitive buttons just stopped responding. Locking the phone then unlocking brought them back, but I hadn't run into that before.

It's nice knowing that it's being looked at though, who knows, maybe we'll see a breakthrough one of these days. Thanks guys, for all your work on this!
[Fascinate Android Development] ssewk2x:
Yeah, I think more and more it has something to do with data hand-off .. perhaps in the form of a badly configured GPIO pin or IRQ conflict or something. I was hoping the code change would filter out the spurious stuff, but it doesn't seem to - at least not completely. I've seen the issue where they become unresponsive, too, btw. I've found that sometimes I can get them back by tapping the back button once, and if that doesn't work, then like you said, lock / unlock will do the trick.

I'll keep at it and get there eventually.

"Keep going." -- Masaaki Hatsumi, 34th Ninja Grandmaster
[Fascinate Android Development] pntballer505:
Since flashing v13, I noticed that I cannot flash

other mtd roms--they just abort.

Tried Rick's 1.12.2 and dfgas' 1.12.9. Both aborted.

Is this a v13 thing?
[Fascinate Android Development] Tk-Glitch:
No issue on i9000, and I didn't hear of any issue on others GSM devices as well. Maybe a Fascinate related thing. Ssewk2x may be more competent than me on this kind of issue, I can't debug this myself as I don't own the device.
[Fascinate Android Development] sixstringsg:
I just tested on a Fascinate, and it works just fine. Can you pull a log from recovery for me?
[Fascinate Android Development] pntballer505:
Thanks for the responses. All right sure, before I pull a log,

I should mention that I am on a different computer than usual. A mac.

I would assume that downloading the zip mtds should not make

a difference between pc and mac?!

Edit: Also, sorry but I don't know how to get the log cat to you after enabling it in recovery :/
[Fascinate Android Development] sixstringsg:
My primary computer is a Mac, all should be fine.
[Fascinate Android Development] k_nivesout:
I'm getting this too. Happens regardless of mac or PC. Tried redownloading files everywhere, ODINed back to stock, reformatted SD card, everything I could think of.
[Fascinate Android Development] ssewk2x:
Is this the same issue Six was telling me about earlier? Is it an md5 failure of some kind?
[Fascinate Android Development] pntballer505:
Thank you for confirming my sanity. Did you get it working?

And when did this start happening to you?

Also, where are the log cats stored?
[Fascinate Android Development] sixstringsg:
No, this is them having an issue flashing a different ROM than what they are on. Nothing to do with backups.

Once the phone boots, the log will be in /cache/recovery/last_log. You can get it with either ADB or Root Explorer.
[Fascinate Android Development] pntballer505:
Okay, thanks Six.
[Fascinate Android Development] pntballer505:
Don't really know what you need to see, but I enabled log....then went about flashing the zip.

Also, there was a lot more info in it, but i assumed this is

all you would need:
[Fascinate Android Development] sixstringsg:
According to the log, your download is bad from what I can tell. I don't know what "minzip: Missed a central dir sig (at 0)" is, but it says your download is bad right after that.
[Fascinate Android Development] k_nivesout:
The error it gives in recovery is: "filename"(bad) installation aborted", which looks like it usually does indicate a bad download. I was trying to flash ICS v4, that gave me the error, so I tried v3 and it worked. Went to go back to MIUI, so I ODIN'd back to EH03, flashed the CWM4 fixed for CM7, and tried to flash this weeks MIUI build. Got the same error so I went through re-downloading (on multiple computers), verified md5 sum, etc, and still got the same error. I reformatted my SD card because I thought that might be the issue, but no. Wasn't until I saw the post from pntballer505 that I realized it wasn't just my phone/SD card.

I'd get a recovery log to you, but I'm still waiting for my files to transfer back to the reformatted SD card before I ODIN again and try to flash back to MIUI 12.2.11, which is what I was on before all this happened... So as of yet, I haven't gotten back up and running. Didn't run into this until today, when I wanted to flash a different rom.
[Fascinate Android Development] sixstringsg:
So are both of you running MIUI? does this happen with other ROMs?
[Fascinate Android Development] k_nivesout:
Yes I was on MIUI. I can't really figure out why it happens with some roms but not others, jt's ICS v4 wouldn't flash for me, but v3 would. This week's MIUI wouldn't flash for me, but I'm hoping last week's (which I've been on all week) will work.

The strange thing is, I first got the error when trying ICS v4 (flashing over MIUI). Didn't work, so flashed v3 (from MIUI) which worked. Wanted to go back to MIUI, so I odin'd EH03, then CWM4 for CM7, and tried to flash the newest MIUI with that and got the same error. It doesn't seem like it would be a glitch issue since I ran into the same problem running the non-glitch recovery, but I could be wrong? Just saw another user with the same issue posted in this thread.
[Fascinate Android Development] sixstringsg:
If it happened when you were running stock recovery (and thus stock kernel) then it can't be Glitch. Ask around in your kernel thread.
[Fascinate Android Development] pntballer505:
Ya I'm running Miui. And I tried to download different zips

several times and check md5 sum to make sure it wasn't that.

Of course I'm not saying it is the glitch kernel, but from what

I've noticed, I have not been able to flash mtd updates since using v13.
[Fascinate Android Development] k_nivesout:
Indeed, good sir. Unfortunately there's no thread for discussion of the MIUI build I was trying to flash, and I hadn't seen anyone else having difficulty flashing ICS v4. Thought there was something wrong with my **** until I saw pntballer505 with the same problem. Sorry for troubleshooting in your thread! :o
[Fascinate Android Development] sixstringsg:
Honestly, I am stumped.

That's fine, I don't mind it being in here. I just don't know an answer to your problem.
[Fascinate Android Development] pntballer505:
I'll flash another kernel, then do some data wipes and attempt to flash

another mtd rom. Will inform you.
[Fascinate Android Development] ssewk2x:
Since we all have recoveries that are basically cwm with tweaks, it may be something to do with cwm, and that's why you're seeing it on all these other roms. I'll check things out as soon as i can.thanks for all the good info.
[Fascinate Android Development] neh4pres:
Odin fixes all.. Just saying
[Fascinate Android Development] skynet11:
Trololololol!

Has anyone seen John Connor?
[Fascinate Android Development] wessiide:
The random key presses and pop ups everyone experiences I used to get often in low signal areas also. But I feel like its worth mentioning that having moved to jts ics for a couple weeks I have never experienced a phantom key press. Maybe just move glitch onto ics compatibility and just move on from the ginger bread bugs? ;)
[Fascinate Android Development] neh4pres:
That would be great if it was gingerbread.. Fingers crossed.. And six stated glitch will be moving that direction.
[Fascinate Android Development] sbenson1226:
Is there any way to keep the soft key lit while the screen is on? It's becoming a pain to hunt for these in the dark? Running CM7 nightlies 11/16.
[Fascinate Android Development] ssewk2x:
I should look into a way to configure that. Some people like the timeout feature we have now, others (like yourself) don't. We've had it both ways in the past and either way, people complained.

The answer, for now, is no. Maybe next time I'm bored I'll see about making that a "yes, and here's how ... "

On another note:

Commradesven, of KGB kernel fame, pointed me in an interesting direction yesterday when he hinted that I should be looking at the dpram driver code. So, I took his advice and compared our kernel with his (which is working great on my wife's fascinate, btw), and I found something kind of shocking: there's a GPIO pin called PDA_ACTIVE, and our kernel configures and uses one pin, whereas the TW kernels configure and use a completely different one! Further, other code in OUR OWN KERNEL expects the PDA_ACTIVE pin to be the same one that the TW kernels use in their dpram driver code! So I thought to myself, "What the hell??" and made the change.

I've been running with the resultant kernel for a few minutes now, and have tested a few more things that I usually do - mainly stuff involving the radio, since the dpram driver seems to be getting some of its signals from there. It all seems to work fairly well. I noticed that the wifi/3g hand-off seems to actually kind of work a little better than I thought, too. For example, I can send myself an MMS message and have it come through ok with WiFi on -- has that been fixed before? I'm not sure. But toggling wifi on and off while doing stuff seems to not trash my data connection anymore either. I also have yet to see a phantom keyboard, but that doesn't mean the bug isn't still there.

Long story short: I'd like to have my Faithful Testers try this build out. Here's a linky to the Fascinate build:

http://dl.dropbox.com/u/28682151/Glitch-kernels/Glitch_Efpophis_TEST_12_dec_2011_1230.zip

Thanks, and please let me know what you think, especially if you see any phantom keypops, etc.
[Fascinate Android Development] sixstringsg:
Tk has decided to work on going back to LED notifications for V14, in which case you can configure the time out yourself.
[Fascinate Android Development] ssewk2x:
Oh, good! I won't worry about it, then :)
[Fascinate Android Development] GizmoDroid:
I'm a big fan of this commit:

Allow backlight timeout adjustment from userspace

https://github.com/teamhacksung/samsung-kernel-aries/commit/07dc0db2963d963605f6c49cd0fa755f152a1730
[Fascinate Android Development] mrf582:
This is ****ing interesting man!
[Fascinate Android Development] ssewk2x:
Ask and ye shall receive. Sometimes.

To adjust the timeout:

1. figure out how long you want it to wait before timing out.

2. if the answer to #1 is "forever," then your timeout value is zero.

3. convert your timeout value to milliseconds. So, if you want 5 seconds, your timeout value becomes 5000. Get it? If not, stop right here and don't bother.

4. write your timeout value to /sys/devices/virtual/misc/notification/bl_timeout, i/e: echo "5000" > /sys/devices/virtual/misc/notification/bl_timeout

Enjoy!

Running a couple hours now and haven't seen anymore phantom keypops. Well, I take that back. I reverted the GPIO pin change just for fun, and I saw the keypop immediately on the next reboot.

Also, remember how I asked about MMS with wifi? Turns out it will work, as long as you send an MMS to someone over 3g first. My changes apparently had nothing to do with this, so sorry for getting anyone's hopes up on that.

So this version I'm posting here has the GPIO pin fix that I think fixes the phantom keypop, plus the adjustable bln timeout.

http://dl.dropbox.com/u/28682151/Glitch-kernels/Glitch_Efpophis_TEST_12_dec_2011_1230.zip

I left the first one I posted up there, too.

Let me know what you think.
[Fascinate Android Development] PhoenixPath:
This wouldn't be on the app at all yet, would it?
[Fascinate Android Development] sixstringsg:
It will soon, this is the first I have heard of this being implemented, so we didn't have it written yet.
[Fascinate Android Development] GizmoDroid:
Thank you!

Only problem is that I'm getting a "cannot create bl_timeout: directory nonexistent" error when trying to write the file.

Also, the CM7 stock kernel has it controlled by AriesParts in Settings > Device Settings > Backlight Timeout. I couldn't find what code flags this to enable it. I was hoping it would automatically be enabled once the commit I posted was merged in, but alas, it is still grayed out.
[Fascinate Android Development] k_nivesout:
Well, I've been keeping up with the test kernels, just flashed the new one with adjustable button timeout. I haven't played with that feature yet, but I'm stoked to report that I haven't been having issues with phantom presses! I'll keep you guys updated, and thanks so much for the work on this kernel.
[Fascinate Android Development] skynet11:
Stupid question (please don't shoot me): did you mount sys/ as rw? Or does that apply to this situation at all?

Has anyone seen John Connor?
[Fascinate Android Development] sendan:
pew pew pew!!
[Fascinate Android Development] ssewk2x:
Just remember this is a test kernel, not official or anything like that. I threw that code in to see if it worked. If it's broke, I'll get to out when i get to it. Right now, the phantom key pop is more important. Any findings on that?
[Fascinate Android Development] k_nivesout:
I haven't had the opportunity to test it in low-signal areas, however I noticed that it would mostly happen for me with the data handoff (3g/1x) when SMS messages were sent and received. I'm rarely in areas with poor signal (somehow) so I'm not sure on that front. Your kickass test kernels have resolved the issue though, I can't seem to remember the phantom presses happening with the test ones you've posted.

HUGE :thumbsup: :)
[Fascinate Android Development] neh4pres:
I get several a day at home.. woo be there in a hour or so. I think a fair test would be a full night without any. I will also do some downloading to see if this fixes the 3g stall issue.

Thanks
[Fascinate Android Development] neh4pres:
Well.. Got 1 keyboard popup. Looked at status bar to see that the phone was syncing. Data seems to be a lot more stable.. What i mean by that is, i can have a download going, walk to my room where i have horrible 3g, then walk back toward my indoor signal booster and the download starts moving again immediately. There used to be anywhere from a minutes pause, to me having to tease the radio by opening up something else that uses data. Also, i notice i rebooted in this cell coverage black hole i call home and did not have to toggle airplane mode and data a thousand times to get 3g working properly. I am also now surfing xda in my room which most definitely should cause keyboard popup.... Hmmm.. I'll keep you updated

Thanks
[Fascinate Android Development] neh4pres:
Sadly this does not fix the softkey glitch. Just got repeatedly attacked by my keyboard.
[Fascinate Android Development] ssewk2x:
****. Back to the drawing board. I still think I'm looking in the right place, tho. That dpram code is an unmitigated clusterfuck.
[Fascinate Android Development] neh4pres:
i think their coded in Korean. Lol
[Fascinate Android Development] knoxjon:
I can definitely tell you these changes helped. I went to my major problem area, and I can't remember the last time my phone worked so well. I didn't get a single keyboard popup, although the back key went off a few times.

BUT. It took me a few minutes to figure out the biggest difference: the phone for the first time with cm went from 3g to 1x without reporting having 2 bars while actually getting nothing.

Simply miraculous for me.
[Fascinate Android Development] neh4pres:
The data in low service is absolutely amazing now.. I can now go from page to page and app to app laying in bed where before mostly i would be going from airplane mode on to airplane mode off to get the stupid pages to load. Great work.
[Fascinate Android Development] ssewk2x:
Well .. I'll call that progress, then. I honestly have no idea how what I changed is helping your data stay on, but I won't complain if it's helping. Truthfully, though, it's not anything to take any credit for - merely a happy accident, lol!

The back key going off like that is, I think, the result of the same problem - something causing random keypresses on the touchkey pad. It's just different keys sometimes.

Bugs like this are such a pain in the ass to find - especially without proper hardware documentation (schematics, manuals, etc.) .. stuff that the Samsung developers should have access to, but then why the hell are they producing such crap? </rant>
[Fascinate Android Development] stalls:
How do I create the file bl_timeout? Sorry jus need a lil push :)
[Fascinate Android Development] sixstringsg:
Have you tried

echo "5000" > /sys/devices/virtual/misc/notification/bl_timeout

In terminal emulator/ADB? If that fails, do:

touch /sys/devices/virtual/misc/notification/bl_timeout
echo "5000" > /sys/devices/virtual/misc/notification/bl_timeout

Then you should be good.

Edit: I'm wrong, ssewk2x said it should be there if you're flashing the right kernel.
[Fascinate Android Development] stalls:
I dont have the file bl_timeout. I can get all the way to /sys/devices/virtual/misc/notification/ but there is no bl_timeout file...

Am I missing something here? or am i jus tarded?
[Fascinate Android Development] GizmoDroid:
That's how it's supposed to work, but its currently not working:

# echo "5000" > /sys/devices/virtual/misc/notification/bl_timeout
cannot create /sys/devices/virtual/misc/notification/bl_timeout: directory nonexistent

# touch /sys/devices/virtual/misc/notification/bl_timeout
touch: /sys/devices/virtual/misc/notification/bl_timeout: No such file or directory

As far as phantom key presses, I've only had 1 so far on the newest test kernel. In the past, mine have exclusively been the back key, yet this one was the home key. Weird?
[Fascinate Android Development] ssewk2x:
Then somehow you're not running a kernel that has the support in it. The bl_timeout file should be created by the kernel and exist in that path automagically - no need to create it.
[Fascinate Android Development] k_nivesout:
I'm also getting the same thing they're getting when trying to execute the commands with terminal emulator. I'm on the last test kernel you posted, I'm assuming they are as well?
[Fascinate Android Development] stalls:
Hmm thats weird... Guess Ill try an reflash it now

Still nothin there?
[Fascinate Android Development] sixstringsg:
Just a fair warning: I am doing server maintenance/migration this evening, therefore the site might be down fore some periods of time. If you need a file while it's down, PM me and I can hook you up.
[Fascinate Android Development] pntballer505:
Well...I can confirm that the rom abort issue is not kernel related.

Tried it with Jts as well. Also tried a full wipe before each.

Still can't flash one of the mtd updates, strangely.

So I quit for now. No idea what's going on there!
[Fascinate Android Development] ssewk2x:
Ok .. you guys having trouble with the bl_timeout file, please post the following information:

1. the output of the command 'uname -a' run from a terminal or adb shell.

2. the output of the command 'ls /sys/devices/virtual/misc/notification'

3. the output of the command 'ls /sys/devices/virtual/misc/backlightnotification'

4. the output of the command 'cat /sys/devices/virtual/misc/backlightnotification/enabled'

Yeah, all of those from terminal or adb shell. Thanks.

FYI, I'm running the kernel I posted that was built at 16:26ish on 12/12. I see the bl_timeout file right where it should be.
[Fascinate Android Development] k_nivesout:
Sorry, I'm not sure how to copy the output from terminal emulator over to my laptop or xda app. I'm assuming there's an app that does this but I haven't had need for it yet.
[Fascinate Android Development] stalls:
ya i have tried all that but nothin works... I still dont have the file in there. I have even tried reflashin the kernel that you posted on 2434.

is there another that u posted an i an others have happend to miss it?
[Fascinate Android Development] ssewk2x:
No problem. I notice 2 things:

1. I don't think you're running the latest kernel. Note the timestamp on your uname -a output. It should be 16:26ish, yours is 11:something.

2. Your BLN is disabled - which is why /sys/devices/virtual/misc/backlightnotification/enabled has a 0 in it. Which means the timeout field is likely to not exist also. Try enabling BLN first, and then see if the file shows up.

Possibly. Rather than go back and find it, here is the link again:

http://dl.dropbox.com/u/28682151/Glitch-kernels/Glitch_Efpophis_TETS_12_dec_2011_1636.zip
[Fascinate Android Development] bdanders:
You might want to change the link in post #2434. It points to a different build than this one. That is probably the source of the confusion.
[Fascinate Android Development] GizmoDroid:
Problem solved :)

Glitch_Efpophis_TEST_12_dec_2011_1230.zip did not have the bl_timeout file.

Glitch_Efpophis_TETS_12_dec_2011_1636.zip does. It also supports the Settings > Device Settings > Backlight Timeout part of the CM7 settings.

Woot!

I also found that "110" is the lower limit if you manually want to adjust it to the shortest possible time:

echo "110" > /sys/devices/virtual/misc/notification/bl_timeout

Thank you ssewk2x, I've been wanting this for a long time, and I've been too busy to merge and compile it myself!
[Fascinate Android Development] k_nivesout:
Yep, it works perfectly with the kernel from the link posted on this page! Thanks guys. FWIW, I still haven't had any issues with phantom presses.

Edit: Got a BLN question. To enable BLN, I downloaded the BLN control app from neldar and enabled it through that. Is there any way to enable BLN without having to actually have the app/notifications? Say I just wanted to enable it to be able to control timeout of the softkeys. Could I just

echo "1" > /sys/devices/virtual/misc/backlightnotification/enabled

or am I understanding that right?

I like BLN, but it seems like having the button lights always on for notifications would be detrimental to battery life. Also tried "blinky", which was cool because you could control how long the lights stay on/off for, but I noticed some battery drain that I'm fairly confident was related to the app. I also could be wrong, the softkey lights might consume a negligible amount of battery, I honestly don't know.
[Fascinate Android Development] droidstyle:
Same here!!!!
[Fascinate Android Development] ssewk2x:
Ok, good. I also think you can set it to 0 in order to have it never time out, if you prefer that behavior.