yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bvsbutthd101:
Here I thought I was only person experiencing this. I was about to post about it. Flashing the kernel again seems to fix it but it ends up happening again. I've tried all three versions of the latest kernel, happens on all of them. I don't remember it happening on the last version of Dirty V I was on.
[Samsung Galaxy Nexus] cujo6801:
Done...

Thanks...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] osm0sis:
Clean flashing your ROM fixes it for everyone so far. Then keep dynamic fsync disabled to decrease the likelihood of it happening again.
[Samsung Galaxy Nexus] @jmorosky:
I am experiencing vbus-tuna.otg wakelock. My phone won't go into deep sleep. I'm not sure if this started with V2 or not. Any suggestions?

Sent from my OmniMetal and DirtyV
[Samsung Galaxy Nexus] Funnydwarf:
First of all try to exclude any software problem.

That said, it's very likely caused by a faulty USB port: sadly a well know issue. Some people fixes it by cleaning the port, others by straightening back that tiny metal strip you can see inside. In my case nothing worked and I had to change the USB port flex.
[Samsung Galaxy Nexus] ashclepdia:
fakemailgenerator.com

boom, your welcome

lol
[Samsung Galaxy Nexus] ILA:
[MENTION=4328678]metalspring[/MENTION] I see you are active in this thread: [COMMIT] [AOSP] JustArchi's ArchiDroid Optimizations - Increases performance up to 6x

That's a dev thread so I couldn't ask you there. Thankfully this thread is more liberal for on/off topics :good:

How difficult would it be to enable those flags on your GNex ROMs (or maybe even a custom build of Vanir? :D ) and this awesome kernel?

I'm sure [MENTION=4608636]bsmitty83[/MENTION] , [MENTION=4544860]osm0sis[/MENTION] and others saw this... :)
[Samsung Galaxy Nexus] bsmitty83:
It'd be quite hard kernel side since its all ROM specific . all those flags are already set kernel side .
[Samsung Galaxy Nexus] metalspring:
FYI, I'm actually compiling a vanir build with those optimizations right now (with a couple essential changes) lol. However it is for the m8, and if it does work well then maybe someone can compile tuna versions (it would take me too long lol).

And with all these optimization and linaro threads around anymore maybe I'll just make my own thread combining the best of everything (cflag optimizations, linaro optimizations, and kernel optimizations) since I do know a bit about that stuff :p
[Samsung Galaxy Nexus] osm0sis:
I think I know what you should call your thread.. :cool:

[YOUTUBE]33VOGilOT0w[/YOUTUBE]
[Samsung Galaxy Nexus] metalspring:
Why you delete your post? Maybe some people wanted to listen to your music??
[Samsung Galaxy Nexus] michierusama:
I love this dude randomness lmao.
[Samsung Galaxy Nexus] michierusama:
Lol. I could never tell what you will do next bahaha. Random guy.

I went back to latest smittyV after using the metalsmitty gov test. It was good tough.
[Samsung Galaxy Nexus] metalspring:
So to all the devs in this thread, hows this for a start of an all in one super optimization commit? lol (nothing fancy yet, just basically a base to get started with -O3 and fstrict-aliasing)

https://github.com/metalspring/build/commit/19adc4f36b3c4316780f2ad00b981adb7f3bbcc1

Also anyone up for testing a linaro-ized build of omni rom if it builds and isnt totally broken lol? nothing really special added yet, just dirtyv kernel (of course), an adapted version of the commit above, link time optimization, -O3, strict-aliasing, all the usual stuff. Only thing experimental is adding a -O4 and strict-aliasing to clang compiler (-O4 on clang is basically like -O3 and LTO for gcc)
[Samsung Galaxy Nexus] pattyboi:):
ill test any day of the week :good:
[Samsung Galaxy Nexus] metalspring:
Btw, anyone else know any popular roms that are known for optimization for other devices?

Obviously I know vanir and liquid, but dont know of any other really popular multi device ones.

