yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Nephilim:
Turned out my overnight charge SOD's were a result of Linaro 4.8 toolchain in the kernel, since Smitty has switched back to 4.7 they are gone.

The main SOD's were a result of something that has been modified in the ART settings on anything passed 1/18 in Vanir and LiquidSmooth rom.

As for Sabermod vs Linaro, it's kind of a personal preference thing. I as well as a few others here have noticed a slight advantage on how smooth performance is with Linaro 4.7 over Sabermod. Not to say Sabermod is a slouch in anyway. It's great as well.

Out of the two though, I prefer Linaro 4.7 as of right now.
[Samsung Galaxy Nexus] bsmitty83:
I just took a look at your project on github , looks awesome . when its finished I hope to try it out
[Samsung Galaxy Nexus] wisefreakz:
Yes if videos are 1080p
[Samsung Galaxy Nexus] demlv:
Sorry, I just have have to ask........Yes, it's a coincidence? Or yes, the kernel causes issues on YouTube?
[Samsung Galaxy Nexus] pattyboi:):
if you flashed the super ram version,then you have to reboot again and it should fix any playback problems
[Samsung Galaxy Nexus] HONG86:
Well...we are on the page 900!!!

amazing!!!

Sent from my Gnex
[Samsung Galaxy Nexus] Droiderat:
Am using SmittyV-NoMeM-5.3.14 on Maguro. Did a warm boot and ended on in a Google bootloop. Had to pull the battery, etc.

This is the first time this has happened with this build, but this activity started several builds ago (previously reported). Once the phone starts, it is fine. No unusual behavior that I am aware of.

Do Synapse settings affect a warm boot (at the Google logo stage)? A cold one?

The ROM is cm-11-20140411-NIGHTLY-maguro, which I understand to be the most recent stable build.
[Samsung Galaxy Nexus] osm0sis:
If you don't have Synapse installed it doesn't affect anything. If it were Synapse related, of all of us you'd think I'd be the one seeing the issue. :p
[Samsung Galaxy Nexus] pvkiniyan95:
bfq with rab 4096 gives me one heck of a read write speed, i hate benchmarks but i noticed extraordinary improvements when i was transferring files from my pc or usb or within the gnex..has it anything to do with that update u mentioned [MENTION=4608636]bsmitty83[/MENTION] or just that i was stuck with zen
[Samsung Galaxy Nexus] büscher:
I don't really know what happened, but yesterday I installed a new ROM (clean) built with linaro 4.9.1.

Of course I throw SmittyV 5/3 on top, set up everything and could use my phone a whole day.

In the evening I decided to install Antutu again and run a test. After completing the test my device turned black and couldn't been woken again.

I pulled battery and restarted. Everything seemed fine, but shortly after the boot my device didn't respond to inputs, showed crt animation and was dead again. Restarted and blacked out again.

I then restored my nandroid backup, but my device seemed borked. the same blackouts happened over and over...

I decided to go back to stock, that worked.

Installed the new linaro 4.9.1 rom again, also with SmittyV and started. seemed to work. began to configure and suddendly the blackouts began to happen again.

one more time back to stock...

now I just installed CM-Remix with the built in kernel and configured all my settings and apps. It works since 12 hours now.

May smittyV doesn't play nice with a rom with linaro 4.9.1 but why my nandroid backed up system (what worked great for several days now) didn't work after I restored it...?

Now I'm afraid that could happen again and I don't dare to install SmittyV again :crying:
[Samsung Galaxy Nexus] gautam_nexus:
is there a bug related to profile saving and deleting in Synapse? I am able to save the profile but when i save multiple profiles i am not able to delete them.
[Samsung Galaxy Nexus] scarcry:
I've been able to delete synapse config profiles just fine.

you have to apply the profile after choosing it before one can delete it.

I'm on latest synapse.

