yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Nephilim:
The issue was that 2.7.0.0 leaves storage unchecked by default in the backup section. You just have to tick the internal storage option on the top part of the backup page. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] JuanG:
I flashed Dirty_V but the camera app crash. In the kernel version say Dirty_V-SR not Dirty_V. It is a bug?

EDIT: Yes, it is a bug. I cleared data of camera app and launched it, the 1080p is not in the options. I think that Dirty_V link is Dirty_V-SR. Check please
[Samsung Galaxy Nexus] akhi24nick:
Which version of the kernel can I use with PA?

If I cannot use any of them which kernel can I use with PA?

The last time I flashed this kernel on an AOSP based ROM I had a boot loop, supposedly bcos of the ramdisk.

Please help me out
[Samsung Galaxy Nexus] osm0sis:
Should all work fine, flash and find out. If you get a bootloop flash another kernel. Why do people act like a bootloop is the end of the world? :p
[Samsung Galaxy Nexus] akhi24nick:
Its just bcos its 12am here and I dont want my phone to end up in a bootloop before sleep :P

Will try out then :)
[Samsung Galaxy Nexus] Hetalk:
It's still about 35 minutes to 12:00 AM in chennai. :D:angel:
[Samsung Galaxy Nexus] osm0sis:
Flash a working kernel: bootloop gone. Just gotta pull the battery or hold down the three buttons to catch it during the reboot. No big deal. :)
[Samsung Galaxy Nexus] bsmitty83:
I don't even call it a bootloop anymore . its now a boot delay ,cause it delays me about 10 seconds to pull the battery , reboot to recovery and flash another kernel lol
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4608636]bsmitty83[/MENTION] told us that the new SmittyV has some extraordinary in it which we should test. I needed my phone so I couldn't test it but did anyone else yet? And is there a difference?

I think he needs feedback on that. ?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] furb3t:
With last cm11 nightly 1803, with Smitty1503 kernel all works well while with DirtyVR1603 i have problem with display, where characters seem chinese characters and on screen there are a lot of white dots.
[Samsung Galaxy Nexus] dbh369:
Says "soon"in the op...
[Samsung Galaxy Nexus] bsmitty83:
Soon as in as soon as I get off these 12 and 14 hr shifts ....
[Samsung Galaxy Nexus] michierusama:
And rest of course.
[Samsung Galaxy Nexus] gohamstergo:
[MENTION=4608636]bsmitty83[/MENTION] Not to beat a dead horse with a stick, but I've been in contact with [MENTION=2538253]bponury[/MENTION] about the TouchControl issues. I think he has an idea for a fix. So, not sure if he's gonna post here or PM you, but just wanted to give you a heads up. :good:
[Samsung Galaxy Nexus] bsmitty83:
Just got his msg . i should be able to makebit work now . I know a lot of people use it so I'll make sure to get it to work
[Samsung Galaxy Nexus] gohamstergo:
You rock bro!
[Samsung Galaxy Nexus] dbh369:
No pressure! :D
[Samsung Galaxy Nexus] ashclepdia:
who has time for rest/sleep?

that stuff it's overrated.

every time I sleep there is 10 new pages to catch up on in this thread...

lol ;D
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=4544860]osm0sis[/MENTION] , I think I found the problem with lmk . I added a commit to kswapd that decreases the time spent in congestion_wait . gonna try that , revert the GPU commit so people can choose their own freq . still working on touch control support , bponury emailed me and said it was because of a certain few lines of code , but they haven't been edited in 3 years , so idk how it would be the cause . I'm gonna play around with some things and maybe I'll get lucky . I think he may have derped on what file it was but I think it still involves a file in the folder .

