yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Smasher816:
New market version should be pushed.

It has support for rom manager premium, a bug report button, and some other stuff.

Tell me if you have any problems or suggestions.
[Captivate Android Development] Captivate2010:
I just update and I have FC when try to use.

See what is the problem thanks.

This is the first time happening.
[Captivate Android Development] makelegs:
- ignore me...nothing to see here - 0.o
[Captivate Android Development] Smasher816:
Anyone else confirm that the new market version is not validating?

It should work. It works ok on my version (i don't have the market one, i made the app).

Make sure that you are connected to the internet and stuff. If everyone says its broken then six didn't test very well :P, and proguard is being stupid about deleting stuff again.
[Captivate Android Development] vercro:
I'm getting FC's every time I try to select any of the manual options. Selecting install latest RC does seem to work, however I didn't actually hit yes to download.
[Captivate Android Development] RichMD:
I haven't tried them yet but I am waiting for the MIUI battery style to finally get merged. Can anyone here explain what is required to get that merged since Diogo rejected it since it is "ideologically wrong"...? If just one administrator approves, does it get merged or would it take two to outvote the one rejection?

---------- Post added at 12:13 PM ---------- Previous post was at 12:06 PM ----------

I just flashed back to stock, formatted both internal, and external to get a completely clean install for #178. Yes, I know this is overkill since wipe data is generally enough. I have wiped data and flashed recent builds a couple of times recently and when I went to use Google Nav it would freeze starting it and the phone would go into constant vibrate even if I killed the app. 3-button reboot would fix it. I was on V13RC both times but I have no idea yet if that had anything to do with it. I will test on the stock kernel (#178) before applying Glitch V13RC but I am curious if anyone has ever heard of an issue like that. The battery would drop like a rock in a short time before I could reboot it.
[Captivate Android Development] sixstringsg:
The MIUI battery mod is in the build I posted that he made. And I've never heard of that, no.
[Captivate Android Development] RichMD:
Thanks. I saw the MIUI battery was in that build. I haven't researched any alternate (Kang?) builds so I prefer to stay on more "mainstream" builds. I don't doubt that it would work but as I customize things I at least want to be starting on a build that many other people are running as well.

I've asked the "governance" question on how items get merged into CM7 if someone rejects it but nobody has ever had an answer. Does anyone know if it is documented anywhere or how it works?
[Captivate Android Development] sixstringsg:
I'm betting it's on a case-by-case basis, and which people care enough to look at it. For example, if cyanogen or Koush vetos something, there is probably little chance of it getting merged. However, if someone less important vetos it, but a few other people decide it's ok, then it will get merged. I think it depends on the reason for the veto, and who does the vetoing. I have no proof of this whatsoever, just a thought since I tend to watch gerrit.
[Captivate Android Development] makelegs:
Think of a Kang as a cm7 compilation that was run at a different time of day and on a machine other than buildbot. By definition it is a cm7 nightly. In this case we have the opportunity to evaluate features that may or may not ever be merged into the official builds.

As far as i can tell, it's not looking awesome for the miui battery to get officially merged. I could be wrong. There seem to be some strong feelings on both sides about it. The adw improvements are nice, though. I expect then to merge.

This process is how new features get tested, approved, and potentially merged...or not.

Edit: I spoke too soon...looks like the adw stuff WILL now be merged \o/

Edit2: Looks like all sorts of crap just got merged!
[Captivate Android Development] J-Wall:
I am on Galnet ICS and I get the same thing when I try to use Google Navigation, it just vibrates so I have to pull battery. The only way to use navigation is to us Maps and choose navigation from there. Did you find any other way to fix it?
[Captivate Android Development] closeshave2:
Same here... For me,

all

of the install/browse buttons cause an immediate force close. It appears to be some kind of null pointer exception:

shortMsg:java.lang.NullPointerException
longMsg:java.lang.NullPointerException
stackTrace:java.lang.NullPointerException
at com.glitch.updater.GKUmain.a(Unknown Source)
at com.glitch.updater.GKUmain.onPreferenceClick(Unknown Source)
at android.preference.Preference.performClick(Preference.java:1004)
at android.preference.PreferenceScreen.onItemClick(PreferenceScreen.java:208)
at android.widget.AdapterView.performItemClick(AdapterView.java:284)
at android.widget.ListView.performItemClick(ListView.java:3535)
at android.widget.AbsListView$PerformClick.run(AbsListView.java:1827)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3703)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
at dalvik.system.NativeStart.main(Native Method)
[Captivate Android Development] sixstringsg:
I don't know how many different ways to say it: I love logs of the app when it is working improperly, but this is not the thread to put it in. It needs to go in the app thread. This is not just me being picky, since it is a paid app, I can't "support" it through any forum other than the paid software section.
[Captivate Android Development] sixstringsg:
Here is our new IRC server:

