yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] Tk-Glitch:
I'll eventually push an update today with recovery fixes and additions.

As it seems to be different between devices, I'd say it could or will help in some cases, but probably not for everyone.

On my i9000 for example I don't have any SOD with wifi and GPS.. Anyway, as always, reports are welcome :)
[Fascinate Android Development] sageDieu:
I just turned on DIDLE, wifi and GPS and made sure I was connected to wifi and everything, and no sleep of death after letting it sit for a few minutes. Before beta 6 it would usually SOD just turning on wifi and locking the phone with DIDLE enabled. I will keep it all on for today and report back if there are any issues.

Sent from my AOKP SCH-i500
[Fascinate Android Development] djk21108:
Seems great so far. With the newest THS ROM and this kernel, I seem to have lost screen orientation switching.

My phone won't go landscape, and it looks like I have the option enabled.

Has the accelerometer been nuked accidentally?
[Fascinate Android Development] ssewk2x:
Yes, that's a known issue. Sbrissen is working on it on the ths side. I may try to look into it myself if he takes too long, lol.
[Fascinate Android Development] djk21108:
Hehe, thanks man.
[Fascinate Android Development] kuronosan:
Not quite sure how to work touch recovery. The buttons at the bottom aren't too helpful. Am I missing something?

Sent in an Ice Cream Sandwich from my SCH-I500.
[Fascinate Android Development] sixstringsg:
Buttons at the bottom don't work. Press the capacitive buttons underneath to do the same functionality.
[Fascinate Android Development] neh4pres:
Anyone?
[Fascinate Android Development] shag_on_e:
I thought at this point there just isn't an app to control it yet. I've seen on the NSTools thread where it's been brought up, I'm sure he'll integrate it soon...

~~~~There is no spoon~~~~
[Fascinate Android Development] sageDieu:
welp, didle is still broken. kept it on all day and had multiple SODs with wifi, so it is still an issue... seemed to be less of one and not as quick to die as before though.

Sent from my AOKP SCH-i500
[Fascinate Android Development] sixstringsg:
As we have said multiple in the past, there is a reason that Samsung took Deep Idle out of their GB builds. Deep Idle IS NOT going to work for everyone, and there is nothing we can do about it. There might be things that can be done to fix it, there might not.
[Fascinate Android Development] shelby04861:
I am a little confused at this point. I tried downloading the originally updated link a couple times yesterday and could not do a backup. I did clear cache and dalvik , but I can't yet do a backup. It is no buggy, I just wasn't sure if I truly was doing some wrong. Thanks
[Fascinate Android Development] Stephen.k.spear:
known that it was broke its fixed just not released yet.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] bobloblaw1:
Please don't crush me like a bug with this suggestion ;)

Now, I know I'm comparing apples to oranges or ummm stale gingerbread to rich creamy ice cream, but imoseyon was able to implment both the Samsung and ezekiel deep idle methods (at different points in developmen, of course) in his Touchwiz (trololol) Gingerbread lean kernel. It seemed like his implementation worked well for everybody and I don't think there were any complaints.

I don't know if any of the code there would be useful or worth the effort of porting but I'd figure I'd mention that it is possible to get it to work on Gingerbread and point you to the resource.

Apologies again if this is a completely stupid suggestion.
[Fascinate Android Development] sageDieu:
yes I know, I had asked earlier if some of the changes in beta 6 might alleviate the SOD issues a bit, so I did some testing and was just reporting back. I wasn't expecting them to be gone, just hoping!

Sent from my AOKP SCH-i500
[Fascinate Android Development] droidstyle:
edit nevermind!
[Fascinate Android Development] djk21108:
Does anyone have the experience I have with lots of sleeps of death (DIDLE off) often requiring a battery pull?

Do we have the option to play with leakage anymore, because this is reminiscent of what used to happen when I installed a kernel with the wrong leakage.

OC and UV are all at stock.

This issue isn't present when I use the stock kernel, either.
[Fascinate Android Development] shag_on_e:
Adjust int voltage using NSTools to match the values of the leakage you found to be stable for your phone on the older versions. Int voltage is our new way to fine tune our leakage settings kinda.

~~~~There is no spoon~~~~
[Fascinate Android Development] djk21108:
I never really messed with int voltages. Does anyone have a good approximation of what someone on high leakage should put?

Edit: Found it in OP.