I'm trying to work some time in to actually do some things . as soon as I can get behind my laptop for more than 10 min I'll get to work lol .
[Samsung Galaxy Nexus] michierusama:
Lol. I do. :P and usually get lost in the thread :'(
[Samsung Galaxy Nexus] agreenbhm:
I've been getting random warm reboots a couple times a day. I'm running the Super RAM kernel with Vanir nightly. I'm not undervolted except for lowering the Smart Reflex values to 810. I also use Nephs other settings (aside from UV). I run at 1400Mhz max. Is this a kernel thing I can tweak or is the ROM buggy?
[Samsung Galaxy Nexus] fleckdalm:
I remember that I have read something about Bluetooth low energy sometime ago in this thread. Any news on this topic? Does this kernel support it?
[Samsung Galaxy Nexus] sam45:
BLE works with this kernel (using omnirom)
[Samsung Galaxy Nexus] Carlos_Manuel:
All Tuna's kernels has BLE support. Getting BLE support on a Nexus, depends of the ROM.

With this change on the device repository (bdroid_buildcfg.h) and the permission file you get BLE support:

#define BTM_DEF_LOCAL_NAME "Galaxy Nexus"
#define BLE_INCLUDED TRUE
#define BTA_GATT_INCLUDED TRUE
#define SMP_INCLUDED TRUE

Kernel 3.4 has more Bluetooth Low energy changes and features.

Kernel 3.0 has BLE support and what I know, with kernel 3.0 (same with 3.1?) you can only connect to one BLE device at the same time.
[Samsung Galaxy Nexus] cujo6801:
I thought I'd share

New and improved

https://www.dropbox.com/s/3qwvwp9tgn6zoza/AdAway (2.8.1).apk

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Charmacas:
Hey [MENTION=4608636]bsmitty83[/MENTION]!

I've now used DirtyV-R-03-16-14 for a while and noticed a few lags and also multitasking always used to take long.

Then I've decided to install the best working version for me so far which is cwm-DirtyV-RSR-3.2.14-Synapsed. I instantly noticed that the problems are gone. Also the wake up lag is less than with the version from the 16th.

Strange... I know... But I just wanted to let you know.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] Nice! Sound like good ideas.

Worth seeing what boype/Fancy has set up for LMK/kswapd perhaps as well, since we have the same process priorities set up in our boot script as him and I don't think they've got the LMK rampage issue. :)
[Samsung Galaxy Nexus] hardstyle86:
:victory:
[Samsung Galaxy Nexus] Swede2008:
oooooo there is an update to Trickster Mod in the play store
[Samsung Galaxy Nexus] bsmitty83:
I got a question for touch control users , what version of my kernel did touch control last work ?
[Samsung Galaxy Nexus] jerom87:
SmittyV-RSR-2.14.14

does 1080p work at the newest version of DirtyV-R { 3/16 }?
[Samsung Galaxy Nexus] AutomaticFailure27:
Not 100% sure, I more follow this thread than use it (still on JB) but I think someone mentioned that 2/25 was the last working TC.
[Samsung Galaxy Nexus] bsmitty83:
I don't think so , I think I derped and used dirtyV-sr config for dirtyv and forgot to change the version name . pretty sure all you need to do is rename your mediaprofiles.bak to ".XML and reboot . it'll restore your old profile before my ramdisk switched it out .
[Samsung Galaxy Nexus] hardstyle86:
TC works with 2.23 Smitty.
[Samsung Galaxy Nexus] bsmitty83:
2/25 does too
[Samsung Galaxy Nexus] Culex316:
2.14 dirtyV was the one (compiled on Sat Feb 22 2014)

I don't know much about kernel programming but it should be possible to restore the code...or at least make it work with an existing module (CM11) like boype's kernel.
[Samsung Galaxy Nexus] osm0sis:
The script renames that file on every boot, so they'd need to copy the .dvbak over the original but keep the .dvbak in place to work around it until you rename the config. :good:
[Samsung Galaxy Nexus] bsmitty83:
Yes and no . I'm just trying to figure out what messes it up , I just downloaded the app and am gonna find out

That's what I meant to say [emoji12]
[Samsung Galaxy Nexus] poo706:
I'm certain 2/25 was the last TC-friendly kernel.

