yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] jcurley:
Not to hijack the thread, but, I am actually loving Maxthon right now. it is REALLY fast.
[Fascinate Android Development] s44:
I'm sure it doesn't help, but imoseyon's kernel seems to do well with memory. BLN still doesn't work, which sucks, and I'm stuck at 800 max because there's no 1000 step, but I can leave open Dolphin, Pulse, Tapatalk, a game, etc. and not have the thing grind to a halt when I try to take a phone call (open the dialer) or wake from sleep.

Still looking forward to your next build. ;)
[Fascinate Android Development] 92GreenGT:
Kind of a hijack but why does my stock browser have issues with flash player? It's installed but it thinks it isn't installed(if that makes sense).
[Fascinate Android Development] kwinders:
Look under settings in your browser for plug-in option, probably set to off. Change to always ruin or ask to run, maybe that's it, I had the same thing happen after one of the updates.
[Fascinate Android Development] shag_on_e:
/

http://www.androidpolice.com/2011/1...sends-url-of-every-page-you-visit-to-a-remote

~~~~There is no spoon~~~~
[Fascinate Android Development] s44:
Your mistake is even worse than I thought, then... You didn't just hear it wrong, you failed to actually read your own source!
[Fascinate Android Development] Dj-Dubster_TN:
Ya i know its for desktop to and its also super fast,it just never caught on in america,its huge in china and europe tho
[Fascinate Android Development] shag_on_e:
I read it, I know it's been fixed, I q&a only saying that I read that Dolphin was sending urls to a remote location...that's it.

Not a big deal.

~~~~There is no spoon~~~~
[Fascinate Android Development] the entity:
Skyfire does the same.
[Fascinate Android Development] 92GreenGT:
Will check, thanks.

After getting the increase in call volume, I love this kernel....minus the screen capture, that's annoying.:D Everything else is perfect though!!!!
[Fascinate Android Development] s44:
Heh, now I'm getting hot boots and lockups on wake with his lean kernel. Guess I'll switch back as soon as another dev build drops.
[Fascinate Android Development] jcurley:
I am having one problem w/11/06 kernel.

Video recording jams up after recording a video. I can exit, but I have to hit home and go back into camera.

But after video recording a couple times, it started working again. This did not happen on previous builds.

I have not tested it to see if this happens after each restart or not.

Anyone else seeing this issue?

Pwgb

Tks 11/06

Vm heap 48

AKMO optimum
[Fascinate Android Development] Merman1983:
Not seeing that issue with 1106 but I am running Resurrection 1.2.

What I have found since switching from imoseyan lean 1.52 is that my soft key lights never go out. Is this known? Is there a fix?

SCH-I500 Tap, Tap, Taparoo!

* @ wessiide wow, well that's a damn shame. Haven't had this since Eclair iirc. Well - not enough reason to switch out for the moment, but it makes reading at night terribly terrible.
[Fascinate Android Development] wessiide:
Unfortunately long as your on this wonderful kernel you will have blinding backlights. Nobody is exactly sure where it is located in the code or whether its kernel or rom dependent but hopefully we will one day have the option like aosp roms do now to tailor to user preference.
[Fascinate Android Development] the entity:
So I was having ready bad lag issues due to the memory management of the 11/16 build. I set akmo to aggressive, but either the rom or kernal seemed to ignore the settings altogether.

I switched back to the stable build and things seem to be going ok so far.
[Fascinate Android Development] comradesven:
It is both, as in it's "supposed" to be ROM dependent and it's also in the touchkey driver code as what was an unintended side effect of BLN in its earlier implementations.

I am aware of the existence of adjustable touchkey backlight timeout in the AOSP ROMs. It is a hack to a specific, older version of the touchkey driver and does not directly translate to my kernel. Getting BLN was a bit of a chore to begin with on this kernel due to Samsung's changes and as soon as I ported a driver and made some changes to the platform definition files that sorta worked I was loath to do anything more with it because there were many attempts that didn't work properly before that. But I'll put it on the list along with the other things.

I'm about to release another devbuild which has a few more improvements in it under the hood regarding memory management and such, if my testing in the next few hours works out, or whenever it's ready if not.
[Fascinate Android Development] comradesven:
OK, let's give this a try.

