yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] swo0sh:
hey, only the 1,3 ghz kernels work for me but i cant find them in UL-Voltage, it would be nice if you could update this. and how could i trubleshoot the boot-fails with 1.4GHZ kernels? yy logcat, but which infos would be intressting in the log? would be nice if they work

---------- Post added at 10:39 AM ---------- Previous post was at 10:33 AM ----------

and do you experience the same problems like me if i boot with usb-connected my xt894 loops, without connected usb it starts fine. i can fix it with a fastboot flash but after this kernel updates again it will bootloop with usb-connected.
[Motorola Droid 4] jul515:
Thank you for the additional suggestions. Unfortunately, I'm still unable to generate the desired logcat report. Debugging is enabled, USB connection type of PTP is selected (manually changed from the default of "Charging only"), the trust this PC box is checked, my device shows as attached in response to the "adb devices" command, and a lengthy logcat report is generated with the "adb logcat" command. When I then reboot, this active logcat session is terminated, and the adb logcat command (again initiated during Safestrap) simply indicates "waiting for device" throughout the entire boot sequence. This appears related to the default USB connection behavior in Marshmallow. Whenever I reboot, the previously selected USB connection type (PTP) does not stick, but always returns to the default "Charging". As a result, my device is no longer "attached" during reboot, due to the changed USB connection type. Unless that limitation can be overcome, it does not appear that a logcat report can be obtained during the reboot/bootloop sequence after flashing the SDSwap. Thanks again for all your help on this.
[Motorola Droid 4] Edinho376:
There are many kernel options. I got a umts_spyder and i'm using Mokee 6.0.1

What kernel should i use?
[Motorola Droid 4] swo0sh:
jo edinho, i would try the full scale 1.4 ghz kernels, first ULV, then LV, then HV, if they dont work try the 1.3 ghz kernels. the special permissive kernel is for special use, not for you. dont forgett a full backup, they may not work for you at all cuz of your AOSP. the kernels here are made for C-yanogen_M-od specially CM-Version 13 (Android 6.0 Marshmallow), but maybe your lucky
[Motorola Droid 4] joojoobee666:
The "Mode" doesn't matter if debugging is enabled properly. You can get debug data no matter what the mode is; I normally leave mine in charging mode and have no issues. Maybe just try running the adb logcat command once you see the CM boot animation instead of it having to wait on the device? :confused:
[Motorola Droid 4] joojoobee666:
The 1.3 kernels only have one voltage level. That level was chosen due to it's stability in pretty much every device. Regarding troubleshooting the 1.4? Don't bother. You'd need a serial debugger and a special kernel with debugging enabled to get the logs, however the info obtained would be useless. The problem is basic: the SOC is running beyond it's means. You would most likely see different crashes every boot or an at minimum it would crash in 5-10 different ways, depending on the mood. The bottom line is that the 1.4 overclocking on your SOC is causing the main CPU to return erroneous data; data the kernel is NOT expecting.:eek:

No boot issues with USB connected here, that issue there COULD benefit from some kernel debugging. :)
[Motorola Droid 4] jul515:
Thanks joojoobee666. I appreciate your assistance and patience. With the above information I tried debugging on a different computer, and it worked(!), as you indicated, even when the USB connection was "Charging". After flashing the SDSwap, a very large logcat report was generated, which continued to grow as my Droid Razr went through the boot sequence, then optimized apps, then indicated it was starting apps, at which point the boot sequence started over again. Is there a particular part of this huge logcat report that is the most useful? Could I repeat the logcat using only the E (error) attribute rather than the entire Verbose report? I'll try to send you the needed debugging information.
[Motorola Droid 4] joojoobee666:
The whole log wouldn't hurt. If you are worried about any sensitive information, you can just grab the last few hundred lines before the reboot occurs or PM me the entire log. You may want to scrub it as well. It's possible your phone number could be in it.
[Motorola Droid 4] chuchipando:
FYI. theres an update to the OMAP4 kernel in the 05/02 nightly. https://review.cyanogenmod.org/#/c/142702
[Motorola Droid 4] Bobcus Leper:
It looks like it only fixes compiling errors on Ubuntu 16.04.:(
[Motorola Droid 4] joojoobee666:
Thanks, but I was actually the one that pointed out the compile issue to stargo, however that's all it is, a compilation fix, no change to the kernel.

Unrelated, there will most likely be a new kernel later today or tomorrow containing around 170 fixes (212 for the stock kernel) so be on the lookout.;)
[Motorola Droid 4] joojoobee666:
Hey all, updates are in. A slightly early Cinco De Mayo present. ;)
[Motorola Droid 4] frankonia:
Any progress at SD-Swap?
[Motorola Droid 4] joojoobee666:
None yet. I do have a log file I am reviewing. Hoping to find something to point me in the right direction.:fingers-crossed:
[Motorola Droid 4] joojoobee666:
Ok, I made a few changes to the SDSwap here. Anyone having issues want to try this and let me know? Also, a logcat of boot would be great if the issue persists using the following (linux only):