[poo]
[Samsung Galaxy Nexus] bsmitty83:
No , I believe SmittyV-3/19 was the last touch control friendly version . [emoji16]

Back to old GPU freq for now . lmk should behave now as well .
[Samsung Galaxy Nexus] dbt816:
Getting an error installing SmittyV 3/19

E:Error in /tmp/update.zip

(Status 6)

Installation aborted

Maybe it's a corrupt download...I'll double check that.

Edit: download is fine...unzips on my laptop and contains the boot.img and update scripts
[Samsung Galaxy Nexus] Madsunable:
Same error on latest TWRP recovery

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] thoiloidainhan:
Got error installing Smitty 3/19 using twrp 2.6.3.1. Not twrp fault I assume as I have been able to flash all the newest ROM and kernel
[Samsung Galaxy Nexus] namtombout:
Goto the updater script in the zip and delete the assert maguro toro and toroplus lines. Repack and flash.
[Samsung Galaxy Nexus] metalspring:
4.7.4 actually, since it's the newest version. However there shouldn't be any major difference between 4.7.3 and 4.7.4
[Samsung Galaxy Nexus] Nephilim:
Both sabermod and linaro 4.7 v5's work without a hitch. I personally feel like 4.7 is a slight bit smoother than Sabermod but that could just be me.
[Samsung Galaxy Nexus] Blackcrx:
Smoother than sr4? This I gotta try. Downloading noa
[Samsung Galaxy Nexus] Nephilim:
The best part is it has the missing schedulers and governors people wanted to use. (fiops for me)
[Samsung Galaxy Nexus] clnzx2:
Yeah the one with 4.7.4 is running nicely. Safe to assume all the problems were from 4.8?
[Samsung Galaxy Nexus] Vekhez:
-90 from the stock kernel? [MENTION=2853378]Nephilim[/MENTION] Do you wanna add my previous voltages (page 48-49 I believe) and see if we get any more comments like this? If so I'll make a slight modification to them :D
[Samsung Galaxy Nexus] Blackcrx:
I run [MENTION=4544860]osm0sis[/MENTION] mpu voltages on almost all kernels and no issues at all. I wouldn't suggest the core or iva. I've had lockups when I play with those voltages.

http://xdaforums.com/showpost.php?p=34951507

Don't forget to thank him if you use his settings.
[Samsung Galaxy Nexus] bsmitty83:
I'm saying yes . like I said before I knew 4.8 was a nogo , so it suprised me when one of my test fixes actually worked so I put it out there . but its apparant that it still needs work to be 100% stable . I'll stick with the linaro 4.7 chain that served me very well for as long as its been out .
[Samsung Galaxy Nexus] clnzx2:
Awesome. Your kernel is flying with 4.7.3 no issues even at 1.72ghz :)
[Samsung Galaxy Nexus] Nephilim:
This.....

Agreed, I run between -50 and -100 across the board on MPU but I do not touch Core or IVA. As far as undervolting goes I'm pretty mellow on it as far as MPU so that part of my custom settings are always a base starter that I can confirm works well for me. Since every Gnex is slightly different I let everyone experiment as they will from that point on if my voltages don't work.

Keep up the good work though Vekhez and I'll probably play around with your settings just for my own fun sometime today. ;)

---------- Post added at 04:39 PM ---------- Previous post was at 04:35 PM ----------

I'm hoping the 4.7 change-over remedies my overnight charging SOD's, honestly that's the only real issue I have. I'm confident the occasional 1 to 5 second lockup/freezes that happen every so often will be squashed soon enough in one of these future builds. I mean between one update it went from heavy keyboard lockups, severe recents menu lag and random freezing to now only the occasional keyboard freeze and sometimes app lockup, neither of which require a battery pull, just a little patience while the device kicks back into gear. :D