Still, though, does anyone have a lot of problems with SODs even on stock settings?
[Fascinate Android Development] shag_on_e:
On this kernel stock settings may not be suited for you. It's designed for high performance, so for me it's more stable now that I've taken the time to find the right settings for my phone. I haven't had any SOD's. Once I found my sweet spot, I baked up the settings in NSTools so after flashing anything I can jump right back.

~~~~There is no spoon~~~~
[Fascinate Android Development] djk21108:
Thank you very much for the support. I'll keep it in mind!
[Fascinate Android Development] tonu42:
I don't know what it is but since like beta 5 my phone has felt considerably laggier. Not so much sod but like performance lag which is weird cause I am at 114 live oc. Maybe its cna 1.5.5 because aokp didn't seem to lag. I'm switching when I get home. Will report my findings.
[Fascinate Android Development] sarkozy:
Same here, but with AOKP. It seems to be smoother with a simple bump to the 1200MHz step, and no LiveOC.
[Fascinate Android Development] shag_on_e:
I played with LiveOC a lot and I've found too much will slow you down. I go for a higher max frequency with a tiny bump of LiveOC and mine is definitely flying. I'm rocking AOKP b28 right now.

~~~~There is no spoon~~~~
[Fascinate Android Development] tonu42:
CNA 1.5.5 still feels like it was a port. I remember the "port" version of these roms were smooth but not like super smooth, cna still feels like a port, not a build, idk why. Like aokp 28 feels a lot better now.

Not that it matters, but I should have ran a quadrant to see which one was higher.
[Fascinate Android Development] droidstyle:
set you background process limit to 4...seems to get rid of the lag.
[Fascinate Android Development] tonu42:
I did that and cna was still slow as hell. AOKP is much much faster.
[Fascinate Android Development] ekowanz:
Can u explain more about this tk?

Im non verizon user/outside US. And i can't get the data working. I use aokp 28 here..

So now i have to back to glitch beta5 for ths6.1 in order to get the data back on.

Sent from my SCH-I500
[Fascinate Android Development] ssewk2x:
Ok .. so I managed a "fix" for sensors in the Glitch kernel. Based largely on Sbrissen's work and insight, but with a lot of my own hacking and stuff, too. I'm not sure if it's all quite right, but all of the sensors (including orientation) are reporting semi-sane values in Elixir, and other apps as well (gps status, etc).

There are a few Caveats:

1. It seems to hold the CPU to a high frequency in spite of showing small utilization (like around 1-3% in elixir). I've gotten around this to some extent by switching from "conservative" to "lazy" governor. I remember something like this in the past, but no idea what the solution ended up being.

2. The orientation sensor doesn't seem to start talking right away. It takes a lot of time to actually come up and start reporting values in elixir. Very strange.

3. The rotation delay control in aokp seems to be .. odd. If you set it for anything less than 100ms, it works just fine. If you set it for over 100ms .. it doesn't work at all. I will have to investigate this more, but for now, I recommend setting this to something under 100ms. The default is 200ms, so if you flash this kernel and your auto-rotation breaks, and you don't look at that value first before you post to complain, I'm going to kill -9 you.

For this reason, I'm reluctant to call this totally fixed just yet, and therefore have not initiated pull requests. If folks want to try this out and confirm my results, though, I'd be very very happy.

Anyway, the source for what I've done is on my github and partially on that of the glitch kernel organization:

https://github.com/Efpophis/android_device_samsung_aries-common/tree/sensor-fix - device tree for sensor fix

https://github.com/GlitchKernel/Glitch/tree/orientation_exp - kernel changes for sensor fix

http://dl.dropbox.com/u/28682151/Glitch-kernels/CM9-fascinatemtd-Glitch-B6_sensor_fix.zip - flash in CWM
[Fascinate Android Development] Sheradrax:
Does this address the mounting issues for backups and restores as well? That's pretty much the only thing stopping me from using beta 6.

Send from one twisted fassy
[Fascinate Android Development] yonith:
My compass app is now alive and kicking! Thanks ssewk2x, you da man!

