[KERNEL] 2.6.38.8-incredikernel-12/08/2011

[watt9493]

Fastcharge toggle widget now available in the market!

https://play.google.com/store/apps/details?id=com.incredicontrol.fastchargewidget

As soon as i.dont have an incredible in use anymore.

Sent from my DROIDX using Tapatalk

 

[chad0989]

As soon as i.dont have an incredible in use anymore.

Sent from my DROIDX using Tapatalk

Could always bring fastcharge over to the other devices. If they don't have it yet.

Edit: Looks like the shift uses the same chip to control charging as the rezound. Would take about 5 minutes to do.

 

[watt9493]

Could always bring fastcharge over to the other devices. If they don't have it yet.

Edit: Looks like the shift uses the same chip to control charging as the rezound. Would take about 5 minutes to do.

Ooooo. My girlfriend would love that! If you could do it for the DROID x id be so grateful. But there's no custom kernels possible on this. :/

Sent from my DROIDX using Tapatalk

 

[tiny4579]

As soon as i.dont have an incredible in use anymore.

Sent from my DROIDX using Tapatalk

I thought you were getting your Incredible screen replaced....

 

[watt9493]

I thought you were getting your Incredible screen replaced....

Once it comes in.

Sent from my DROIDX using Tapatalk

 

[drk.hd]

Fastcharge toggle widget now available in the market!

https://play.google.com/store/apps/details?id=com.incredicontrol.fastchargewidget

I'm getting an App Not Compatible on my Pons CM7.2 kang running Tiny's latest build.


Sent using xda premium

 

[tiny4579]

I'm getting an App Not Compatible on my Pons CM7.2 kang running Tiny's latest build.
View attachment 947910

Sent using xda premium

sounds like a problem with the build.prop have to see what it should be...

Chad can you test on the latest nightly for the Inc? I will test today possibly but not sure when. I don't think kernel detection even exists for app compatibility. Could be wrong though.

Sent from my Galaxy Nexus using Tapatalk

 

[chad0989]

sounds like a problem with the build.prop have to see what it should be...

Chad can you test on the latest nightly for the Inc? I will test today possibly but not sure when. I don't think kernel detection even exists for app compatibility. Could be wrong though.

Sent from my Galaxy Nexus using Tapatalk

Downloading now. Can you see if you can search for it on your nexus too? A couple guys reported the same error for the gnex.

I'm guessing its a market bug though, as like you said, there is no kernel detection for app compatibility. Hopefully it'll work itself out soon. The only compatibility parameters are:

Screen layouts: SMALL NORMAL LARGE XLARGE
Required device features: android.hardware.touchscreen

Edit: Market says incompatible with the latest nightly here too. Hmm. Incredicontrol has the same compat parameters and it comes up though. ::shrugs:: hopefully its just a market thing and it'll straighten itself out in the next day or so.

 

[chad0989]

Market started working correctly now. Hopefully it straightened out for everybody.

 

[drk.hd]

Market started working correctly now. Hopefully it straightened out for everybody.

It's working now for me. Thanks.

Sent using xda premium

 

[Pons]

It's working now for me. Thanks.

Sent using xda premium

So, nothing wrong with the build.prop, Google Play was just misbehaving?

 

[chad0989]

So, nothing wrong with the build.prop, Google Play was just misbehaving?

Yeah. Not sure what its deal was. Haha.

 

[chad0989]

To whoever left the nasty comment in the market about the widget not being there:

1) Yes it is, its called fastcharge widget. Unless you're running some alternative launcher that doesn't support normal android widgets, its there.
2) You have to contact me if you actually want a response. The market is not a place for troubleshooting. There is no way to respond to comments in the market.
3) Don't use my apps or my kernel if you think that trying to discourage others from using my stuff is going to make me want to continue to develop and give away 95% of my stuff at no charge.

 

[SynisterWolf]

To whoever left the nasty comment in the market about the widget not being there:

1) Yes it is, its called fastcharge widget. Unless you're running some alternative launcher that doesn't support normal android widgets, its there.
2) You have to contact me if you actually want a response. The market is not a place for troubleshooting. There is no way to respond to comments in the market.
3) Don't use my apps or my kernel if you think that trying to discourage others from using my stuff is going to make me want to continue to develop and give away 95% of my stuff at no charge.

Haters gonna hate. :/

Sent from my sexy assistant. (AMOLED HTC Incredible)

 

[chad0989]

Haters gonna hate. :/

Sent from my sexy assistant. (AMOLED HTC Incredible)

Pretty much. The one thing I really dislike about the market is there is no way to respond to the comments to elicit more information. It makes it impossible to resolve issues / get logs.

 

[HoochieCoo]

Pretty much. The one thing I really dislike about the market is there is no way to respond to the comments to elicit more information. It makes it impossible to resolve issues / get logs.

Or even clarify when someone is being an idiot.

 

[drk.hd]

Chad, tiny, did you see this?

Qualcomm released official Adreno 2xx drivers for ICS!

This means we should be able to get non-hacky HWA, right?

 

[tiny4579]

Chad, tiny, did you see this?

Qualcomm released official Adreno 2xx drivers for ICS!

This means we should be able to get non-hacky HWA, right?

Awesome... they seem to be userspace binaries which would be in the rom. This is amazing news for the Inc. Too bad I can't test right now. Post this on the current ics rom threads.

Sent from my Galaxy Nexus using Tapatalk

 

[chad0989]

Chad, tiny, did you see this?

Qualcomm released official Adreno 2xx drivers for ICS!

This means we should be able to get non-hacky HWA, right?

I believe it should. That's awesome.

 

[WildZontar]

I'm running CM7/Android 2.3.7 with the 8/15/2011 kernel. Am I likely to see a speed or battery improvement with the latest AOSP kernel? Are there significant changes from the 8/15/2011 release?