Looking forward to the next kernels and any neat new modifications it brings!
[Samsung Galaxy Nexus] pianistaPL:
I installed Sabermod version and is running fast as hell of course :) I don't know how is working Linaro 4.7 version but Sabermod is deninitely fast.
[Samsung Galaxy Nexus] bsmitty83:
Anybody still having issues when the 4.7 toolchain or sabermod tc is used ? I't sounds like it did , either way I'll have some new ones to test
[Samsung Galaxy Nexus] Hetalk:
I just flashed the latest commotio vanir build from today. Restoring my stuff.

Then I'll see how this 4.7 kernel goes with vanir and report back.
[Samsung Galaxy Nexus] pianistaPL:
As i said, i'm using metalspring's Sabermod version and don't have any issues on stock voltages with Deadline + hyper.
[Samsung Galaxy Nexus] scarcry:
I flashed [MENTION=4328678]metalspring[/MENTION]'s updated dirtyV-SR5-test2 on vanir 012214 an hour ago.

so far no issues to mention but an hour is hardly enough time.

Still thanks for all the hard work [MENTION=4608636]bsmitty83[/MENTION] !

Tapatalked from my maguro running vanirAOSP nightlies
[Samsung Galaxy Nexus] juju2011:
I had a few freezes and unresponsive screen on sm kernel posted log and kmsg going to try again with nephs custom settings [MENTION=4608636]bsmitty83[/MENTION] care share your settings for dirty v I'll throw them in trickster and see if they make a diff
[Samsung Galaxy Nexus] Nephilim:
I ran the Sabermod test kernel for about 2hrs and only had one major issue, I got an SOD from leaving my device sit for about a half hour. That was my fault though because I had it set to Interactive forgetting that it was borked.

I have now been running Linaro 4.7.4 test kernel for about I'd say a little over an hour with not a single problem outside the usual freezes that happen during typing and occasionally when opening apps.

My vote is to build with Linaro 4.7.4, I felt it's a tiny bit smoother and faster. Just my opinion of course.

---------- Post added at 05:20 PM ---------- Previous post was at 05:19 PM ----------

I did a little tweaking again to my settings, not alot but a few things are changed. You can find them on page 49, I marked my modifications in green. ;)
[Samsung Galaxy Nexus] juju2011:
Kk going to store to get milk n diapers for the Lil ones will check them when I get back
[Samsung Galaxy Nexus] Vekhez:
Yeah, I agree, seems smoother :D
[Samsung Galaxy Nexus] bsmitty83:
OK thanks guys . I'll be changing a few things but got updates for 3 kernels to do , (really its 6 builds) . should be able to get it posted tonight .

Btw [MENTION=2853378]Nephilim[/MENTION] . loving the SIG you made for my kernel , thanks again
[Samsung Galaxy Nexus] cujo6801:
No

Sent from the "DOG" pound
[Samsung Galaxy Nexus] dbt816:
That works :)
[Samsung Galaxy Nexus] Nephilim:
I'm going to go ahead and just wait for a booting version. I'm too sick to unpack and delete files from my phone.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] dbt816:
Dude... still? That sucks. :(
[Samsung Galaxy Nexus] bsmitty83:
Give me asec I effed up the meta ....

The new zip is up

Sorry [MENTION=2853378]Nephilim[/MENTION] , being sick is never fun
[Samsung Galaxy Nexus] Nephilim:
Yea man, going on 4 days of complete agony. Can't wait for smitty to reup the 3/19, been waiting for something to flash while bedridden.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Madsunable:
Jeah, I delete the lines and now the kernel AND TouchControl works.

Thanks [MENTION=2538253]bponury[/MENTION] and [MENTION=4608636]bsmitty83[/MENTION]

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] bsmitty83:
Its up and boots , I swear
[Samsung Galaxy Nexus] dbt816:
Running great here!
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=3685904]ak[/MENTION] [MENTION=2838735]aosp[/MENTION]

This is looking pretty cool:

http://kevinboone.net/kbox2_downloads.html