UPDATE: Just an observation, my Bull Whip app (don't judge me) takes considerable more force to trigger than on the pre sensor fix glitch build

Samsung Fascinate, AOKP build 28, Glitch b6 sensor fix
[Fascinate Android Development] Stephen.k.spear:
those have been resolved and new builds are coming, but this does not fix the restore boot loops issues. Those are in the kernel not the recovery.

Edit they could be in there I don't know which recovery sswek2s used.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] ssewk2x:
I used whatever is the latest recovery on the glitch kernel github. I don't know what's in it or what it fixes and doesn't. I said in my post that this is an attempt to fix sensors, nothing more.

Truthfully, i probably have to re-work a bunch of the sensor stuff, too, and if sbrissen comes up with something that's better, I'll end up nuking all this and kanging his stuff. I put this out there now in the hope that folks might be able to test and see if I'm even close to the right track is all.
[Fascinate Android Development] SotYPL:
ssewk2x your kernel is working almost perfectly for me. Compass is working fine, light sensor is much better (on original glitch b6 it only showed 6 or 5000 lux, nothing between) but auto rotation doesn't work at all. Elixir is showing orientation values just fine but screen doesn't rotate in any app or launcher. I'm on latest CM nightly so I can't change rotation delay.
[Fascinate Android Development] shag_on_e:
I'm also getting great results man. Sensor reading apps seem to have some funky outputs, but rotation and compass are working for me, light sensor is a little off (not changing much with auto brightness), the arrow isn't pointing in maps, but it's been acting weird last couple updates anyway. Also my CPU seems to be acting normal as well. As usual thanks for fighting the good fight friend.

~~~~There is no spoon~~~~
[Fascinate Android Development] droidstyle:
auto rotation works on my device...
[Fascinate Android Development] mleonm5:
Not mine, also on the sensor fix. Temple run shows it detects fine but it just won't rotate the screen on any app.
[Fascinate Android Development] ssewk2x:
Ok. I will attempt to iron out the auto rotation issue soon. Of course, after i posted this build, i got to thinking and have a bunch more ideas to try and almost no time to try them.

I may have inadvertently brought back some old code with the orientation thing. There is probably a better way that won't be so wonky. Stay tuned.
[Fascinate Android Development] mrjake1970:
just an fyi..ran the new beta (before this latest fix) and ran into 2 uh oh's..

pretty good battery drain from a wakelock with media server and my bln quit staying lit after 2 days..started doing the come on for 10 seconds and timing out.

when i read that maybe some old code may have inadvertendly gotten merged it reminded me to post this..

AOKP M4 :: Glitch V14B5/6.1 Kernel :: EH03 Radio
[Fascinate Android Development] ssewk2x:
When I said "old code" I meant strictly related to orientation sensor driver stuff. I haven't touched BLN or any of that other stuff.
[Fascinate Android Development] shag_on_e:
I don't know if y'all have seen this but arifhn put a test version of NSTools out with selective LiveOC and option to load settings in init.d and wants testers. Here it is...

http://xdaforums.com/showthread.php?p=24137337

[APP] NSTools v1.15 for managing various Ezekeel's MOD and tweaks

~~~~There is no spoon~~~~
[Fascinate Android Development] Tone_Capone:
External SD?

I found a pretty big issue with recovery.

When i went to restore a NANdroid after flashing the new kernal, the recovery only allows restoring recoveries from an external SD card. The Fascinate recognizes the SD as an internal SD, and when selecting the "restore backup from external SD" feature, recovery says the external cannot be mounted.

I had to restore through Rom manager to get my NANdroid to work.

Can this be fixed?

Thanks!
[Fascinate Android Development] sageDieu:
I do not have this issue.
[Fascinate Android Development] sageDieu:
trying it out, seems good so far. I'll watch CPU spy.
[Fascinate Android Development] Tone_Capone:
This was just after flashing Beta 6. Does recovery recognize the SD as external on your phone?
[Fascinate Android Development] ssewk2x:
I am pretty sure I've now fixed the orientation / accelerometer sensors for good in the Glitch kernel. Auto-rotation works on my device, as does the orientation / compass / everything else.

Here's a link to a test kernel with these fixes in it: http://dl.dropbox.co..._rotate_fix.zip

Source for the kernel changes is at https://github.com/G...orientation_exp

Source for the sensor library changes is at https://github.com/E...tree/sensor-fix

Please let me know of any issues related to sensors, and if you're a dev, feel free to kang away or suggest improvements.
[Fascinate Android Development] dave3588:
Link to your drop box is dead
[Fascinate Android Development] sageDieu:
http://ge.tt/7v9bdcF/v/0?c

Here's a quick-fix download, for some reason XDA cut his in the middle. Use this until he fixes it or whatever, and ssewk2x I can keep track of downloads and everything through this provider. (I prefer it to dropbox for file hosting like this)

(this also works great on phones, they have a quick little mobile UI, anyone can see the file size, type and download count)
[Fascinate Android Development] ssewk2x:
Crap.

I had to run out for a bit, but I'll fix it as soon as i can.

Thanks!
[Fascinate Android Development] sageDieu:
Yeah no prob. I can also host it on my dropbox or on a full personal server if you'd like, it'd be faster and has pretty much unlimited bandwidth.
[Fascinate Android Development] SotYPL:
Everything seems to be working fine this time. Auto rotation works, light sensor gives accurate values in elixir, compass works, cpu clock going down just fine. I switched to AOKP 28. Thank you.
[Fascinate Android Development] shelby04861:
confirmed working here
[Fascinate Android Development] sageDieu:
Alright guys here's a better link, should be much faster than the one above. Again, ssewk2x, if you want either of these taken down let me know; this mirror should be a lot faster and has no bandwidth issues like dropbox sometimes does. Let me know if you need anything else hosted here now or in the future.

http://encounterpc.com/android/stevespear426/CM9-fascinatemtd-Glitch-B6_rotate_fix.zip
[Fascinate Android Development] sixstringsg:
Here's the latest test kernel from ssewk2x: http://efpophis.glitchteam.com/CM9-fascinatemtd-Glitch-B6_rotate_fix.zip
[Fascinate Android Development] ssewk2x:
Oh, please mirror the heck out if it, i appreciate it! You all are awesome :)