I'm just looking for well tested cflags to experiment with (well tested meaning used on multiple devices)
[Samsung Galaxy Nexus] jkleo:
What about Slim ROM?
[Samsung Galaxy Nexus] metalspring:
Carbon roms cflags are essentially stock aosp lol, they might have other optimizations hidden away elsewhere though

They do have some interesting ones there but then again they dont particularly make any sense the way they have them but I think combining them a little differently may do something.

i.e. in the -Os option for TARGET_arm_CFLAGS they have fno-zero-initialized-in-bss, -Os is designed to try to make code as small as possible, but fno-zero-initialized-in-bss should inherently make the code larger for more accuracy. (the opposite of that option is enabled by default making code smaller but slightly less accurate). I'm thinking -O3 plus fno-zero-initialized-in-bss might make for pretty large code, but it may also improve performance as well since some code will be more accurate
[Samsung Galaxy Nexus] pattyboi:):
[MENTION=4328678]metalspring[/MENTION] ose might have some good ones
[Samsung Galaxy Nexus] metalspring:
ose???
[Samsung Galaxy Nexus] jhonnyx:
http://www.drdevs.com/subs/ose/

https://github.com/Team-OSE

aaand:

http://www.drdevs.com/devs/?dir=teamose/OSE/Nightlies/maguro

(did not try it yet)
[Samsung Galaxy Nexus] metalspring:
Even codefirex isnt any help with finding useful cflags since they switched to compiling in almost all clang (hence testing gcc cflags wasnt really needed), not to mention that they are no more.

However I did find that unfortunately trying to make clang compile with -O4 doesnt work lol (for those that dont know even though most roms mainly use gcc, there is still code compiled with clang, mostly graphics stuff as vanir said before). But passing -O3 (same as clang -O4 minus link time opt) and fstrict-aliasing to clang seems to work :P

Speaking of which any toro users here are to test a "stock" omnirom with latest dirtyv kernel and these optimizations (except that clang is -O3)-

https://github.com/metalspring/android_build/commit/4d75087c4e135570516b68a57ca8c2789e80dc39

https://github.com/metalspring/android_build/commit/c831f535a48aea75068e996c39f85c601d24f7b7

https://github.com/metalspring/android_build/commit/86536e2f19daf7624042e59dd20a20d1fbb0d8e1

https://github.com/metalspring/android_build/commit/7f07405f3b1ffe152b63b5d1af763b47673fc2e8

FYI, it might be a good idea to reflash the latest version of dirtyv anyway, since I didnt add the ramdisk changes in this build (it was mostly just to get the optimization commits tested)
[Samsung Galaxy Nexus] metalspring:
Yeah, thats why I stick to proven combinations of cflags for now lol (might add an option to enable experimental ones for testing later though).

And the cflags I used were essentially the same as vaniraosp plus LTO cflags and std=gnu++11 and the other stuff is mostly IAmTheOneTheyCallNeo's commit to easily specify different gcc versions for androideabi and the kernel toolchain

:P

https://github.com/VanirAOSP/build/blob/kk44/core/combo/TARGET_linux-arm.mk

https://github.com/VanirAOSP/build/blob/kk44/core/combo/select.mk

https://github.com/VanirAOSP/build/commit/2a5a902c3a9ba47cd173d789caf74f6ffd9853fb

(TARGET_THUMB_STRICT is just fstrict-aliasing or -fno-strict-aliasing)
[Samsung Galaxy Nexus] DR3W5K1:
LOL. I'll bite.

[MENTION=4328678]metalspring[/MENTION]
[Samsung Galaxy Nexus] pattyboi:):
[MENTION=4328678]metalspring[/MENTION] im down for some metalized omni (:
[Samsung Galaxy Nexus] metalspring:
Toro only test right now but here-

http://xdaforums.com/showpost.php?p=52803913&postcount=2280
[Samsung Galaxy Nexus] RLC44:
Been jonsing like Pookie for some new omnimetal!
[Samsung Galaxy Nexus] metalspring:
I wouldnt call that a new build of omnimetal yet, more like getting all the linaro stuff and other basic optimizations and testing the clang optimization (if you try that build be sure to test graphic benchmarks since thats what clang mostly compiles)
[Samsung Galaxy Nexus] RLC44:
[MENTION=4328678]metalspring[/MENTION] I guess I'm a little eager then. Thanks for the clarification and thanks for putting it together. Still going to give it a whirl.
[Samsung Galaxy Nexus] pattyboi:):
thanks buddy :good: dling as we speak