Mako running LS on AK Exodus kernel
[Samsung Galaxy Nexus] gautam_nexus:
Thanks! that sucks i thot you could just delete it by selecting it. i just want to get rid of those profiles which I dont use without applying them.

and also there is no way to save a profile by adding a custom name.
[Samsung Galaxy Nexus] aeroxr1:
I thought that this superam's "restriction" was only for video recording and not playback video.. I was wrong ?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Droiderat:
I do have Synapse installed. One of my questions is *when* the Synapse *settings* are implemented relative to warm boot and cold boot. For example, if the settings aren't implemented until the ROM is loaded, then the Synapse settings (however wrong) can't be a cause of my issue. If they are implemented before the kernel is loaded, then they (i.e., poorly chosen settings ... particularly undervolting) could be a possible cause of the boot loop at the Google logo (I get the Google logo; I don't reach the CM splash screen; after the Google logo, the phone vibrates and reboots).

I'm not suggesting that the Synapse *interface* is at all related to my issue.

I've been using the CM menu to initiate the warm boot. Perhaps there is a problem with the way CM interfaces with the kernel (we can blame CM for everything, can't we?) I just now turned off the phone (completely), and then restarted, and there was no issue.

FWIW, others have reported this (Google logo boot loop) as well.

---------- Post added at 12:03 PM ---------- Previous post was at 11:57 AM ----------

Use ES File Explorer (or whatever) and go to sdcard/Synapse/saved_profiles. You can then delete and/or rename.
[Samsung Galaxy Nexus] AndreiLux:
When the toast message shows up.
[Samsung Galaxy Nexus] cujo6801:
Yes you where.... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] pvkiniyan95:
i've been using smittyV with LS for a long time and also just today i too flashed CM Remix and its running with smittyV and DirtyV without any issues so may be SmittyV is good and just a little suggestion whenever i have such issues i used to lock the bootloader and unlock it again and startover :D
[Samsung Galaxy Nexus] osm0sis:
Exactly what I was going to suggest for custom names. Thanks! :)

Just remember you have to refresh the lists with "Restart Synapse" like the toasts and description says and deletion should work fine.

Synapse settings get applied when you see the toast notification and feel the vibration, after boot has completed. Can't miss it. ;)

I'm not saying the logo loop isn't a problem for some people, just that I don't think it's Synapse-related, because I used to always have the logo loop problem and I personally haven't seen it for ages. Not since the last kernel source rebase at least. :good:

Can someone point me to a video that doesn't work? I'm on DirtyV-SR and just watched the latest 1080p Spider-man Trailer no problem. :confused:
[Samsung Galaxy Nexus] ak:
bootloop

Bootloop to logo can't be related to synapse.

From my point of view may be due to (but i dont have log to check):

- mount point (ramdisk)

- dalvik optimizations (rom)

- corrupted data (fsync)
[Samsung Galaxy Nexus] metalspring:
I've had the bootloop to logo a few times and its not really possible to get a log, but I do think it is ramdisk related since it really only seems to happen on some roms but not others. Whats odd is a battery pull fixes it.

Btw, [MENTION=4544860]osm0sis[/MENTION], does the dirtyv ramdisk still include the aosp heathd binary? Maybe that could be the issue somehow
[Samsung Galaxy Nexus] ak:
Sometimes, when bootloop, you can do adb shell and collect directly dmesg or logcat,

even if the boot is not complete.
[Samsung Galaxy Nexus] Alkemix:
Is very likely to be the ramdisk ... I had a similar problem by omsosis's 2.0 ramdisk (extrapolated from dirty-V) and I wanted to give it a try .. I used the ramdisk (1.0) by @ Koush and kernel runs on all roms that previously did not work (bootloop) ...

maybe fstab file into patch folder ?
[Samsung Galaxy Nexus] ak:
maybe ... from my point of view. when I developed the kernel for tuna I had seen similar problems and had reported the status of the fstab file to the original after a lot of tests.
[Samsung Galaxy Nexus] metalspring:
I think the roms that have issues are heavily cm based and cm hasnt done anything to fstab, however they have changed the some other ramdisk things within the past month or so, and they also updated the sepolicy files