http://androtransfer.com/IRC.html

Our old IRC host is having some issues.

For those of you with a real client:

irc.freenode.net

Channel: #glitchkernel
[Captivate Android Development] RichMD:
It was Maps V5.12 and I found the same workaround - go into maps and then navigation would work. I restored a backup 5.11 and I don't have any problem. With 5.12, I would try launching Nav and see the startup screen and it would just stay there. I wouldn't get the constant vibration until I hit the back-arrow key and then it would be done until I did a 3-button reboot or shut-down via the extended menu. The phone was still responsive enough to allow me to shutdown via the menu. I figured it was a bug with V5.12 that was triggered by something in my setup. However, it happened on the stock kernel after a COMPLETE wipe/reload. Apparently, the bug is not as uncommon as I thought...
[Captivate Android Development] sixstringsg:
Well, at least it's not a Glitch bug. Just a CM7 bug.
[Captivate Android Development] Smasher816:
Alright guys sorry for the delay and problems.

I figured out a way to force Rom Managers isPremium() to return false, or the normal mode. This will let me test both sides.

I think i found the problem, and an update should be out tomorrow. I'v been busy with school and a few other side projects.
[Captivate Android Development] goob1284:
How do I get this to work with andchat? Or is there an app on the market that I can use?
[Captivate Android Development] sixstringsg:
andchat counts as a "real client" so just put those in. Default port is fine.
[Captivate Android Development] goob1284:
It doesn't work. It says no ident response?
[Captivate Android Development] sixstringsg:
All it is is freenode, it's not anything special, you shouldn't be having any problems. I just checked on androIRC and it worked just fine.
[Captivate Android Development] Smasher816:
http://xdaforums.com/showpost.php?p=19387820&postcount=247
[Captivate Android Development] mrhaley30705:
@six

I finally found a glitch kernel my phone is ok with. Too soon to comment on battery life, but looking good so far. My problem is with charging. I like to charge with the screen awake, but on v12b3 ML if I try, it charges at max clock (1200 on my phone). I've also saw this on the last2 NEO releases. If I turn the screen off, it won't hit max clock, just 100 or deep sleep. Any ideas?

Edit

This happens on Proto's MIUI, and both Galnet versions, GB and ICS.
[Captivate Android Development] jerkysh:
would it be possible to get more governors? like on the gs2 :D
[Captivate Android Development] sixstringsg:
Give me a link to the source, and why you want them, and I would be happy to.
[Captivate Android Development] jerkysh:
http://xdaforums.com/showthread.php?t=1263838

on my sisters phone phone, there are a lot of governors, with this kernel, but i liked smartassv2 because it stays on low freqs when screen off and it saves battery, but it has a "fast wake up" feature that instantly goes from sleep to wake , and it's not laggy, at stock 1.2 ghz with noop sheudler and this governor, i was able to watch full hd videos on youtube, playing tegra games (with chainfire 3d) and other stupid stuff , and no lag at all (compared to the same stats, but with the ondemand governor which gave me a little lag while browsing and with some apps )
[Captivate Android Development] sixstringsg:
We have all the schedulers that kernel has, and we have smartassv2. What governor specifically do you want here?
[Captivate Android Development] goob1284:
So I'm guessing smartass=smartassv2?
[Captivate Android Development] sixstringsg:
No. It's in V13, Smartass in V12B3 is normal smartass.
[Captivate Android Development] jerkysh:
so, i read on this thread http://xdaforums.com/showthread.php?t=1242323 what each governor does

these are the places each governor has,

it would be great to have the smartass2, minmax and the savagedzen :D