Can you do me a favor and post those links to the thread on rootz, too? Don't want to leave those folks out in the cold..

Thanks again! Glad this finally works :)
[Fascinate Android Development] sageDieu:
on it!
[Fascinate Android Development] sixstringsg:
Did you not get my e-mail with the FTP info?
[Fascinate Android Development] ssewk2x:
I did, i just haven't gotten used to using it yet, lol. And now that I'm on the road, i won't get to it until tomorrow at the earliest.
[Fascinate Android Development] shelby04861:
Made a successful backup as well

Sent from my SCH-I500
[Fascinate Android Development] Stephen.k.spear:
The question is will it restore?
[Fascinate Android Development] sageDieu:
I can make backups all day but as soon as I restore I get a bootloop that I have to Odin out of. Haven't tested on this sensor fix one but I can't imagine it would be any different since nothing was changed.
[Fascinate Android Development] shelby04861:
Not sure if I want to try restoring at this point. I am just happy with what we have and that I haven't had to Odin back to stock and reflash everything all over again in a while.

Sent from my SCH-I500
[Fascinate Android Development] speedingcheetah:
The touch recovery is quite nice. However, the Glitch red background and graphics on the bottom of the screen makes it hard to read the text of the recovery itself, especially when u list the constants of the sd card.
[Fascinate Android Development] pdubsfc:
I got it to backup and restore successfully! No issues. When I first flashed b6, I couldn't get it to initiate a backup. Awesome job! Thanks ssewk2x!
[Fascinate Android Development] thisguy23:
OK everyone please don't blast me, but through each update, rom, and kernel I've been keeping track with two methods: quadrant and how it feels. Last week quadrant for example ram was breaking 600. Now with same rom clean wipe and all I can't break 350 even with live oc and oc. The way it feels is much slower too. I run all latest updates for glitch akop 28. And same results after stock Odin. Thoughts?
[Fascinate Android Development] Tone_Capone:
Edit: Nevermind. I flashed the latest kernel with the sensor fix and my backup/restore issue was solved!

Thanks!
[Fascinate Android Development] ssewk2x:
Well .. that's very interesting, but I had nothing to do with it. I didn't touch anything that should possibly be related to backup / restore, and I can't for the life of me come up with a reason why what I did would have any affect on it at all.

It's entirely possibly that you just got lucky .. I wouldn't call it good if I were you until you've seen several backup/restore cycles with no issues.
[Fascinate Android Development] sageDieu:
when I get home and have Odin ready I'll test it. if it's still broken in any way then it'll show itself for me, I've had it happen many times. :p
[Fascinate Android Development] pdubsfc:
Hey, I'll take what I can get. Call me lucky. I don't usually do multiple backups/restores on the same setup. If I can get one to stick per new ROM flash/kernel flash, I'm happy. It is a little strange that it would finally allow me to even make a backup after your sensor fix, although you didn't touch that.
[Fascinate Android Development] 00ffej:
Any chance we can implement this patch? http://xdaforums.com/showthread.php?t=1571215
[Fascinate Android Development] ssewk2x:
I'll look into it.
[Fascinate Android Development] sageDieu:
I sent it to six as soon as it came up and he said it should be pretty easy as far as he knows. I think he was going to take a look at it.
[Fascinate Android Development] mrjake1970:
MY ****Z IS BORKED YO, CAN YOU FIX IT?