List of the recent ramdisk changes cm has made that may be causing an issue if the dirtyv ramdisk wasnt updated for them-

https://github.com/CyanogenMod/android_system_core/commit/b10c52080780119c0f3aa92f14153f4536642e9a

https://github.com/CyanogenMod/android_system_core/commit/c8fb65c20f7af90eca0537c874322f7becdd88af

https://github.com/CyanogenMod/android_system_core/commit/dfe31f9bb948f838d27cc5b4c367481867b4ce13

https://github.com/CyanogenMod/android_system_core/commit/7b1b96e67dba60284c7d7d1728344765413fe002

https://github.com/CyanogenMod/android_system_core/commit/d8b8cfa2c58fb70a3481b8df307cd580b6b4d706

https://github.com/CyanogenMod/android_system_core/commit/6cc5150c33ca20ed2d821e0ccb59fb1cd2567411

https://github.com/CyanogenMod/android_system_core/commit/3f2d22254512a09f8f9319f5f3fdebc9d46bae16

SE changes-

https://github.com/CyanogenMod/android_vendor_cm/commit/d3827c4f4170f7b647d776f1901e2422ab8adcca

https://github.com/CyanogenMod/android_vendor_cm/commit/002b4f0a4f2579e1ff96244ba3804ce0729a9810

https://github.com/CyanogenMod/android_vendor_cm/commit/58154f365c527a1cf687693bb339b3fc62b5ecc7
[Samsung Galaxy Nexus] osm0sis:
CM everything except AOSP charger binary. Possibly could be that? I straight up hate the percentage overlay in CM's. Did the latest round of logo loops start with 4.20.14? That was my ramdisk rebase using CM's latest. I could try reverting to the charger from before that, but then it won't be current with the other files, so I'd imagine could cause other problems... I'd be happier if we had a log to go from first.

Only way to grab a log would be to catch the loop with the bootloader key combo and then fastboot flash a different kernel that'll boot the first time. There should be a useful last_kmsg that way.

You're talking about AnyKernel. Totally different set is issues. :)
[Samsung Galaxy Nexus] aosp:
Can you link me the source code for dirty fancy please?

[KERNEL][universale: 4.2.x-4.4.x] dirty fancy kernel http://www.androidiani.com/forum/showthread.php?t=397610

[MENTION=3685904]ak[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] [MENTION=5380162]pattyboi:)[/MENTION] [MENTION=2088054]jhonnyx[/MENTION] [MENTION=4615478]boype[/MENTION]
[Samsung Galaxy Nexus] pvkiniyan95:
y no dirty fancy up in xda :silly:
[Samsung Galaxy Nexus] metalspring:
;)

This is why any and all kernels need to have up to date source code published- http://www.gnu.org/copyleft/gpl.html
[Samsung Galaxy Nexus] büscher:
Yep, thats what I had to do twice...

Also my setup with smittyV worked great for nearly one day until I decided to install that piece of crap-app antutu...

So I may just give you the advice not to install antutu [emoji12]

Will try it again with smittyV, with the original kernel from cm-remix the system is stable.

edit: baaaaaad idea....
[Samsung Galaxy Nexus] osm0sis:
I just wanted to share this because it cracked me up.

Entire conversation. :laugh:
[Samsung Galaxy Nexus] aeroxr1:
what's the meaning of "yes you where" ? i'm italian and my english is bad... :(

Last night no video work , but after a reboot everything was OK !

But on youtube app there is only hd - no hd settings and therefore I don't know if the video was or wasn't 1080p :confused:
[Samsung Galaxy Nexus] osm0sis:
He meant "were". Don't worry. He's American and his English is bad. :p
[Samsung Galaxy Nexus] pianistaPL:
Lol :D

Btw On latest DirtyV RSR i had video playback problems as well but i never had these problem before. On all Dirtyv RSR and even Mpokang SR.

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] pvkiniyan95:
uninstalled that crap months ago.....better get back to LS if u want enjoy the sweetness of SmittyV, personally i feel there are no big differences between LS and CM Remix except for the fact of organisation of settings and sorce base...both with linaro 4.9,