EDIT:this build is perfect.
[Samsung Galaxy Nexus] cujo6801:
Hello is there anybody out there

is there anybody home

okay just another pin prick

Now I can wait for an update

There is no pain...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] metalspring:
How do the graphics do in benchmarks? They should do a little better than most roms do (except vanir should be about the same lol)

Btw, what rom should I compile for the m8? Vanir and liquid are out (vanir doesnt leave much to add on lol, and liquid doesnt have a gerrit which makes cherry picking commits much much harder). And cm is out, because cm is just plain evil, lame, poor attitude, and just killing open source as we know it...
[Samsung Galaxy Nexus] bsmitty83:
Omnimetal m8? ...........
[Samsung Galaxy Nexus] metalspring:
Yeah, I was thinking of that but since omni uses a twrp recovery base, while cm (and just about everyone else) uses a cwm recovery base, it would be way beyond me to get the recovery stuff set up properly, especially since there isnt a lot of source for twrp for the m8 yet.

Just to show what I mean-

basically all the twrp source I can find is like this-

https://github.com/jmztaylor/android_device_htc_m8ul/blob/android-4.4/BoardConfig.mk

However cm device tree (which is about the same every other rom has right now) is this-

https://github.com/metalspring/android_device_htc_m8/blob/android-4.4/BoardConfig.mk
[Samsung Galaxy Nexus] rkpeterson:
I'm praying for dirty. M8
[Samsung Galaxy Nexus] metalspring:
Yeah, bsmitty needs to join the m8 party lol, so far we already have some of the vanir devs, liquid devs, francisco franco just got an m8, faux has an m8, I guess [MENTION=3685904]ak[/MENTION] is thinking of getting an m8, plus all of us other devs (or in my case, almost-semi-but-not-really-dev).

I say we start a donation fund to get him an m8 :P
[Samsung Galaxy Nexus] bsmitty83:
Twrp shouldn't be too hard to build for . just follow the instructions on twrps how to page . really the only thing you absolutely need is the device resolution I believe .

And if nobody's got a twrp build for the m8 , all the more reason to do it [emoji123]

Lol the m8 is cool , but I haven't even built anything for my note 2 yet lol , [MENTION=2838735]aosp[/MENTION] and myself have been slugging it out with f2fs on the nexus , its gonna happen .......
[Samsung Galaxy Nexus] metalspring:
There are twrp builds for the m8, but they dont work properly on all variants, I myself got into an interesting situation where the twrp I was using randomly decided to not flash roms or restore backups (good thing I had a cwm zip on my phone lol). Btw, I wonder how f2fs would work on the m8 or if theres even support for it, I remember seeing a few kernels with a commit adding f2fs filesystem support somewhere
[Samsung Galaxy Nexus] metalspring:
[MENTION=4608636]bsmitty83[/MENTION], you want to see something funny? Check out this post lmao-

http://xdaforums.com/showpost.php?p=52812435&postcount=539
[Samsung Galaxy Nexus] bsmitty83:
It'd probably work good , it seems like f2fs is becoming popular. For some reason the nexus doesn't want to give up ext4 lol , every recovery we build for f2fs won't flash the ROM correct. It says it does , but the /system folder is empty . we got the recovery to wipe and format f2fs , mounts correctly and all , just can't get a ROM to flash. That's why there hasent been much activity on this thread , been working on that .

Ive added all those flags before , even the redundant ones just to see if it did make a difference , it doesn't .

I think the problem is people don't know that when you use -O3 , its just a lot of flags , not a flag itself .
[Samsung Galaxy Nexus] sagara.sandaru:
bponury is gonna terminate Touch control app again.. Now I can say he's an real asshole.. He doesn't even care that people paid for it. Is it that hard to make such an app? [MENTION=4544860]osm0sis[/MENTION] it would be great if u could add some sort of similar feature in to Synapse? [emoji6] If I knew how to program I would make such an app and give it for free for nexus users.
[Samsung Galaxy Nexus] pvkiniyan95:
Simple

