Post Reply

[KERNEL][UV][CWM] Entropy's Daily Driver-GB, 03/07/2012 (Small Fixes))

OP Entropy512

29th February 2012, 02:37 AM   |  #2001  
Member
Thanks Meter: 2
 
34 posts
Join Date:Joined: Sep 2010
Is there a way to change the recovery to the touch version? tired flashing it in the cwm that came with this kernel but it dosnt change anything. im guessing the .img file would need to b decompliled?
Red5
29th February 2012, 03:09 AM   |  #2002  
Guest
Thanks Meter: 0
 
n/a posts
Yup, both 2/18's ran fine (although not at great as 2/15-C) then jumped over to 2/26 and my phone felt like it was only operating at 400MHz and only had 128MB of RAM total installed (slow, laggy, choppy in apps, games and in the app drawer... power button took 3-5 seconds to turn on and wake up). Just flashed back to 2/15-C and my phone is running awesomely smooth again.

Whatever it is, my phone just flat out does not like the 2/26 version.
29th February 2012, 03:25 AM   |  #2003  
Senior Member
Thanks Meter: 57
 
330 posts
Join Date:Joined: Sep 2011
Quote:
Originally Posted by Red5

Yup, both 2/18's ran fine (although not at great as 2/15-C) then jumped over to 2/26 and my phone felt like it was only operating at 400MHz and only had 128MB of RAM total installed (slow, laggy, choppy in apps, games and in the app drawer... power button took 3-5 seconds to turn on and wake up). Just flashed back to 2/15-C and my phone is running awesomely smooth again.

Whatever it is, my phone just flat out does not like the 2/26 version.

I find it so weird that you have such big problems with it when I haven't had any symptom remotely like yours. I know to a certain extent all our phones are their own monster but still... way weird to me


Sent from my SGH-I777 using XDA App
29th February 2012, 03:31 AM   |  #2004  
ryude's Avatar
Senior Member
Flag USA
Thanks Meter: 643
 
2,589 posts
Join Date:Joined: Jun 2010
Donate to Me
More
I had no issues with 2/26, perhaps just a corrupted download or a bad flash.
29th February 2012, 03:34 AM   |  #2005  
Senior Member
Thanks Meter: 59
 
376 posts
Join Date:Joined: Nov 2011
More
Entropy,

I just got back from a cruise, I've read for the last hour still have some catching up to do, lots going on. As far as the Ashmem issue I'f its affecting other users negatively, take it out or whatever you'd like to do. I just put 2/15 on and will work my way up. Before I left I did a full wipe and put back on 1/30 with uckh7, had no issues at all while away.
Thanks for all your hardwork, I'll be sure.to document if I have any issues.

Sent from my SAMSUNG-SGH-I777
29th February 2012, 03:42 AM   |  #2006  
Senior Member
Des Moines
Thanks Meter: 47
 
421 posts
Join Date:Joined: Mar 2011
More
Im with red5 on this. No major issues with 2-20 but 2-15c runs smoother. Even with my 2d only games were noticeably laggy. Will run with 2-15c for a few days to compare
29th February 2012, 03:53 AM   |  #2007  
Senior Member
Long Beach, CA
Thanks Meter: 22
 
198 posts
Join Date:Joined: Feb 2012
More
I guess I'm one of the lucky ones, I haven't had any issues with any of entropy's kernels.
29th February 2012, 04:00 AM   |  #2008  
OP Senior Recognized Developer
Flag Owego, NY
Thanks Meter: 24,467
 
13,347 posts
Join Date:Joined: Aug 2007
Donate to Me
More
Quote:
Originally Posted by rav4kar

Entropy,
We can add even XWKL1 base to bug list; in idle state, XWKL1 base drains 10%/ hour on my work wifi with AOS topping >67% with lots of wlan_rx wake locks.

Well, to confirm it's the base - please perform the diagnostics (skip right to Shark captures) in the known battery drainers thread.

I saw BT-AMP happen once on XWKL1, but it was when I was janking around with some experimental settings in the wifi driver and never again.

I'm 90% certain I ran the arpdrain test against KL1 and it was immune. Will try again later this week.

Quote:
Originally Posted by shinji257

I believe it was 2/18b (confirm definitely 2/18b) since the kernel was actually dated 2/18. It was charging via PC USB rather than the standalone adapter. I had skipped 2/15c coming from build 1/30/12.

Sent from my SAMSUNG-SGH-I777 using xda premium

Hmm, if charging via PC USB, and it happens again, try to ADB in and pull /proc/last_kmsg

On other topics:
I'm going to revert that ashmem patch. I have no idea why red5 is having performance issues with it, but since it's clear that things go badly when switching between 18B and 26 that there is a delta, I'm going to go with it.

For the patches in 18A and B - I need more info because too many people skipped A.

I'll be uploading shortly.

It also contains a bunch of small recovery fixes INCLUDING swapping internal/external SD to be consistent with Android standards (and with CWM labeling)

Touch recovery is not planned at this time - It is too prone to user error.
Last edited by Entropy512; 29th February 2012 at 04:13 AM.
The Following User Says Thank You to Entropy512 For This Useful Post: [ View ]
29th February 2012, 04:50 AM   |  #2009  
shoman94's Avatar
Recognized Contributor
Flag Maine
Thanks Meter: 12,219
 
8,448 posts
Join Date:Joined: Mar 2009
Donate to Me
More
Quote:
Originally Posted by Entropy512


Touch recovery is not planned at this time - It is too prone to user error.

That sucks. Maybe red pill then?



Sent from my Transformer Prime TF201 using Tapatalk
29th February 2012, 04:55 AM   |  #2010  
OP Senior Recognized Developer
Flag Owego, NY
Thanks Meter: 24,467
 
13,347 posts
Join Date:Joined: Aug 2007
Donate to Me
More
Quote:
Originally Posted by shoman94

That sucks. Maybe red pill then?



Sent from my Transformer Prime TF201 using Tapatalk

I'll look into it - I think the main improvement there was removing a bunch of the "nos" in the confirmation screen, which does make sense - there are a few too many...

The Following User Says Thank You to Entropy512 For This Useful Post: [ View ]
Post Reply Subscribe to Thread

Tags
cwm, kernel
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in AT&T Samsung Galaxy S II Android Development by ThreadRank