but i really really want the smartass2
[Captivate Android Development] sixstringsg:
That thread isn't specific to our kernel. Each kernel interacts differently with different governors, as does each phone, and it changes by how much the dev tweaks each governor. Governor's aren't one-size applies to all.
[Captivate Android Development] jerkysh:
yeah, i know, but it would be great to have some additional governors ;D ,especially the smartassv2 :D
[Captivate Android Development] goob1284:
Ok thank you.
[Captivate Android Development] mrhaley30705:
Any idea about my charging issue? Is it even an issue, or is it normal?
[Captivate Android Development] jerkysh:
ah, yeah, where can i get the V13? :D
[Captivate Android Development] Gromlakh:
https://market.android.com/details?id=com.glitch.updater
[Captivate Android Development] RichMD:
If we are on V13RC, would you suggest SmartassV2 over OnDemand? I googled a bit and it looks like V2 is better tuned to use low power but scale up quickly when necessary so it "appears" to be better than ondemand which is a "universal" linux method used on servers, desktops, etc.
[Captivate Android Development] sixstringsg:
Ondemand for now. It's a lot more heavily tweaked by Tk-Glitch. But as always, test it yourself, see what you like.
[Captivate Android Development] spacecase-25:
How stable is the current v13 rc and the rcs in general?
[Captivate Android Development] RichMD:
Could you point me to the FAQ "3000, 3000, 37000" that you referenced? It's probably obvious but I don't know what thread you are talking about.
[Captivate Android Development] sixstringsg:
The third post on this thread.
[Captivate Android Development] rockosifraldi:
Not requesting for an ETA

I am not trying to start any ETA request fever... so please people... let SixS or glitch answer this..

RC date for the Kernel if I go by the file name is 20111021, approx 3 weeks old. Should I be checking updates to RC build like another release before 13 comes out..or I should consider that the Kernel update app was basically just to get V13RC....
[Captivate Android Development] Raul77:
just got the app from market and on latest RC version, i have the same problem on CM7. it works and then stops and then works again etc. as soon as you touch the screen it works though.
[Captivate Android Development] sixstringsg:
I would give you an answer, but if something comes up and I can't fulfill what I say, I will get ten pages of *****ing because it didn't come out when I said. Therefore, I am not answering your question.
[Captivate Android Development] rockosifraldi:
Understood... Just checking how the minds are thinking!!:)
[Captivate Android Development] sixstringsg:
You will see how the minds are thinking shortly ;)
[Captivate Android Development] rockosifraldi:
I just downloaded RC2. Thx
[Captivate Android Development] simple man:
RC2 is running smooth as silk on #182 Kang build!
[Captivate Android Development] airtower:
BLN is still broken for me on RC2. Using the BLN test in BLN control, the lights come one for about 3 to 5 seconds and then switch off. BLN timeout, blinking, schedule, all disabled.

Wiped data, reinstalled BLN. Still no dice.
[Captivate Android Development] bentonhall:
Same here. Other than that its awesome!! Nice work!
[Captivate Android Development] sixstringsg:
We're aware of BLN. its either people ***** about that, or people ***** about the keys not timing out while screen is on.
[Captivate Android Development] airtower:
Fvcking *****es

it's all good, just wanted to make sure I wasn't alone. FWIW i couldn't care less about KTLO, timeout, whatever. There's 4 softkeys and it took all of 10 seconds to memorize where they were when i got the phone. I dont even notice whether or not they're on anymore.

/rant
[Captivate Android Development] Holmes108:
Not me. I like to ***** when they DO time out while the screen is on. :D
[Captivate Android Development] Raul77:
I promise to only ***** for BLN. :) thanks guys really appreciate the hard work.
[Captivate Android Development] CptTwinkie:
I flashed rc2 and lost my notification tray. Reflashed and no better. I'm going to restore through nandroid and try again. I'm on cm nightly 181

Edit: Restored and reflashed. Seems ok.

Sent from my Captivate w/ CyanogenMOD and Glitch
[Captivate Android Development] airtower:
Same thing here, but I don't know about notifications since I always have my phone on silent if I'm listening to music. Making or answering a call will cause the volume to max out briefly.

Probably related to voodoo, not specifically this kernel
[Captivate Android Development] simple man:
That's a noted peoblemt w/ miui the last couple of updates. Even w/ stock CM7 kernel.
[Captivate Android Development] sixstringsg:
V13 is out! Come and get it from here for now:

http://androtransfer.com/

OP will be updated shortly. A couple of them still have the DEV title, that was a cut/paste error on my part. That is V13 Final right there.
[Captivate Android Development] tkjeeper:
Thanks brother