adb logcat | grep -i 'vold\|mount' > logfilename.txt

Let me know how it goes. :good:

Update: Main post updated with new SDSwap zip/link.
[Motorola Droid 4] frankonia:
Oh, great news! - I just update my system from the mid-february Resurrection-build to the latest from 01-05/2016 with SDSwap.

Update:

As expected everything with SDSwap is working fine.
[Motorola Droid 4] NAYBER:
I can also confirm that SDSwap appears to be working fine on Droid 4 also. Stock Rom slot, CM13 Nightly 5-6-2016, OC Kernel 5-3-2016 ULV, SDSwap 5-5-16, OpenGapps 6.0 pico 5-7-2016, Holo Launcher Pro Marshmallow. Thx so very much! Like a brand new phone!
[Motorola Droid 4] joojoobee666:
Hey all, just an FYI that the kernel was updated again. Just syncing to upstream, 11 more patches. :silly:
[Motorola Droid 4] joojoobee666:
One more patch, so a new kernel up. Nothing major though, just a really specific USB security patch. :good:
[Motorola Droid 4] joojoobee666:
Hey all. 6 new patches so new kernels up. As usual, check the first post for details and links. :cool:
[Motorola Droid 4] EclipsedDK:
Loving the 5/17 update. Things are a lot more stable and still behaving as a fresh boot even though it has almost been a week since my last reboot. :D:good:
[Motorola Droid 4] giannhs_n:
i am new Droid user, i am wondering if i can flash cm13 on stock partition for better performance(when i try it phone did not boot) , thanks
[Motorola Droid 4] Bobcus Leper:
There isn't any performance difference, unfortunately. With that said, I would flash CM13 to the stock slot to save internal storage space.
[Motorola Droid 4] giannhs_n:
i understand... i try to do more space with the following way too

mount mmkblk01p24* -o ext3 rw,blablabla witch is the stock partition but for some reason (maybe cm13 security) i cant execute any file i only can read write , any suggestions for that?
[Motorola Droid 4] Bobcus Leper:
Hmmm... I have never used terminal commands to mount the stock partition. I use safestrap to mount the partitions. One the stock slot has been loaded up, I wipe system, data, cache, and dalvik-cache. After that I install the ROM and Gapps as usual.

Cheers!:good:
[Motorola Droid 4] giannhs_n:
i see... anyway i ended up with cm12 i find it ways faster than cm13

cheers ?
[Motorola Droid 4] joojoobee666:
Hey guys, small update so new kernels up. Just wanted to let you all know.:good:
[Motorola Droid 4] joojoobee666:
SDSwap updated today to reflect some of the performances changes that were added last night. Those not using SDSwap just install the latest nightly to get them. So far, I've noticed some slight increases with the device with no negative side-effects. :good:
[Motorola Droid 4] joojoobee666:
Hey all, new kernels up. Just a patch for KSM (Kernel Same-page Merging). :cool:
[Motorola Droid 4] joojoobee666:
Hey guys, more new kernels up . These are just updates to include the latest security patches. :D
[Motorola Droid 4] joojoobee666:
Hey all, another update. Again, just a couple security fixes. :good:
[Motorola Droid 4] Careless_:
so whats the reason for the SELinux permissive kernel, again?
[Motorola Droid 4] joojoobee666:
This is needed to enabled init.d support which some apps needed or still need like Chainfire's LiveBoot or App2SD (which may or may not require it anymore).
[Motorola Droid 4] Careless_:
would you say it's a better idea to install that one, and also- why no ULV?