I'm using his gcc packages to try and set up a native build environment on my N7 '13. ;)
[Samsung Galaxy Nexus] bsmitty83:
More than cool , that's bad-freaking-ass man . I've been waiting for something like this , makes owning a tablet worth it
[Samsung Galaxy Nexus] cujo6801:
My N7/13 will love you...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Culex316:
What's your PayPal address? :D
[Samsung Galaxy Nexus] osm0sis:
I've been trying to compile git for the last little while and running into some dependency annoyances (over stupid **** the NDK doesn't provide like iconv.h and libintl.h), but then I found this:

https://play.google.com/store/apps/details?id=com.spartacusrex.spartacuside

Basically the same idea as kbox but it doesn't emulate the full Linux filesystem like kbox does. It does have git though, so I might just steal all the useful binaries from it and move them into kbox. ;)
[Samsung Galaxy Nexus] Culex316:
What module are you trying to load on the kernel? I tried loading bsmitty 3.16 module on DirtyVRSR version 3/6 using the paid touchcontrol app and it said failed to load kernel.

I am using CM11 M4 and it worked with Bsmitty 2.14 version perfectly before. :confused:
[Samsung Galaxy Nexus] Madsunable:
Try the new 3.19 build from the OP :good:

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] Culex316:
oh I'm such a dummy I downloaded 3/16 instead of 3/19 :eek: sorry.
[Samsung Galaxy Nexus] milojoseph:
i doubt you will remember but you had a modified version of dirty in your dev host... Did you remove them?
[Samsung Galaxy Nexus] osm0sis:
Yes. I remove them once my ramdisk changes are integrated.
[Samsung Galaxy Nexus] Charmacas:
Installed SmittyV-R-03-19-14 and will report as soon as I notice something.

Should we test for anything special [MENTION=4608636]bsmitty83[/MENTION]?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Swede2008:
Smittyv 3-19 touch control working :D
[Samsung Galaxy Nexus] imjustafq:
what is the best app can i use to edit kernel setting?

via my neighbour's forehead
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4608636]bsmitty83[/MENTION] the new SmittyV-R works better than the previous version but is noticeable less smooth in terms of switching and opening apps than cwm-DirtyV-RSR-3.2.14-Synapsed.

This is of course a first impression but I already used my phone a lot this morning.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] DR3W5K1:
Mine phone was like that for a couple of hours when I flashed it. Now that it's had time to settle in seems smoother than 3-2.
[Samsung Galaxy Nexus] Charmacas:
I am always monitoring my CPU after the phone has booted up to see when it settled down. So this is not the problem. ?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] RoadToNever:
3/19 gives me perpetual boot up, reverting to 3/16 for now.
[Samsung Galaxy Nexus] DR3W5K1:
Tried all governers ondemandx is the only one I could get to play nice. Only after I tweaked the settings though.
[Samsung Galaxy Nexus] Charmacas:
I had this with the versions before. Try to hold all buttons to come to the bootloader. Boot the recovery and then choose restart system. Now your phone should boot up.

I don't know what is causing this logo bootloops.

It would be nice if you could give your settings so that we can test them. ☺

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] DR3W5K1:
Min 230000

Max 1200000

Sorry it's ondemandplus...

---------- Post added at 03:38 AM ---------- Previous post was at 03:29 AM ----------

Sorry.....

Change up threshold to 65

Working better?
[Samsung Galaxy Nexus] RoadToNever:
Tried your trick with no luck(both 3/16 & 3/19). Are you using TWRP?
[Samsung Galaxy Nexus] Charmacas:
Yes, I do. 2.7.0.0

Trying your settings now!
[Samsung Galaxy Nexus] paarthdesai:
my settings.... ? works fluid enough...

scheduler noop
[Samsung Galaxy Nexus] Punkiderma:
Flashed 3-19, I have 739 mb of ram.

Is that normal? I believed it was a nomem build with 698. I flashed it over franco kernel (that has asram), could that be the problem?

Thanks!
[Samsung Galaxy Nexus] DR3W5K1:
Something is wrong with the latest Smitty. CPU constantly pegs out for no reason. Switched back to 3-2 all good again.. I wish that the 3-2 build didn't have the lmk rampage bug cause it's the smoothest I've ever used. Anyone else that rolls back to 3.2 tryout hotplug super smooth and omg that battery. I'm getting three hours of OST with it consistently. If anyone wants the hotplug variables I'm using just let me know.