Sent from the frozen tundra known as Canada
[Captivate Android Development] Gromlakh:
WOOHOO!!!!
[Captivate Android Development] spacecase-25:
When can we be expecting V14? ;)

This should be read as, Thanks!!
[Captivate Android Development] Aus_Azn:
You're asking for a flaming :rolleyes:

Not everyone's reading from mobile or going to highlight your post...
[Captivate Android Development] tkjeeper:
Lmao, now that's funny!

Sent from the frozen tundra known as Canada
[Captivate Android Development] Vaanhoot:
Just flashed version 13. My screen turns bright green and when I touch the screen it goes back to normal. After a short time it turns bright green again. Anyone else get this?

Sent from my SGH-I896 running MIUI.
[Captivate Android Development] Tk-Glitch:
Check your voodoo color settings. Make sure you aren't using "Punchy" settings for gamma.
[Captivate Android Development] Vaanhoot:
Punchy settings are selected. As long as I am using the phone the color is fine. But after not using it for about 30 secs the screen turns bright green. Sucks for watching movies.

Sent from my SGH-I896 running MIUI.
[Captivate Android Development] sixstringsg:
That's your voodoo color settings. Raise the minimum of your auto-brightness, or play with voodoo color.

edit: ninjad

Try raising the minimum brightness through CM7 settings.
[Captivate Android Development] Vaanhoot:
I uninstalled voodoo control app and rebooted and problem still happens. Green turns all green until I touch it or press button.

Sent from my SGH-I896 running MIUI.
[Captivate Android Development] sixstringsg:
Uninstalling doesn't change your minimum brightness.
[Captivate Android Development] Vaanhoot:
I just reflashed miui and glitch v13 and seems to have solved the problem. Thanks for your help.

Sent from my SGH-I896 running MIUI.
[Captivate Android Development] mrhaley30705:
If I flash v13, what is the default leakage, if I don't set one.
[Captivate Android Development] sixstringsg:
High.

10char
[Captivate Android Development] techguy615:
Sweet! Think I just pitched a tent in my shorts. *hits the download button* :p
[Captivate Android Development] Fate-Silver:
Thanks for the V13 Kernel. It's compatible with ICS MIUI!

The BLN still black out in a few seconds for MIUI ROM. CM7 ROM is fine with BLN.
[Captivate Android Development] simple man:
The new v13 kernel splash screen and recovery looks great. Runs smooth, nice work all involved! :-)
[Captivate Android Development] Maranevim:
sod

dunno if its kernel related, bud ive flashed newest cm nighty, then latest glitch and now i get SOD very often. Anybody with similiar behaviour? :)

anyhow, great kernel, thanks for it :)
[Captivate Android Development] galakanokis:
Everything seems great except wifi. I get an error when trying to turn on. Flashes a few different combos of nightlies and the 12 and 13 versions of the Glitch kernel and wifi works on everything but V13. Anybody else having this issue?

G man on a Glitched Nightly
[Captivate Android Development] sixstringsg:
How much are you attempting to UV?
[Captivate Android Development] bentonhall:
Running nightly 181 and Glitch v13 and I don't have that. I had one charge death on 181 before installing glitch but haven't had it since.
[Captivate Android Development] Koizuma:
So far running Low leakage V13 with my usual -175/-200mV and its extremely smooth, running with MIUI 1.11.18
[Captivate Android Development] Aus_Azn:
Six,

You mentioned that there was a bug in V12 and early V13RC undervolting that you said was fixed, right?

So, am I just lucky or what? Seems more stable than these numbers produced on V12; been running it since V13 dropped, and I have yet to have a random shutdown, FC or freeze in normal use.

LL

800MHz - Ondemand

1300MHz - Performance (Charging)

200MHz - SmartassV2 (Screen Off)

1300MHz - -175mV

1200MHz - -175mV

1000MHz - -175mV

800MHz - -200mV

400MHz - -225mV

200MHz - -250mV

100MHz - -300mV