LOL sorry had to throw some 2.2 superclean OP fun in there..

flashed the latest test, and caught a nasty bootloop after creating a backup. i was toying with flashing build 28, so i thought i should make a new nandroid.

backed up fine, rebooted fine.. then about an hour later i rebooted to recovery to flash the 28 build. it loaded recovery, after about 10 seconds the screen flashed 2x and then rebooted itself into milestone 4.

i was like hmm thats weird, maybe i accidentally hit a key.. so i rebooted to recovery again.. this time the glitch splash screen came up, flickers once then bootloops to hell..

going to odin out and start over.. no biggie.. i know this is the issues we face when we play with the epicness :)

i think the bootloops have to do with something borking during the backup, because it ran just fine until i tried to get into recovery again.

EDIT : so to follow up, i odined back, to ed05, flashed bootloader and radio after and then flashed build 2 to get to 4.0.x. used the stock recovery to restore my backup and in same session flashed the original b6 kernel so i wouldnt have recovery issues. came up fine and is running smooth..
[Fascinate Android Development] sageDieu:
yeah I agree, when I did have the problems with recovery breaking stuff, usually what would happen is I would make a backup and then it would screw up the phone in some way, causing it to reboot not long after. after that it would be dead, just play the animation until I odined.
[Fascinate Android Development] Not_So_There:
Screenstate

I have been running the test kernel with the rotation fix (AOKP 28, using nstools) and I noticed that when I use screenstate scaling (glitchassv2 on, glitchondemand off) that after the phone sits for some time with the screen off it will not switch out of the off Governor once you turn the screen back on.
[Fascinate Android Development] JoeDat:
Google Maps not receiving compass data

I'm running the test kernel containing all the sensor fixes. Everything looks golden in Elixir and the compass app that I'm running. However, Maps doesn't seem to be receiving the compass data. When you click on the compass icon, the display should re-orient based on the direction you're facing, using the compass. When I click the icon, it doesn't do anything. In what seems to be a related issue, Navigation also doesn't seem to be receiving data. So, the sensors appear to be working for me. But, they're not passing their data to these apps. Anyone else encountering this?
[Fascinate Android Development] ssewk2x:
I just checked that out. It looks like it's a RIL issue of some kind .. gmaps apparently gets its data straight from the RIL and not our sensors. RIL is always reporting "bearing 0" in its update location message.

Not sure what can be done about that just yet.

Edit: also, I'm about to build a kernel with that fast-charge stuff in it. wish me luck.

Edit2: fast charge works, but you lose adb connectivity unless you shut it off under ROM control and reboot. But, if you need a quick charge and don't care about adb, it definitely charges the phone pretty freaking fast.
[Fascinate Android Development] JoeDat:
Ahh, understood. Thanks for checking it out so quickly! Seems as though you have a firm handle on the cause, so I'm not sure if the logcat will do you any good. However, here's a link as promised. I invoked the function in gmaps twice (which should turn it on, then turn it off).

http://pastebin.com/a1rMpgG9
[Fascinate Android Development] neh4pres:
I thought fast charge was not needed on our device because it always charges at full current
[Fascinate Android Development] sixstringsg:
Different thing from what I understand. This is for fast-charging over USB, so when you plug it into your computer it will charge faster. The other thing someone saw earlier was for faster charger over the power adapter. If that's not right, then ssewk2x will give you the right answer :)
[Fascinate Android Development] ssewk2x:
Yeah .. I goofed when I had said that. Sorry.

Anyway .. here's a test kernel with my final rendition of sensor fixes (shouldn't change functionality, it just made the code prettier) plus the fast charging stuff:

http://efpophis.glitchteam.com/CM9-fascinatemtd-Glitch-B6_sensors_fastchg.zip

Thanks to Six for the ftp account. And F**K AT&T for making things so that the only way I can upload stuff is through internet explorer. :mad:

Also, Six is exactly right.

Also, I love that there's an FTP site with my username in the URL! That's gotta be good for at least a little bit of nerd-cred, no? :D
[Fascinate Android Development] neozen21:
Hmm.. I just installed this kernel ontop of THS7.1 WITHOUT the sensor fix and the compass is still not working.

Should I install the THS 7.1 sensor fix too?

Thanks for all your great work!