btw, installed the regular Full Scale ULV kernel yesterday. it's doin pretty well. nice work!
[Motorola Droid 4] joojoobee666:
Generally speaking, it's NOT a better idea; less secure. Also, there should be very few circumstances where it's needed. I like to do a lot of tweaks and such in my own personal cm13 builds and have never needed permissive.

This same reasoning can be used to explain why there aren't any other permissive versions. This was a special request from one user for that particular kernel and I've received no others. However, should you find yourself needing a ULV full scale with SELinux inpermissive mode, I'll happily build one for you.:good:
[Motorola Droid 4] Careless_:
well in that case, save your time! I think i'll stick with full scale ULV <3

im wondering though, i never had a chance to test with the stock kernel, but when I have an incoming call if I reach for the phone the screen goes black for some reason.

subsequently, if i try to hang up, taking the phone away from my ear and pressing the power button to have the screen come back on takes ages before it actually turns on again.

kernel or latest nightly issue? im not sure myself.
[Motorola Droid 4] 3of12:
The sleep issue has been a thing on CM for years, it happens when the cpu won't kick up to the clocks required to wake up quickly. Try changing governors.
[Motorola Droid 4] Careless_:
I know. it happened on my Desire Z, but it wasn't happening on the build before the one I'm currently using. I was wondering if the kernel had anything to do with it.
[Motorola Droid 4] joojoobee666:
I've seen this as well. Not a kernel issue, it's usually a RAM issue. If you are using ANY browser, make sure you actually close it down when you are done. I've tried playing around with the OOM and the LowMemKiller settings but nothing seems to appease. From what I gathered, when RAM is low, the phone processes end up getting killed, regardless of the fact that they are set for a VERY high priority regarding RAM. So a call comes in, it needs to start those processes up but has to kill off tasks before it can fire up the phone processes. This takes a small amount of time. Once they are killed, the phone processes start....and this takes even MORE time. It's possible to completely miss an incoming call when this happens; I know as it's happened to me many times. The phone rings but the screen never comes on in time to actually answer. I attribute this to 3 things:

Old-ass device

1GB RAM

CM12 and 13 telephony are pigs

Again, keep any apps that are huge mem users closed when not in use. Browsers (Chrome, stock or Firefox) being the biggest culprits. Sadly, it's NOT a kernel issue. The OC helps but clearly not enough.
[Motorola Droid 4] Careless_:
I don't disagree with what you're stating, but I DID mention that it did not happen with the previous build CM13 nightly (3-26, I believe) and I only noticed it starting to happen again after going to a later build- in conjunction with this kernel. I'm not saying it's the culprit.

Like i said, I have had underpowered devices. In fact all of my phones have been underpowered because I want to utilize a physical QWERTY keyboard, and thus I have to make a compromise where performance is concerned in order to retain the keyboards that I like.

I was just inquiring if there is some sort of setting that alleviates the issue which is specific to this kernel, using Kernel Aduitor- or perhaps a better governer to use.

I do not do these tests with any program in the background. In fact, I close every program as soon as I'm done with it. I don't have any BG processes. I almost never do. That's just how I use my phone. The background processes are minimal at all times.

So it's probably the CM nightly introducing something in the overhead. I'll have to experiment.

Thanks for your hard work.
[Motorola Droid 4] 3of12:
This is why I'm perplexed that they dropped the stock clocks from 1.2 down to 1.0GHz for targa from CM11 to CM13 at whatever point. They get really conservative with performance settings and now have just removed them completely. Why didn't they just take the work of project sense and JBX and make an overclock capable kernel? Nope... lets run the bottom clocks even on REV A! Its as if they do zero usage testing, targa has never been functional on CM without overclocking and voltage options but they keep fighting it.
[Motorola Droid 4] stargo:
What are you talking about? targa is running at 1.2GHz on CM13.

Regards,

Michael, who has spent months of unpaid time to just keep the OMAP4s current on CM. Even with usage testing.
[Motorola Droid 4] Septfox:
Welp, went and ran CM11 for a bit...I now more deeply appreciate the work that went into making Marshmallow not be a juttery mess, and stargo's efforts to make it so we see as much as that smoothness as possible on our aged hardware.

[MENTION=1070688]joojoobee666[/MENTION]

May I bother you for a stock+1.3ghz kernel set to permissive? Since I'm going all clean-slate, it makes sense at this point to make a partition and get Link2SD up and running, which as I understand requires such (due to init.d).

Also, regarding this:

Have you tried turning on the "Home button answers incoming call" option in Settings>Buttons? I was having trouble with the in-call interface and lockscreen coming up simultaneously when a call woke the screen, and neither responding to touch input; turning the option on allowed me to bypass the issue the next time it popped up. Since the touch buttons are technically hardware buttons(?), perhaps it'd work while the screen is still blanked as well.
[Motorola Droid 4] u.b.o.o.t:
I'm also facing many lags and tried many things without success (increasing over-provisioning to 100, increasing/decreasing Swappiness, trying different gouvernors and I/O schedulers, etc.). To me it seems that I/O is causing some of the lags and it seemed to be less when I had CM13 installed on native partitions via Safeslot which unfortunately does not work anymore. Installing on loop-device seems to cause additional overhead / slow down I/O due to block-misalignment, etc. But I'm still not convinced about that and I suspect it is also a RAM issue and I'm not sure if zRAM is a curse or blessing here.

If there was a way to recover safely if something goes wrong, I would install CM13 on stock slot.

f2fs instead of ext3 should also considerably increase I/O throughput (random 4k), but it's not supported by 3.0 kernel.

But on my Xperia Pro I remember that there was a bug in low-memory-Killer which prevented phone app from staying in memory. If there is a similar issue on the Droid4, I might get fixed somewhen....

Also, I consider trying putting Android into low-ram-device-mode via build.prop. This would instruct certain apps to use less memory (provided that the app-developers care about low-ram-devices).
[Motorola Droid 4] joojoobee666:
Indeed. I'll get everything setup here and maybe have it for you later today. :good:
[Motorola Droid 4] joojoobee666:
Give this a go. Tested fine here. Let me know if you're satisfied and I'll make sure it stays in any upcoming updates. :good:

Nope, but I enabled it to give it a go.:silly:
[Motorola Droid 4] joojoobee666:
It's not my thread, it's the community's. Anyhow, I thought it was well rounded and contained information others may find useful. Thanks.:good:
[Motorola Droid 4] chuchipando:
The red/blue color bug is still there, even without the low_ram flag enabled (or at least I didnt see it anywhere in the build.prop. or am I looking in the wrong place?). I tried getting some screenshots but curiously they come out in the correct colors. the bug is 100% reproducible on the XDA Labs app in the wallpapers section. I'm on cyanogenmod nightlies and update daily as long as an update comes out. The only difference is on on a droid razr xt912, but still the same innards as a droid 4. I hope stargo can take a look at that. I always get so exited to see OMAP4 fixed in the CM changelog. and then come straight here for the updated kernel. :D thank you stargo and joojoobee666. :good::good:
[Motorola Droid 4] Septfox:
The flag was added as a supplement for extremely low-memory devices (512mb according to the documentation; I can't even imagine how painful it'd be to run MM on 512mb of memory unless it's really fast memory), so it defaults to disabled and won't already be in build.prop unless specifically added before the ROM is compiled. Gotta edit it in yourself if you want to try it, just stick it at the bottom under all the other stuff; ro.config.low_ram=true

And, yea. It's not that the colors actually change, it's how they get rendered on the way to the screen that gets changed. Another reliable way to check for it is the Youtube app while playing a video; it pops for me nearly every time when rotating the screen from landscape to portrait.
[Motorola Droid 4] joojoobee666:
So yeah, didn't help. I left the AccuWeather app open (it's a ****ing pig) and got a call but the screen never lit up. Hit the home button, but...nope; missed the call. :eek:
[Motorola Droid 4] u.b.o.o.t:
[MENTION=1070688]joojoobee666[/MENTION]: thank's for trying lowmem-mode. On my 512MB RAM Xperia Pro with CM13 it was definitely enabled and there definitely also was transparency.

Regarding OOM-killer - I set it to "very aggressive" via kernel adiutor -> free mem stays above 200MB most of the time now and everything feels snappier. Does not seem to be _too_ aggressive for me, but maybe it could be relaxed.
[Motorola Droid 4] Septfox:
[MENTION=1070688]joojoobee666[/MENTION], the kernel works perfectly, init.d came right up after I updated from 2016-03-02 (yes, really) and flashed it. Now if only I could find my card reader, Safestrap really doesn't like being host to SD card partition juggling...