and i also heard that LS guys started working on Linaro 4.10.....today was my ROM hoping day and settled with CM Remix but guess what i m going back to LS in few hours....:p:p:p
[Samsung Galaxy Nexus] büscher:
The things that hold me back at CM-Remix are:

- PA PIE with chevron targets

- Wakelock blocker

- App Circle Bar

Last time I checked LS didn't have these features... does it now?

Don't want to go trough the whole setup again just to find out that the features are not there... did 3 clean installs in 24 hours now...
[Samsung Galaxy Nexus] pvkiniyan95:
link for Franco Kernel r396 optimized by metalspring please :highfive:
[Samsung Galaxy Nexus] pianistaPL:
Guys, please ask [MENTION=4328678]metalspring[/MENTION] if he's ok with that :D

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] osm0sis:
Maybe also ask in the Franco thread, not the Dirty V thread??
[Samsung Galaxy Nexus] pianistaPL:
That's right ;)

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] pvkiniyan95:
my bad...sorry :eek:
[Samsung Galaxy Nexus] michierusama:
Im having the set on boot bootloop on paranoid android 4.3 beta 2 and 3. Settings takes a little longer to set than on other ROMs I tried and when the phone sleeps the phone restarts. And then a dirty shutdown advice is showed. Latest Smitty and paranoid android. Didn't happen on CM11 M5 or M6.
[Samsung Galaxy Nexus] Droiderat:
I first noticed it on the build of 4.24 (which is the first ROM I installed after 20 April, so it would be the first ROM I tried that incorporated your ramdisk rebase). I've been using cm-11-20140411-NIGHTLY-maguro since 11 April; no changes there.
[Samsung Galaxy Nexus] osm0sis:
CM device framework for tuna works around the CAB reboot bug by forcing the screen to stay on for the first minute or two following boot. Perhaps AOSPA doesn't have that fix in. Totally different thing from the boot logo loop we're discussing though. :)

Generally the fix has always been to either set CAB during boot with an init.d script, or make sure you unlock your screen after it boots so that the bug doesn't trigger.

Okay. Would you be willing to make a nandroid and use a CM build from after 4.20.14 to see if it's still a problem? Perhaps because you're using an old build the ramdisk files are actually too new for you.

Also, since you seem to be the guy who can reproduce the issue best, can you please try to grab a log using the exact method I described a page or so ago? That'd help a lot. Thanks!
[Samsung Galaxy Nexus] cujo6801:
Um yup..

I are smart

Me got um pubic edimacation.

Sent from the "DOG" pound
[Samsung Galaxy Nexus] osm0sis:
Hahaha. Pubic. :D
[Samsung Galaxy Nexus] aosp:
[MENTION=2853378]Nephilim[/MENTION]
[Samsung Galaxy Nexus] michierusama:
I got so lost...because I don't understand most of this...but that's what I do when it boots. Leave the screen awake.

So how Can I edit that script to make it stop with the reboots... thanks.
[Samsung Galaxy Nexus] osm0sis:
Grab my 900colorsettings script from "My GN Settings" link. It disables CAB, so should do the trick for you. :good:
[Samsung Galaxy Nexus] poo706:
Is it this line specifically?

echo 0 > /sys/class/backlight/s6e8aa0/acl_set;

[poo]
[Samsung Galaxy Nexus] michierusama:
Ok I have the script txt file and whats next... Thanks
[Samsung Galaxy Nexus] osm0sis:
Yup.