---------- Post added at 08:04 AM ---------- Previous post was at 07:50 AM ----------

​

Does anyone know if it's possible to disable LMK?
[Samsung Galaxy Nexus] GilGameshn1:
I think with Performance app in Vanir or Synapse ... Could be wrong thou . [emoji11]

Sent From HellRift
[Samsung Galaxy Nexus] Culex316:
Even with multicore power saving switched to "0" (since it does not play well with hotplugging governors, I still get random reboots when using hotplugging governors on my phone so I don't know how you guys do it.

Normally I use ondemandplus which is the best with respect to battery life and performance
[Samsung Galaxy Nexus] Nephilim:
3/19 is working flawlessly on my settings, no lag, no cpu maxing, no reboots, no freezes and no sod's. I have not a single issue with this kernel. My settings are made with trickstermod, no scripts and no other performance apps.

Sent from my Android 4.4.2 Galaxy Nexus

---------- Post added at 09:08 AM ---------- Previous post was at 09:04 AM ----------

Ondemandplus sucks for performance compared to Interactive, the minor battery improvement isn't worth it at all, to each his own though. I get amazing battery life with my settings including Interactive gov on all SmittyV kernels.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] dbt816:
Well 3/19 was running great. Rebooted this morning (to kick a media scan) and two things happened:

1. Went from booted to screen lock to suspend without me ever unlocking the screen. Caused a SOD. I've seen this numerous times, and I believe even other kernels in the past. I think I'm just in the habit of unlocking it when it boots now :)

2. WiFi quit working. Worked fine on initial load, but after the reboot it won't connect.

Going to try a reflash since I did a really dirty install with the borked zip file last night :)

EDIT: WiFi settings had lost my access point password...I recall others posting on this, but it's the first time I've seen it myself
[Samsung Galaxy Nexus] ashclepdia:
I am doubtful this is kernel issue.

this has been happening to me for while now. and I haven't ran smitty yet(atrocious I know!)

it seems random, I've been trying to figure out what causes it to happen. it seems to happen less when I force the wifi band to ONLY 5ghz or 2.4ghz. but, it still happens occasionally then also. (and even more so if the router I'm connecting to is dual band, and I can access EITHER 5ghz or 2.4ghz on my gnex)

I've also noticed that it doesn't exactly FORGET/drop that access point completely every time. the "saved" will disappear from under AP name in WiFi list, but sometimes will come back on its own, and almost always a toggle off/on of WiFi will bring it back without me having to add it again

it also does not take the ap out of the file used to store ap(s)(/data/misc/wifi/wpa_supplicant.conf)

if anyone has tracked down exactly what causes this, let me know. I suspicious that it has been caused by the cloud back up of user settings that restores from Google, but I also suspect that it could have started a long time ago when I once restored AP via Helium backup(I should wipe data I know, it's been very long, but I've also seen people say this happens and they haven't done any of that)

that's my experience so far regarding this.

---------- Post added at 01:09 PM ---------- Previous post was at 01:04 PM ----------

lmk if I'm not mistaken is "Low Memory Killer" aka OOM setting. which is a part of Linux in general. I do not believe it can be "disabled". if you did, you would run out of ram, have no ram management, and would run into some major issues.

I do believe however that you can tweak the way it behaves, though I'm not sure if you have to build your own custom values directly in kernel or not(used to easily be able to change them, but something changes at one point with where the settings are stored/read from)

apologies if I'm way off here, let me know if I am so I don't keep thinking wrong lol
[Samsung Galaxy Nexus] dbt816:
I would agree that it's not a kernel issue... it DOES connect once you put the AP password back in, so the wireless driver is good.

This was either introduced in the 3/19 Vanir nightly (but I don't see anything obvious in the change log to show that it could have been) or it has been there lurking and I just hit it :)