Bring back touchwake...
[Samsung Galaxy Nexus] poo706:
Link?

[poo]
[Samsung Galaxy Nexus] Hetalk:
2nd last post on this thread http://xdaforums.com/galaxy-nexus/themes-apps/app-mod-touchcontrol-pgm-galaxy-nexus-t1721895/page265
[Samsung Galaxy Nexus] sagara.sandaru:
did u mean the link for his post that he mentioned about this?

http://xdaforums.com/showthread.php?p=52816210
[Samsung Galaxy Nexus] poo706:
Bummer. Is there a way to extract the module from our current setup so that we don't have to rely on the soon-to-be-defunct app server to download from?
[Samsung Galaxy Nexus] paarthdesai:
lol ^ again :@

bdw , how to backup the module , here - http://xdaforums.com/showpost.php?p=52821410&postcount=2654
[Samsung Galaxy Nexus] osm0sis:
Yup. Since there would be no conflict anymore, Smitty could add t2w back to the kernel source and I could then add a switch for it to Synapse.
[Samsung Galaxy Nexus] aosp:
Hopefully this means he terminates himself too right?

[MENTION=2400340]Jimsth[/MENTION] ?
[Samsung Galaxy Nexus] michierusama:
A little OT how can I flash CWM recovery using terminal emulator. I tried.

Su

Flash_image recovery /sdcard/recovery_image_name

But got error that it cannot find the recovery partition.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=5476864]michierusama[/MENTION] flash_image is for mtd partitions only I think, ours are emmc. You need to dd the image to the correct block.

su -c dd if=/sdcard/recovery.img of=/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery

Same goes for the boot partition (kernel). That's how all the apps do it.

It needs to be an image though, if you write a zip that way you'll have a bad time.
[Samsung Galaxy Nexus] michierusama:
:( Dont know how.
[Samsung Galaxy Nexus] metalspring:
It would be nice if you guys could get something like this commit ported over to the gnex

https://github.com/xboxfanj/android...mmit/305cb7c6cb6c3e74996a2a0d970ff11fda537a47

And this might be nice too if it could be ported over

https://github.com/xboxfanj/android...mmit/f678488b4a2d4af27ae5619a4dd762c4e1de7c26
[Samsung Galaxy Nexus] poo706:
I used this to install CWM Touch recovery on my gnex: https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools

[poo]
[Samsung Galaxy Nexus] michierusama:
Thanks for the help guys.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4446775]cgollner[/MENTION]'s Flashify is also fantastic. :)

Again, they all do it with the command I posted. :good:
[Samsung Galaxy Nexus] ILA:
And s2w? :eek:
[Samsung Galaxy Nexus] michierusama:
Thanks. Downloaded. Also I wanted to know why your 900 colors script is not working on stock cm11 kernel... Lol just curious.
[Samsung Galaxy Nexus] osm0sis:
Oh, just the usual "CM did it differently than everyone else just to be difficult."
[Samsung Galaxy Nexus] ashclepdia:
there is also an app called flashify that works great for installing img files(boot.img, recovery.img)

edit... the powerful oz beat me lol

---------- Post added at 07:16 PM ---------- Previous post was at 07:14 PM ----------

does your script set the safety to off?

I wonder if That might be causing issue, not letting them set above "200" for mults
[Samsung Galaxy Nexus] michierusama:
Thats what I tought. Also I was reading some commits and they are like working con f2fs too.
[Samsung Galaxy Nexus] metalspring:
Lets see if anyone besides [MENTION=1533050]bsmitty[/MENTION], [MENTION=4544860]osm0sis[/MENTION] and [MENTION=486080]asop[/MENTION] get what this is lol :P

https://github.com/metalspring/andr...mmit/26e6b1f239c7bccec3691d6ba5ade90a902d11e0

---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------