Explained in the post you downloaded it from. :good:
[Samsung Galaxy Nexus] aeroxr1:
The problem on video playback reappear , all of the vevo app's video doesn't work .. One of this is "Calvin Harris - summer" .

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] michierusama:
Thanks for all your help. Your fix worked for me on Paranoid Android. Now I can reboot and let it settle without worrying. And sorry I didn't read the whole post first I was working and in a rush. Thank you very much.
[Samsung Galaxy Nexus] osm0sis:
Works here. :confused:

No worries. I'll see if there's a way in the source to set it off by default for us all. :good:
[Samsung Galaxy Nexus] aeroxr1:
I flashed dirty 5 bigmen and now all video perfectly works :D :victory: :confused:
[Samsung Galaxy Nexus] michierusama:
If you are worried about video playback just install smittyV and all good.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] I think this is it?

drivers/video/omap2/displays/panel-s6e8aa0.c:

1661 s6->acl_enable = true;

Worth a shot to see what happens at least. :good:
[Samsung Galaxy Nexus] bsmitty83:
Yup , I believe so . switching to false disables cab by default . I knew it was lurking somewhere in the display , but I kept thinking it was in the atmel files

Sad thing is , I had used that commit previously for my old kernel , but somehow couldn't find the commit .
[Samsung Galaxy Nexus] michierusama:
This kernel was a charmander and now its a charizard lol
[Samsung Galaxy Nexus] Nephilim:
You're forgetting that the Gnex has a native resolution of 720p meaning it's 100% impossible to view a video in 1080p on it. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] ashclepdia:
Well..not impossible... Just would rescale the video to fit 720 instead :p

If it was impossible, then watching video you recorded WITH the device just wouldn't work..

Ahh semantics yay! :p

(I know what ya mean..I'm just being a SmittyAss(
[Samsung Galaxy Nexus] milojoseph:
man this rom plus the new rom resurrection is so fast... im using 1200 as max frequency and it is still to much. Lmfao how is that possible :D XD
[Samsung Galaxy Nexus] osm0sis:
There might be something to the fsync idea...

[MENTION=5523756]Droiderat[/MENTION]

I actually just managed to recreate the bootloop by f*cking around with the Core voltages. I set 153 MHz too low (825), had a nice pixel party freeze, and then it auto-rebooted to the logo loop. Now it happens after many of my reboots.

Tried my method which usually works for pulling logs by triggering the bootloader and fastboot booting a different kernel, but it only gave me a weird partial last_kmsg from the boot before the loop. Still experimenting to see if going back to my old faithful settings resolves it, or if it's permanent from some data corruption.

I've always thought Dynamic Fsync was kind of a sh*tty idea; it protects from SOD data loss, but a lot of freezes and reboots are screen-on, so you're left completely unprotected..
[Samsung Galaxy Nexus] metalspring:
Unfortunately I have dynamic fsync off and have had it off to prevent any data corruption and still have the reboot issue, I'm leaning towards either the recent adb changes cm (and consequently many other roms) did, or the charger.c changes cm did (which I believe is a part of healthd).

FYI, it does seem odd a battery pull usually fixes the bootlogo bootloop though, which is why I'm leaning towards healthd binary being the issue
[Samsung Galaxy Nexus] osm0sis:
I might revert just the binaries to those of my previous ramdisk base to see what that gets us. Really freaking weird that I hadn't experienced the recent logo loops before the undervolting freeze though, which is what had me thinking data corruption. :(

Triggering the bootloader and fastboot flashing/booting a different kernel or even just booting to recovery and rebooting to system from there also work and avoid a battery pull. :good: :)
[Samsung Galaxy Nexus] metalspring:
I think data corruption can also cause that issue too, no idea why, but it is what kinda forced me to flash a new rom after running my old one for like 2 months lol. (and same older version of dirtyv as well so it most likely was unrelated to the issues others are having now)
[Samsung Galaxy Nexus] Unzitron:
[MENTION=3317173]büscher[/MENTION], what do you min free values translate to in trickster/synapse?
[Samsung Galaxy Nexus] ashclepdia:
We also have to be willing to think though that the same result of the logo bootloop might not necessarily be restricted to only ONE cause ;)