Unfortunately, the same can't be said for my battery gauge after updating; something appears to have gotten broken, and it's back to the infamous Motorola 10% increments. Still trying to figure out if that's due to my SNAFU of a configuration or an actual bug in latest nightlies, but I suspect the latter due to doing it even after the phone was cleanly SBF'd (and being "fixed" when switching back to my much older nightly). Noticed anything yourself?

Edit: newest nightlies also "fix" cLock (by adding another memory-eating service to handle...yay...), so you could use that for weather. If you want a full-sized weather app, Transparent Weather Clock - at least, the old version I have that I haven't updated in months - is reasonably lightweight and gives more information than you'd ever want, or on the more simplistic end of things Weather (by MacroPinch) is lightweight, looks nice, is straight to the point.

[MENTION=309785]u.b.o.o.t[/MENTION]

If it's not already disabled, also try turning Z-RAM off (reducing the size to 0). It can work with decent speed if set to huge amounts, for some reason, but having it on period causes more CPU usage and memory thrashing, neither of which we can really afford. I think it's already shut off in nightlies these days - seems like I saw a commit to this effect a while back - but you may want to check and make sure.

And as usual, disabling services and such will keep more memory readily available, reducing the need to wait for the LMK to politely ask said services to shut themselves down. Someone really should write a mini-guide on which things to disable, how, and the consequences of each. Hmm.
[Motorola Droid 4] u.b.o.o.t:
[MENTION=5521404]Septfox[/MENTION]: I'm not sure about zram. Swapping an already initialized and loaded app back to RAM should be faster than booting up an app from disk IMHO. And on the Droid4, zram runs with 2 threads.

And Stargo recently _increased_ zram to 400MB and swappiness to 100:

http://xdaforums.com/showpost.php?p=67372270&postcount=361

http://xdaforums.com/showpost.php?p=67410788&postcount=365

I have ds.cpuoverlay running to monitor cpu usage and I/O utilization. During lags I face almost always a high amount of I/O. I credited that with flash access because it maxes out at 25MB/s which seems way too slow for zram....

I expect zram to achieve hundrets of MB/s throughput.

Am I wrong?
[Motorola Droid 4] Careless_:
[deleted]

not pertinent to this thread. mistake post.
[Motorola Droid 4] joojoobee666:
Indeed, it was due to the introduction of the new cm charger-mode (which our sh*tty Omap4's don't support). This caused healthd to revert back to the moto blob for battery stats. However, thanks to [MENTION=3457922]stargo[/MENTION], a fix has been pushed and the 1% increments will return on the next nightly. :D
[Motorola Droid 4] Bobcus Leper:
On reading up in the Galaxy Nexus forums, I saw that the TI-OMAP 4 was not supported in AOSP Lollipop and above. Is this why our OMAP phones perform poorly on ART based ROMs, while ROMs using the dalvik compiler are smoother? In AOSP Nougat, the Snapdragon 800 and 801 chips using the Adreno 330 GPU are no longer supported as well. I guess my question is if it will it be possible to reverse engineer OMAP-4 drivers for Nougat that can support the new surface view texture renderer?
[Nexus 6P Q&A, Help & Troubleshooting] Karlo666:
I have tryed to find out what app does this.Even disabled Sync and still Screen Off takes more battery then Screen On

Anybody have clue?

http://i.imgur.com/2OjxF1q.png
[Nexus 6P Q&A, Help & Troubleshooting] SpookyTunes:
BetterBatteryStats:

http://xdaforums.com/showthread.php?t=1179809
[AT&T Samsung Galaxy S6] Rooster82:
Does anyone know how to root the lollipop 5.0.2. Any help would be appreciated
[AT&T Samsung Galaxy S6] dandrumheller:
Which build number. If OF3 or later, it's not possible. If prior to OF3, then ping-pong root.

Edit : disregard, reading too quickly I missed that this was for an active. Don't think it's possible.
[One (M8) Q&A, Help & Troubleshooting] roarcrm:
Hello,

A while back I attempted to root my HTC One and I installed CyanogenMod. I've been having a few issues with various things so I attempted to do a factory reset through the settings. I'm now stuck in a boot loop 'teamwin' flashing on the screen every few seconds. I can't turn the phone off and no keys do anything.

Any ideas on how I can resolve this?

Thanks!
[One (M8) Q&A, Help & Troubleshooting] Venomtester:
Hold power and volume up until screen goes dark then quickly hold power and volume down. Then you can enter recovery and flash a rom or restore a backup.