Yeah, more for other devices that can more easily use it than the gnex though...
[Samsung Galaxy Nexus] ILA:
Hahaha, like the way you changed it. Such Deadpool. very developer options. Wow! :D
[Samsung Galaxy Nexus] bsmitty:
Hey guys & gals, I have quick announcement...I'm not bsmitty83!!! LOL! I'm a lesser known & even less knowledgeable user, not a developer. So I'd just kindly ask that, when you refer to bsmitty83, that you reference his entire username.

But hey, no harm done. About as close to my 15 seconds as I'll ever get haha!
[Samsung Galaxy Nexus] ashclepdia:
hahaha!

that's awesome, I think I'm guilty of that in the past, once I realized I was forgetting the 83 I changed it lol.

that could drive someone NUTS! can't imagine amount of notifs that could popup from that.

if it kept happening to me id add a 1 to my name lol!!! Luckily I happened upon a nickname I got IRL(by the way, for those reading my name, it's a mix of Ash and Encyclopedia....yes I KNOW I spelled it wrong, on purpose) so not many could mistakenly type mine in...not that I'm popular or anything anyways.

I'm sure we can all appreciate your request:) :eek:
[Samsung Galaxy Nexus] pkgnex:
That's hilarious!

I feel pretty bad for this guy, though... kind of like osmosis ;)

I once had a phone extension of "180" at a previous job, so I got every phone call from every a-hole inside the company who was dialing a 1-800 number and forgot to dial "9" to get an outside line, so I can definitely empathize with "bsmitty."

Everybody should "Thank" him for his patience and bump his thanks meter up a bit ;)
[Samsung Galaxy Nexus] michierusama:
Lmao. Dude youre lucky :P smutty is awesomeness
[Samsung Galaxy Nexus] metalspring:
Oh hey, whats this I see? ;)

Starting compilation

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=4.4.2

TARGET_PRODUCT=omni_toro

TARGET_BUILD_VARIANT=userdebug

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

TARGET_CPU_VARIANT=cortex-a9

TARGET_GCC_VERSION=4.8

TARGET_GCC_VERSION=4.9

HOST_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-3.13.0-24-generic-x86_64-with-Ubuntu-14.04-trusty

HOST_BUILD_TYPE=release

BUILD_ID=KVT49L

OUT_DIR=/home/metalspring/android/omni/out

Oh and there appears to be a bit of activity here :P

https://github.com/metalspring?tab=repositories
[Samsung Galaxy Nexus] apollo07:
No maguro love?
[Samsung Galaxy Nexus] metalspring:
This is still a test build lol, hopefully all variants will get builds starting tomorrow.

And so this isnt too far off topic-
[MENTION=4544860]osm0sis[/MENTION], do you think you could help add in the dirtyv/synapse ramdisk changes?
[Samsung Galaxy Nexus] pattyboi:):
*backflip started*
[Samsung Galaxy Nexus] metalspring:
*watching thousands (10s of thousands?) of lines of code go by waiting so I can compile other fun stuff*

Btw anyone want to help out with omnimetal in the future? That is if I can port it to the m8 lol

Knowledge of java preferred and C/C++ knowledge a bonus but neither are required :p

Only requirements are a pc, an android phone and a sense of humor lol
[Samsung Galaxy Nexus] bsmitty83:
Sorry about that man , lol yea that must be annoying as hell . Trust me with a name like smith , I know how it feels [emoji6]
[Samsung Galaxy Nexus] bsmitty83:
You know when you've been compiling long enough when you dont even need to read the code , you just know by the length of the line and shape of the paragraphs flying by if something is wrong or not lol , If you really want a headache use "-v " with make [emoji39]
[Samsung Galaxy Nexus] metalspring:
Kernels are really annoying since they just go on and on after an error and then at the end you're just like wtf happened, where's my damn zImage lol
[Samsung Galaxy Nexus] osm0sis:
:laugh: I want him to suffer for taking my first choice of handle. ;) :p

Did you already add the commits from last time so I just need to update? I'll take a look tomorrow. :)
[Samsung Galaxy Nexus] metalspring:
Yeah, everything from before is still there lol