There could be multiple things that in themselves could need multiple factors to be 'just right' to create conditions for the loop to happen.

Which is what I'm thinking, since it just seems TOO random that people using entirely different setups have reported it. I personally haven't. (I haven't had this issue since using mpokang, and even then would only happen if I did a battery pull, without powering down properly first. Whether fsync enabled or disabled even) so I'm gonna go knock on wood now lol.

(I HAVE had it happen what seemed randomly also in the past, even before dirty was ever released...maybe its just the Gnex decides it hates you right now and wants to make you anxious lol!)
[Samsung Galaxy Nexus] osm0sis:
Divide by 256 pages. :)

Gah.. Here's hoping.. My most recent nandroid was last week. :mad:

That'll teach me for dragging my feet on testing your f.K test builds with the reverted SELinux commits. :p
[Samsung Galaxy Nexus] metalspring:
Btw, [MENTION=4608636]bsmitty83[/MENTION] you ever try xubuntu instead of regular Ubuntu? I know it's supposed to be lighter on resources and was just thinking that might help speed up compilation times (at least for ROMs anyway). Plus unity desktop is kinda boring for me lol. Or what about Linux mint (which is based off Ubuntu)?
[Samsung Galaxy Nexus] Unzitron:
10, 20, 100, 120, 95, 195? Right?
[Samsung Galaxy Nexus] bsmitty83:
Yea , I've used it before , not bad , but I use regular Ubuntu 14.04 , I use unity tweak tools to theme , and that's about it . if you don't like unity , there's KDE , GNOME ([emoji106]) , LXDE too .

Personally I hate mint . dunno why , I just don't like it . i keep Kali Linux on a thumb drive for "pentesting" [emoji6]

There are so many flavors of Linux you can find .
[Samsung Galaxy Nexus] metalspring:
Yeah, it's too bad my favorite distro isn't good to develop android on lol, I always loved openSUSE. As for desktops I prefer KDE myself (almost too many options in it).
[Samsung Galaxy Nexus] büscher:
Divide the values by 256 then you get the ones you can set in trickster.

Thay are still from WaveDashHog as I'm a little confused on which to use on current lmk and also because they still work great imo.

---------- Post added at 07:11 AM ---------- Previous post was at 07:10 AM ----------

Right :good:
[Samsung Galaxy Nexus] büscher:
My phone behaves really weird lately...

With smittyV my phone always blacks out. If I enable CAB it blacks out shortly after boot.

Also yesterday my phone somehow lost its partition table. I wasn't even able to access recovery. Had to flash boot.img and recovery.img with fastboot. Then access recovery and dirtyflash my rom to start it again.

could this be related to the CM commits you were discussing?
[Samsung Galaxy Nexus] aeroxr1:
Dirty bigmem and dirty super RAM is equal right ? Super RAM only has more free RAM ?

Because with super RAM except for the playback video everything else go well , with bigmem after one days some lag appears and the nexus become inusable for some minutes .. I'm on vanir 3-5-2014 and I saved all log with syslog because I don't know to create log wothout syslog :/

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] thagringo:
at least with the last release every time i try to set ( or unset) bfq io sched on synapse, system freezes for a while and reboots afterwards.

other than that it works just fine for me. This synapse thing is quite cool actually, first time user here.

cheers
[Samsung Galaxy Nexus] Nephilim:
Downscaling means it is downscaled to 720p, hence it is impossible to view a video on the Galaxy Nexus in 1080p as I just said. The semantics change nothing the video will never be displayed in 1080p on our device, it is 100% impossible because the Gnex screen does not support anything above 720p. ;)

The cameras recording capabilities CANNOT change the Gnex's screen resolution, that is hardware not software.

Sent from my Android 4.4.2 Galaxy Nexus