Changelog: Drivers/kernel settings from EI20, removed carrier hotspot tracking code in init.rc (doesn't make hotspot tracker directories in /system), ARM and memory and RCU updates/tweaks, changes in ramdisk, update to Linux 2.6.35.9actually how about 2.6.35.7 for now.

Seems stable enough and fast enough, seeing as how the random hot reboots on TSMR are pretty much not my fault.

If you're using autokiller/supercharger/adrenalineshot/whatever they may interfere.

Beta and first post rewrite and/or new thread this weekend depending on how it likes people's phones.

http://www.mediafire.com/?u9vwu7b8xq7pjo3

If you want to use the built-in Verizon "Mobile AP" to tether, this may no longer be possible because of the removal of the hotspot event monitoring code in init.rc. Even if it is, your phone ID while tethering the official way != your phone ID accessing 3G. Resourceful people can change the tethering ID to the 3G ID with QPST, a Qualcomm diagnostic software product, which is illegally obtainable here and there.

I have not done this. I cannot and do not want to help you. Therefore,

DO NOT ASK ME FOR DIRECTIONS FOR THIS.

Do whatever you do on your own time. Once again this is a thing about which I personally give no ****s whatsoever because of the existence of Wireless Tether for Android.
[Fascinate Android Development] laureanop:
@comradesven. You really bumped up those first three ram limit values. I just installed, froze AKMO and will run it today and will report back tonight

tsm res1.2, TKSGB 11-06, lag fix
[Fascinate Android Development] comradesven:
Yes, the lowmemkiller values are one of several things that makes this build more usable. It wasn't as simple as "doing what imoseyon does in his kernel" because he kept things on that front at stock. Adding in autogroups and such meant those things got broken and I went through the relevant scheduler code with a fine-toothed comb and added in a few more things before lag went down to a more manageable level as in this build.
[Fascinate Android Development] s44:
Thanks! Had more hot boots and lockups on imo's kernel (still using PWGB), so I've been itching to flash back.

Now that wifi tether does infrastructure on our devices, there's no point in messing with the built-in Verizon tether app.
[Fascinate Android Development] jcurley:
Just flashed this. Seems extremely smooth. I will let you know with more testing, but looks like the best one yet.
[Fascinate Android Development] the entity:
Sure there is a reason to use the built in tethering.... Tasker integration.
[Fascinate Android Development] comradesven:
It appears that the EI20 dpram driver isn't playing nice during long uploads with low signal. Symptoms include the phone hitting back by itself a lot, touchkey backlights going out, dmesg output from the touchkey driver complaining of unknown key codes, and hard reboots. I'll throw up a build reverting to the EH09 dpram driver later tonight.

I've complained about the dpram driver earlier in this thread. Why the cell phone signal should affect the touchkeys never made intuitive sense to me. There is some prior work in getting the dpram timings right on the part of SirGatez back in the Eclair/Froyo days and I suppose I'll have to take a look at that again; the results of that tinkering didn't really work out last time I tried it on this kernel. Ah well.
[Fascinate Android Development] AtropineNa:
which tether version are you using?
[Fascinate Android Development] comradesven:
The latest from the WiFi Tether for Android download page at http://code.google.com/p/android-wifi-tether/downloads/list should work.

By the way, has anyone tried replacing the Broadcom BCM4329 firmware? You can obtain it from mirrors of the bcm4329 driver in the Android source, such as the one at http://www.igloocommunity.org/gitwe...om/wlan.git;a=tree;f=bcm4329/firmware;hb=HEAD

fw_bcm4329_apsta.bin from the Android repo is version 4.218.248.18. Our firmware files are at /system/etc/wifi and they're split up differently. There's a bcm4329_sta.bin which the phone uses when it's just being a regular client, and a bcm4329_aps.bin which is used when tethering. I'm not sure what the mfg one is for. The STA firmware we have is 4.218.248.183 (newer than what I've found online) but the APS firmware is 4.218.214.3 which is pretty old.

So you would take fw_bcm4329_apsta.bin from the Android repo, which as its filename indicates can be both an APS and STA firmware, rename it to bcm4329_aps.bin, and replace the file that's already there in /system/etc/wifi (making a backup, of course).

I didn't do any testing except verifying that wireless tethering starts with the newer firmware. The kernel log I saw indicated that it was loading properly but I never connected to the phone with a different computer to test it. It might be fun to try it out and see if it works for real.
[Fascinate Android Development] laureanop:
That is good news. Hopefully bln will not bring instability to what is otherwise the best kernel I've used on this phone.

sent from my SCH-I500 PWGB 2. 0b3 TKSGB 9-27, shot v7
[Fascinate Android Development] comradesven:
Your question prompted me to write some info on the subject of undervolts in general in that post I reserved on page 1. A good starting point would be -50mV across the board from 100-1000MHz. Although, as I explain in Post 2 of this thread, that would be more like -75mV on this kernel.

Actually finding the lowest settings is a long process. I'm personally happy enough with blindly setting -75mV for 100-400MHz and -50mV for 800-1000MHz and the real limits aren't far enough off for me to care. Those are pretty safe settings in my experience.
[Fascinate Android Development] tulalhyt:
last night I try this kernel with pwgb v 2 b 3 ...

I think this kernel is great, the voodoo all working, the batery is also great

just found a little problem this night

when using this kernel while listen music (i'm using headphone), after from screen off arround more than 1 minutes and longer want to wake (push the power button), the phone is very2 lag

the application for playing music is :

1. pwgb v2 b3 internal player (so worst, I almost can't move the lock screen pusle)

2. power amp (better than internal player, but still lag)

combination i've done

using pimp my cpu

- changing all the governor

- changing all the I/O schedulers

- turn on n off Force minimal freq when sleeping

- 100 > 1000 -0 v (default)

- 100 > 1000 : -25 -50 -75 - 100 (test one by one)
[Fascinate Android Development] droidstyle:
these are my current settings

1400mhz=-25uv

1300-1000mhz=-50uv

800-200mhz=-75uv

Getting 3330 bechmark on untutu

Everything is working great, love your kernal and thanks again for your work!
[Fascinate Android Development] laureanop:
First, try turning off the 100 step. There's no point in using it cause it draws the same voltage as 200. Second, switch to on demand or interactive governor which ramp up the CPU speed way faster.

sent from my SCH-I500 PWGB 2. 0b3 TKSGB 9-27, shot v7
[Fascinate Android Development] Bawb3:
It's really amazing how much snappier this kernel made pwgb.

It really feels like an aosp, instead of tw now.

I was thinking about going back to cm7/miui until I tried this, love it.
[Fascinate Android Development] laureanop:
@comradesven is it accurate to say that the issue of phones not being able to handle Uv is mainly because of Uv at the highest CPU speeds? My phone was never able to handle Pbj -100 on ed 05, but now my voltages are as follows:

1200 -25

1000 -50

800. -75

400. -100

200. -125

And I'm having no issues whatsoever

sent from my SCH-I500 PWGB 2. 0b3 TKSGB 9-27, shot v7
[Fascinate Android Development] jcurley:
1200-50

1000-50

800-75

400-100

200-100

100-100

Deadline

Conservative

Very snappy. I found on demand used more processor when running Pandora (which I use a lot) than conservative.

But perfectly stable and compared to wife's stock EH09 and is a lot faster.

Might remove the 100MHZ, but it is stable now, so if it aint broke.....
[Fascinate Android Development] tulalhyt:
may be it's a weird hehehe

I restore my pwgb (I backup last time before applying this kernel), and re applying this kernel again, installing pimp, reduce 100 and 200 -100

and -50 up to 1000 (not overclockin)

and now normal ... (using power amp)

...............................

by the way are u all still having a google map problem ? my google map still freezing the touch screen after a few second (after playing the zoom, rolling, twist etc on screen)

I think this is google map problem not the kernel or the rom (maybe)
[Fascinate Android Development] laureanop:
Yes, still having the Google maps problem, even after flashing the permissions zip. I'm pretty sure it's a Rom issue though. Maps updated a couple of days ago and the bug persists

sent from my SCH-I500 PWGB 2. 0b3 TKSGB 9-27, shot v7
[Fascinate Android Development] laureanop:
What CPU speed does Pandora stream at? My music streaming apps do it at 200 screen off or on

sent from my SCH-I500 PWGB 2. 0b3 TKSGB 9-27, shot v7
[Fascinate Android Development] briguyy:
+1 I was still having the freezing as well with maps and at the puzzle lock screen sometimes too and this is with no overclocking or undervolting so i just flashed back to stock eh09 kernel and all freezing is gone.
[Fascinate Android Development] SmokeyDP:
EDIT: wrong thread
[Fascinate Android Development] laureanop:
When you start playing around in Google maps, specially in satellite view, the map and phone will freeze until you press the power button, then it un freezes right up

SCH-I500 PWGB 2. 0b3 TKSGB 9-27, shot v7, honeycomb v 2
[Fascinate Android Development] SmokeyDP:
You beat my edit.

That sounds workable then.
[Fascinate Android Development] laureanop:
Any questions pertinent to the Rom and the kernel it's running imo should never be considered "wrong thread "

SCH-I500 PWGB 2. 0b3 TKSGB 9-27, shot v7, honeycomb v 2
[Fascinate Android Development] jcurley:
My Pandora was running 800-1200 when ruining on demand for done reason, but running 200 on conservative.
[Fascinate Android Development] laureanop:
Good enough reason to set it down to conservative if you use it a lot

SCH-I500 PWGB 2. 0b3 TKSGB 9-27, shot v8.5, honeycomb v 2
[Fascinate Android Development] jcurley:
Just started getting freezes on deadline, weren't back to noop to see if there is any difference. I know my fassy can get finicky with oc and uv.
[Fascinate Android Development] laureanop:
Very rarely is the scheduler the cause of freezes

SCH-I500 PWGB 2. 0b3 TKSGB 9-27, shot v8.5, honeycomb v 2
[Fascinate Android Development] comradesven:
Umm are you guys getting the correct file? I guess I'd better change the link on the front page. Once again it's http://www.mediafire.com/?u9vwu7b8xq7pjo3 built on 11/14.
[Fascinate Android Development] comradesven:
Here is that build with the dpram driver from EH09 stock. Otherwise nothing's changed.

http://www.mediafire.com/?mg78n9a77sje6e4
[Fascinate Android Development] laureanop:
@comradesven 11-14 dev was pretty good to me. Ram management was fine with no lock ups. Set the zram to 64 (18. 5% of available memory). The re boots issues are definitely not because of the kernel. I'm on my third day back to tsm 1. 2 and I have no re boot issues whatsoever. In my case they start happening after one week of use regardless of kernel.

tsm res1.2, TKSGB 11-14, lag fix
[Fascinate Android Development] sendan:
11/16 runs great so far. Although I just have a question, Is there any way to disable the 1000Mhz step? Disabling it in voltage control doesn't seem to work.

If that isn't possible, are any of the other steps able to be disabled? (with an OC of 1200 Mhz)

I just feel it would be smoother if I could get the 1000Mhz step out when I want it at 1200Mhz...seems unnecessary.

Thanks
[Fascinate Android Development] HuskerDad3:
I have been using imoesyon's kernel for the past two weeks and have been having random lockups and mediocre battery life. I have also had issues with widgets disappearing after every reboot. I was getting to the point where I wanted to throw my phone against the wall.

I decided to come back to TKSGB since you rewrote the code and I installed the 11-14 version last night and haven't had any lockups and my battery is at 44% after 10.5 hours, with a phone call, a few texts, twitter and facebook use and several downloads. I'll report back in a few days, but so far awesome job. Many thanks for the kernel and saving me from destroying my phone. :p
[Fascinate Android Development] sendan:
I'm going to go ahead and assume clearing both your caches fixed your problems, as I just came from imsoyen's kernel and it was fantastic. Although, no arguements here on this kernel, it's very good.
[Fascinate Android Development] jcurley:
I am on 11/14 and everything is working perfectly. I have not had an issue with the signal drop. 11/14 is FLYING! This is the best my Fassy has ever worked. I did not want to go to 11/16 since 11/14 is working so well.

I am feeling, if it ain't broke....

EDIT: Went to 11/16, just in case. Noticed VZW would not let me *228. Figured I would try that with 11/16 and see if that works.

EDIT II: worked!
[Fascinate Android Development] laureanop:
@comradesven djp 952 appears to have successfully implemented the trickle battery charge feature. Any way that you can kang this and put it in your kernel?

tsm res1.2, TKSGB 11-14, lag fix
[Fascinate Android Development] HuskerDad3:
Actually, I'm not sure if that was it, because I had gone back and forth between 1.4.1 and 1.5.2 clearing data and dalvik cache and had the same problem.
[Fascinate Android Development] s44:
I'm still on the EI20 one because it doesn't skip my music every time it reacquires 3g signal (coming out of the subway tunnel)...

Anyway, the behavior has been flawless so far. No memory choking -- yet, knock on wood. Sio and smartass, no undervolting yet.
[Fascinate Android Development] AtropineNa:
hows 11/16 compared to 10/21? looking for something simplistic stable and uv capabilities
[Fascinate Android Development] jimv2000:
Wireless tether with the newer Broadcom driver worked pretty well for me today. The only odd issue was that my phone suddenly rebooted once when I was setting up the tethering, but it was fine for the entire hour or so that I had it tethered after that.

EDIT

Also, I haven't done wireless tethering before on the laptop I was using, so no pre-setup connections or anything like that.
[Fascinate Android Development] jcurley:
I feel 11/16 is his best yet! Very fast, very stable and no low memory lag AT ALL! The only thing I think left is the Trickle charge hack. Then this kernel will be perfect!
[Fascinate Android Development] s44:
That and a not-always-on liblights = ideal kernel.

edit - here is djp's commit for the charge fix
[Fascinate Android Development] laureanop:
+1 for the 95% version

tsm res1.2, TKSGB 11-14, lag fix
[Fascinate Android Development] laureanop:
@comradesven after three days on 1114 dev I'm happy to report that there's no ram related lock ups or slow downs. Running zram at 64mb .

Did you get a chance to look at djp' s battery charge trickle fix?

tsm res1.2, TKSGB 11-14, lag fix
[Fascinate Android Development] kleffman:
you guys getting any reboots on 11/14?
[Fascinate Android Development] s44:
None. Very happy so far.
[Fascinate Android Development] jcurley:
Only reboot I got was after adding too many active widgets to the home screen. Nothing since removing those.

Pwgb

Tks 11/16

Vm heap 48
[Fascinate Android Development] comradesven:
Sure, OK, why not. I wanted to do some more testing because I had some weird behavior with the battery indicator on the lockscreen with djp952's patch but I guess since you guys are calling for it here you go.

From 11/16, battery trickle charge patch added. RFS/STL drivers from EH03, except the OneDRAM (dpram) which is still from EH09. No other changes.

http://www.mediafire.com/?xedn7l9m8l9eucn

Since this is an experimental patch I'm not putting this in the main tree until some other people who actually have battery drop problems find that it works.
[Fascinate Android Development] jimv2000:
Excuse my ignorance, but what are the RFS and STL drivers?
[Fascinate Android Development] jcurley:
Only one issue with the trickle charge, it keeps giving me the plug/unplug sound while trickling. Did this all night. Drive me insane.

Other than removing the sound, can you fix this comrade?

SC

Tks 11/17

Vm heap 48
[Fascinate Android Development] skiddingus:
Is there a place where I can find the stock kernel in a flashable zip? I would like to be able to flash back if needed.

Thanks.
[Fascinate Android Development] HuskerDad3:
I installed the 1117 patch last night and the phone didn't charge higher than 95%. It did stay at 95 though instead of dropping like it used to. May have to recalibrate the battery.

I'll report back later.

Edit 11/21 - Wiped batt stats and charged while off, now I can get it to 97-98% after charging. I wonder if it might take a few cycles of calibrating to fix.
[Fascinate Android Development] laureanop:
@@comradesven. The trickle charge fix worked. Thank you
[Fascinate Android Development] wessiide:
I don't understand the deal with trickle charge I leave my phone charging all night then in the morning pull it off its 100%... been this way since early versions of this kernel
[Fascinate Android Development] laureanop:
I don't think it happens to everybody and not all the time either.
[Fascinate Android Development] jcurley:
I am having the same issue. I cannot get higher than 95, even when I bump charged it. trying to calibrate the battery now.

SC

Tks 11/17

Vm heap 48
[Fascinate Android Development] jcurley:
After resetting batt stat, I still cannot get to charge over 95%.

phone just well not do it.

Edit: figured out that is is charging to about 4185mv, which is a full charge, but only showing 95%.

This is after a batt stat reset.

Battery is charging, but kernel not showing a 100%.

Not sure how this works, but is what I am showing. Went back to 11/16 and showed 100, in a full charge.

Comrade, maybe a bug in the trickle changes.
[Fascinate Android Development] bestchoicedon:
Same thing here. It will show increasing above the 95% but once at a full charge it goes to 95% when unplugged.
[Fascinate Android Development] notoriousB:
I'm getting this as well, same combo, thankfully the phone is not on my bedroom when charging tho!

I am also seeing 95% off charger, but it sure beats 82%, thank you!
[Fascinate Android Development] jcurley:
Funniest thing is, the voltage on the battery shows a full charge about 4180. At least that is what mine charges too.

SC

Tks 11/17

Vm heap 48
[Fascinate Android Development] comradesven:
Like I said, experimental.
[Fascinate Android Development] jcurley:
It is, but you have been so good, your experimental is better than most stable builds. :)

SC

Tks 11/17

Vm heap 48
[Fascinate Android Development] AuroEdge:
I flashed this kernel and a couple of times the phone would reboot to safe mode. No overclock or undervolt
[Fascinate Android Development] wessiide:
Is this new release worth flashing if we have no battery issues? The driver changes are they good to have?
[Fascinate Android Development] laureanop:
No and I don't see any differences. Touch screen and back lights work fine
[Fascinate Android Development] 4FatSno:
Works great on SC

Thanks for this great kernel!

sent from outerspace