By the by, is Ondemand still the recommended governor for general use? I see that V13 got a couple more.
[Captivate Android Development] 105437:
Phone gets stuck at Glitch/Galaxy S boot screen. Is there a way to boot into recovery so I can flash CM7? Thanks
[Captivate Android Development] sixstringsg:
Three button recovery still works the same way...
[Captivate Android Development] iluretar:
im getting a black( sometimes gray) background color where the launcher dockbar is, tried adw, go and launcher pro and they all have it.
[Captivate Android Development] sixstringsg:
I don't understand how a launcher issue can be a kernel issue....
[Captivate Android Development] iluretar:
neither do i but i wasn't getting it with 12b3 and if it were a launcher issue i guess it wouldn't happen in 3 different launchers, and the black spot is there on the lockscreen too, both stock and widgetlocker.
[Captivate Android Development] RCDuke:
Have you reflashed V12B3 and seen if the issue goes away? Or reflashing the stock CM7 (or MIUI) kernel? If the issue goes away with that, then it MAY be a kernel issue, but doubtful.
[Captivate Android Development] 105437:
I pulled battery and then put it back in. Held down Vol Up/Vol Down/Power until I saw the AT&T boot screen and released and then it just went to the Glitch logo and hung. Next I tried hold the 3 buttons down and it went past the AT&T and then stuck again at the Glitch logo.

What am I doing wrong?
[Captivate Android Development] sixstringsg:
What ROM were you on before you flashed the kernel?
[Captivate Android Development] iluretar:
reflashed v13 and the spot was still there, then flashed v12b3 and it was gone, then flashed v13 again and it was gone, that was just weird.
[Captivate Android Development] 105437:
I ODIN flashed to stock before flashing CM7.
[Captivate Android Development] sixstringsg:
So you flashed CM7, let it boot, then flashed this kernel?
[Captivate Android Development] 105437:
Yes, I did both a good while ago. Since then I've been installing CM7 nightlies and purchased your Glitch updater on the Market and began used it to flash RC2 yesterday.
[Captivate Android Development] galakanokis:
Yeah, I am the same, 181 on V13. I just went back to 12 and wifi is fine. Weird.

G man on a Glitched Nightly
[Captivate Android Development] sixstringsg:
Then I have no idea, you're the only one that's run into issues. Looks like you wiped out your three-button fix with your odin one-click, download mode is your next option.
[Captivate Android Development] 105437:
Thanks for your help, I don't think I'm familiar with download mode. I guess I'll just ODIN to stock again.
[Captivate Android Development] Captivate2010:
Glitch Kernel app

The V13 works fine

thanks
[Captivate Android Development] Snow.Goose:
BLN isn't working out for me. When I get a notification, it turns on, but times out a few second after... In bln control, I didn't set it to time out
[Captivate Android Development] mcala:
No issues so far, V13 running great. I had an initial boot loop but 3 buttoned back to cwm & reflashed V13.

Sorry, I have 1 eyesore. When phone boots I see the old glitch screen for 1/3s then I see the new animation. I had came from the RC. Tomorrow I will flash the new nightly & try again.
[Captivate Android Development] aobmax:
Can't boot & can't get into recovery

Same here, flashed v13 this morning and tonight just now it won't boot and i can't get into recovery to make any changes either.

Edit: Download mode works fine though. Might just change use Odin for now since I have to use it tomorrow. The v13 was performing great, keep up the good work.
[Captivate Android Development] metalfangs:
V13 running very smooth here on MIUI 1.11.18. However I did notice the screen goes yellow just before timing out.
[Captivate Android Development] flxdms:
I flashed V13 and lost a couple of contacts as well as all my text messages. Some of my applications also started crashing randomly. Widgetlocker went ape**** as well as my launcher and most of my applications. It worked fine until I rebooted. Hm... I flashed a newer KANG build of CM7, but it still acts weird.

Edit: I managed to get rid of some of the annoying crash issues by manually wiping most of the app's data. Everything works fine-ish. Except for the contacts I've lost, unless that was supposed to actually happen.
[Captivate Android Development] Snow.Goose:
flashed a newer

cm7 nightly, but it's the same thing. Bln times out after a few second. Anybody else experiencing this issue?

Edit: just got an email on gmail.... Bln works normally.... It doesn't work for other notifications though, including the test in

bln control..... Weird....
[Captivate Android Development] techguy615:
I have been getting the same issue. Not Kernel related. I have had it on Go Launcher EX for over a week now on the nightly builds and I am also on one of the Kangs right now with the same problem. This started before v13 was released. I was on the new Platypus Neo when it started.

So far looks great guys. Love the new splash screen. Performance is great so far as well. Will have to see what happens in the next days as I has some burn in time on my device. But it rocks so far!