Btw, I see franco is starting to try to make kernels for the m8, but couldnt get his first try to even boot :P

Since you worked with him before you should throw him this commit along with how to make a boot.img with a dt.img (like your kernel kitchen does). I've used it and it does in fact work perfectly for the m8, and this commit makes it easy to get the dt.img needed

https://github.com/Team-CodeCraft/CheckM8/commit/0e7b5f068c4f1546863c5ba83057dac060e77221

I tried to tell him on g+ but I think it got lost in all the replies he gets lol
[Samsung Galaxy Nexus] bsmitty:
You feel my pain, brotha, you feel my pain. Haha, no big.

On a side note, I may not own a Gnex but thanks for what you do! Keep it up :good:
[Samsung Galaxy Nexus] osm0sis:
Is there no thread yet? He's usually really good in his primary focus thread. If there is, definitely post this there with a link to my GitHub/mkbootimg fork. It supports all that and more. My unpackbootimg splits dtbs and seconds even. :)

If there isn't a thread, let me know and I'll definitely fire an email off for you.
[Samsung Galaxy Nexus] metalspring:
I dont think there is a thread yet, he just started working on the m8 like a day ago lol. He just commented on g+ how he tried to make a kernel but it wouldnt boot, and his source shows no changes at all, just initial commit of stock source
[Samsung Galaxy Nexus] osm0sis:
Gotcha will do then. I also still need to email him about the downgraded SELinux paid app sh*t CM caused which affected r396. :good:

I have a hunch they f*cked tethering for most custom kernels too. Still no word from [MENTION=2838735]aosp[/MENTION] on an updated binary. [MENTION=4608636]bsmitty83[/MENTION] can you mention it to him the next time you're in contact about your f2fs work?
[Samsung Galaxy Nexus] paarthdesai:
double tap to wake O.o ?

---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------

double tap to wake ? O.o
[Samsung Galaxy Nexus] osm0sis:
It's a phone thing. You are using it while it's charging, therefore it needs to draw more amperage to both operate and charge. This kernel has raised the throttling temperature threshold to 80 degrees, so that may accentuate it a bit, but understand that it's totally normal and expected.
[Samsung Galaxy Nexus] büscher:
Yep, safety limit wont let you go past 200.
[Samsung Galaxy Nexus] osm0sis:
My most recent 900 script should definitely disable the safety though.. So I'm still guessing CM did something else to break compatibility.

Funny, I swear [MENTION=4328678]metalspring[/MENTION] showed me a commit where CM was supposedly bringing color and a few other things back in line with the rest of us. Maybe it hasn't been merged yet?
[Samsung Galaxy Nexus] büscher:
Haha, I don't doubt that if the safety limit line is there ;)
[Samsung Galaxy Nexus] metalspring:
It has been merged, maybe by merging it they actually broke it lol

Actually looks like they saw there might be an issue and merged it anyway... well thats cm for ya...

Heres the commit if you wanted to look through it-

http://review.cyanogenmod.org/#/c/56637/
[Samsung Galaxy Nexus] kinfolk248:
You wouldn't happen to know a way to squeeze a little more battery out would you? I was gonna clock down to 920 but idk cus I already get a stutter when playing music at 1.2ghz...

Just lowered temp to see if that help, thanks for the knowledge...
[Samsung Galaxy Nexus] osm0sis:
It's all about wakelocks and min freq. I have no issue playing music with min 190 MHz. Don't OC max more than 1.3 GHz. GPU OC (if at all) no higher than 384 MHz...

My deep sleep is around 95% and my idle drain is like 0.4%/h. Screen on time isn't stellar but that's KitKat for you.

Mostly I just recommend you subscribe to the BetterBatteryStats thread for a few weeks. Don't post, just learn how to read your wakelocks and get a proper idle drain reading, then see what's keeping it awake and slim down your device.

Search the wakelocks you find. If you are stumped then post according to their rules for logs. :) :good:
[Samsung Galaxy Nexus] metalspring:
just going to drop this in here...

Package complete: /home/metalspring/android/omni/out/target/product/toro/omni-4.4.2-20140522-toro-HOMEMADE.zip