yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] joojoobee666:
The ramdisk should extract fine on Linux using Ark. It should extract to a "ramdisk.img.uncompressed" first, then that should extract to the actual RAMdisk files/folders.

As far as SELinux, permissive would definitely help according to that log message. However, the more apt solution would be to add the correct permissions for the binary. Let me run this by [MENTION=3457922]stargo[/MENTION], he's much better at SELinux and also has the authority to make the change in the device tree on CM so this is permanent. However, in the meantime I can make you a kernel in permissive mode to test to see if that fixes. Which one do you use?

Also, [MENTION=5521404]Septfox[/MENTION], I didn't forget about the SDSwap thing, I just got swamped at work yesterday. I'll have one up for you shortly though (as long as it works).:good:
[Motorola Droid 4] joojoobee666:
Try this: http://droid.cs.fau.de/jjb666/SDSwap/test/cm-13-D4-RAZR-SDSwap-2016-02-13.zip

It shows as "ejectable" for me, hopefully that's enough to make App2SD happy. :eek:
[Motorola Droid 4] daniel_m:
I'd very much like to try out 'CM13 OC 1.4Ghz Kernel LV (Low Voltage)' with permissive SELinux :D

Regarding permissions: Would [MENTION=3457922]stargo[/MENTION] only have to add permissions for 'sysinit', or also for the busybox binary? The latter is not part of CM13 any more...
[Motorola Droid 4] joojoobee666:
As ordered: http://droid.cs.fau.de/jjb666/Kernels/tests/cm-14-OC-14LV-permissive-2016-02-13.zip

As far as permissions, I'm not sure and I don't know how easy or difficult it will be to correct them. I honestly suck ass with SELinux and the necessary changes may not happen at all, depending on what changes would need to be made. Anyhow, let's start here. If this works, then we're on the right track. Post the logs so we can see if there is anything else that would be needed.
[Motorola Droid 4] daniel_m:
Wow, that was quick! And ... it is beautiful! :D

After flashing your permissive kernel, the first thing to greet me was Chainfire's LiveBoot. Instant proof for a working init.d :laugh::victory:

The test script wrote its log to /data. And I can start restoring all my apps from CM12 with oandbackup and Link2SD.

Thanks a lot!

(I will also read up about the security risks I will run into from now on :cool: )

PS: There are some scripts, ZIPs and apps to enable init.d (with a permissive SELinux), but I can also write a small tutorial on how to do this manually. I am not a very trustful person and I like to know what is going on, instead of letting a script/app do things automatically... :p
[Motorola Droid 4] joojoobee666:
[MENTION=4885896]daniel_m[/MENTION]

Ok, I did a crash course on SELinux. ....yeah, here's the bad news: it is NOT possible to fix the policy in device tree as it is being denied via a "neverallow" in the source tree:

external/sepolicy/domain.te:

# Only recovery should be doing writes to /system
neverallow { domain -recovery } { system_file exec_type }:dir_file_class_set
{ create [B]write[/B] setattr relabelfrom append unlink link rename };

Since this is coming from source, it is not something we can override on the device tree. :(. You have two choices, sync the source and modify to allow you to add the following to init.te:

allow init system_file:file { write execute_no_trans };

or run in permissive mode. That's it, those are your options. I'll compile you a permissive kernel from here on out.

@ everyone: new kernel up, just a bug fix for fuse and a 1.4LV in permissive mode for the more adventurous.
[Motorola Droid 4] daniel_m:
Oh, but I expected as much. Life is getting more and more restricted by big companies/organisations :(

Great, thanks a lot! I hope that I am not the only one who likes to tinker with their Droid 4 and appreciate your support :D
[Motorola Droid 4] joojoobee666:
All, I pulled the kernels from today. Looks like my source folder got swapped with the stock. I'll have to fix and recompile. Won't be up until tomorrow. Sorry for the confusion. :o
[Motorola Droid 4] chuchipando:
lol, hadn't even noticed.
[Motorola Droid 4] joojoobee666:
Ok, mixup resolved. Just in the nick of time. They're all still 2016-02-13 kernels...but...well...FIXED. :D
[Motorola Droid 4] Majkus_:
Yeah I did noticed! Thanks, I was confused, what happend :D. Custom kernel, but stock frequencies, governors..

Also, I've got a problem with Whatsapp chat backup restore. When I authorize my mobile number, screen with restore is shown, backup is found, I choose restore as I always do, but during the restore process something goes wrong (it goes from 0% straight to %100 in 2 seconds..) and error message is shown. Could it be somehow kernel related? I did flashed OC 1.3 kernel. The backup is on the internal memory, so there should be no SD card related problems right?

EDIT: I did some workaround and get Whatsapp finally working. Titanium Backup and JB stock to the rescue..

Thanks in advance and for the great work on this kernel, it kicks ass!

M.
[Motorola Droid 4] Shobai:
[MENTION=1070688]joojoobee666[/MENTION],

I've just flashed the latest nightly, and your Run n Gun Lite kernel [downloaded an hour or so ago from the first post]. It looks like it might actually be one of your OC kernels in disguise, though: instead of 300Mhz, 1Ghz, 1.2Ghz and 1.3 Ghz for the frequency table I'm seeing 300Mhz, 600Mhz, 800Mhz, 1Ghz, 1.2Ghz and 1.4 Ghz. Is there any chance there's some mis-naming going on?

Thanks again for your kernel work!
[Motorola Droid 4] chuchipando:
I couldn't get my xt912 to boot after flashing the 02/13 OC Full Scale Lite 1.3Ghz. Neither on 02/12 or 02/14 cm13 builds. Interestingly enough, its kind of what happens when I tried any of the 1.4 Ghz kernels.

edit: I couldn't get my xt912. I had written could before.
[Motorola Droid 4] joojoobee666:
Hmm...strange. I'm not really sure what could have happened there. The one I checked was fine, but it wasn't the RunNGun lite. Stay tuned.

Update: Found the problem. Generating some new ones...again!
[Motorola Droid 4] joojoobee666:
Ok, new kernels up, fist post updated. I tested a few of them here myself. Everything looks like it's back to normal again. :D
[Motorola Droid 4] joojoobee666:
All, even newer kernels up. Just some fixes from upstream. Check the first post for details. :good:

Should also note that there is a new SDSwap as well.
[Motorola Droid 4] daniel_m:
[MENTION=1070688]joojoobee666[/MENTION] and [MENTION=5521404]Septfox[/MENTION], do you have an idea why CM13 wouldn't boot when the internal SD-card (mmcblk1p25) is formatted as anything else than vfat? I tried with ext2/3/4, but CM crashes early during the boot process. So early in fact, that I cannot even adb into the phone and grab the logcat. When I format mmcblk1p25 in the terminal when Android is running, Android is happily accepting ext4.

I also tried to remove mmcblk1p25 (mmc1) from fstab.mapphone_cdma, to prevent Android from getting its greedy hands on it. The modified fstab does its job when mmcblk1p25 is formatted as vfat, but does not help preventing the boot failure otherwise.
[Motorola Droid 4] Septfox:
No idea. Obviously, Android does support them, so one would think it'd run without a hitch : \

It seems like I saw someone (probably stargo) post quick instructions on how to switch one of the partitions over to ext 3/4 over in the CM13 thread, but not sure which they were talking about. Worth a quick search to see if there was an extra step to take.

I also remember seeing somewhere - I think it was in the comments for a commit, not here on the forum - that [MENTION=3457922]stargo[/MENTION] said he'd tried switching to ext 3 or 4, and it unexpectedly dragged things down badly. But I might be misremembering, he'd have to tell you either way.

[MENTION=1070688]joojoobee666[/MENTION] - I did see the non-swappy SDswap you posted, just haven't sat down and tried it out. I just ordered a doner phone to get a "new" motherboard so I can have nice things like a power button, Youtube that doesn't occasionally hard-freeze and possibly a better-binned CPU, so I'll give it a go when that arrives and I have to move stuff between storages again anyway. Thanks for spinning it up.
[Motorola Droid 4] Septfox:
[MENTION=1070688]joojoobee666[/MENTION] Did you remove the efuse offset output after your first few updates, or am I blind and am missing it?

I'm really curious as to what kind of binning this chip achieved. Can't be all that good, I guess, since it died twice @1.4/LV : |

Also, regarding either the normal SDswap or the unswap one you made,

I think something might have gone a bit wrong...

(or it could be someone on the computer side. currently flashing latest nightly without a modded RAMdisk to see)

Edit: no 1.4ghz for me, it seems.

Also wow, running Stock a few times whilst trying to sort activation out, somehow resulted in slot1's partition files getting nuked. Sure am glad I had everything backed up to PC.
[Motorola Droid 4] stargo:
Hi,

just a quick question for people running CM nightlies without modifications: do you sometime get data-drops where the phone is using data and after a time it won't reconnect without toggling airplane-mode?

This seems to be caused by rild somehow exiting (not crashing), but it is very hard to track down (and I can't reproduce it).

Thanks,

Michael
[Motorola Droid 4] joojoobee666:
Yeah, I noticed the problem with the fuse mounts on the SDSwap a month ago but hadn't figured it out, the "external" shows up twice....didn't spend too much time on it yet. As far as the efuse offset output, are you referring to the nr_value overrides? As far as I can tell they should still be getting logged, I see it in the code here. They only show up during boot so you'll need to be watching dmesg after startup.
[Motorola Droid 4] d.casper.b:
Unless it's my network provider or something (but I don't see how they'd get away with intermittent service as people would complain), but I've experienced this even prior to CM13. I usually force-switch bands which seems to help. I've always seen it as a problem when on 3G and not EDGE (but not really sure anymore).

I am on a RAZR though and perhaps this question is for droid4 users..

Sent from my Motorola RAZR Maxx (XT910)
[Motorola Droid 4] stargo:
Hi,

Hmm, this might be the same problem and now happens for more people on CM13. Does toggling airplane fix it for you, too (instead of the band-switch)?

And shame on me, posted the initial question in the wron thread. Sorry [MENTION=1070688]joojoobee666[/MENTION].

Cheers,

Michael
[Motorola Droid 4] d.casper.b:
Reply moved to post 196 here.
[Motorola Droid 4] kzin42:
Hi, just FYI, I had tried the ULV kernals on the "cm-13.0-20160127-NIGHTLY-maserati" and there were apps crashing and random reboots etc. I assumed my D4 was not up to 1.4GHz, But today I had to wipe, ( for some other reason). So I put on the "cm-13.0-20160304-NIGHTLY-maserati" and loaded the ULV Full scale Kernal straight after, and it seems to run just fine...:D
[Motorola Droid 4] Septfox:
It will, until it suddenly doesn't and will suddenly completely refuse to even entertain the idea of rebooting. Our CPU can be really touchy, it seems like the littlest things set it off even when it looks to be rock-solid stable : \

Of course, when I say "our", I except joojoobee's chip. It's braced with titanium and has been blessed by the touch of God or something.

no, i'm not slightly jealous, why do you ask

Keep an eye on it...personally I'd nip it in the bud and just flash LV, accepting the marginally worse power usage in exchange for less possibility of it dying at an important time. But that's just me and and my paranoia.
[Motorola Droid 4] kzin42:
You had to say it... it was fine all yesterday and up to lunch time today when I read your post as I was reading it opera stopped then a reboot and been crap since, LV was no different. so Have gone back to the 1.3GHz full scale.

Are there differences between the ULV and the Lite kernal that would mean screen rotation is working on the Lite but not the ULV? as thats what I have observed.
[Motorola Droid 4] joojoobee666:
LOL, I'm not complaining.

Regardless, new kernels up today. Nothing major, just syncing to upstream. :good:
[Motorola Droid 4] frankonia:
The SD-card-swapper does not work anymore with the latest CM 13.0-builds. The last one which was working, is the build from mid-february.

Used device: Motorola Razr Maxx UMTS-Spyder.
[Motorola Droid 4] frankonia:
Double post => deleted!
[Motorola Droid 4] joojoobee666:
Hmmm...interesting. Working for me here. I've got some new kernels coming shortly, I'll make a new one for you to test.
[Motorola Droid 4] Septfox:
For me as well, on the nightly from 03-02. Been too busy and lazy to unswap everything properly. Maybe some Spyder-specific commit broke it?

Was going to update today, but I saw the iovec fix in the next nightly and imagine that's what your upcoming builds are for...looks like holding off a bit longer is a good idea.
[Motorola Droid 4] joojoobee666:
Ok, updates are in, check the first post. New SDSwap as well. Flashed and tested here on D4. Let me know how it goes. :silly:
[Motorola Droid 4] joojoobee666:
Hey all, just an FYI that I posted another minor update. :good:
[Motorola Droid 4] M-A-A:
The permissive kernel doesn't work at all for me...Anyone else had any luck with it?
[Motorola Droid 4] joojoobee666:
I'll take a look at it today. Did the previous one from the 19th work ok?

Update: I've verified it's working on my device. Does the normal 1.4 LV work on your device. If not, do ANY of the 1.4s work?
[Motorola Droid 4] M-A-A:
The one from the 19th didn't work for me either. I can try one of the others.

Update: None of the 1.4 kernels worked for me.

The non-OC Run N Gun and the FullScale Lite 1.3 kernels were both able to boot.

Is there a permissive kernel available without 1.4/non-OC/etc.?
[Motorola Droid 4] frankonia:
I tried with the latest build of CM (from 22-03/2016) and SDSwap (19-03/2016), but still getting stuck in a bootloop. Nothing else was installed, also no Goggle-apps.

Device is: Motorla Razr Maxx UMTS-Spyder. I think it has something to do with the latest CM-commits for the Spyder.
[Motorola Droid 4] joojoobee666:
Which commits are you referring to? The last ones I see for the spyder and umts spyder were from Feb 6th. Everything else was to the omap4 common which d4 and spyder share. But maybe I'm just not seeing them? Of the latest ompa4 common, I see nothing that would have broken this either. Either way, I'm going to be out for the next week so I won't be able to do much in the meantime. When I get back, I'll take a look and see what options we have as far as logs and maybe enlist some additional help.
[Motorola Droid 4] frankonia:
I mean the official nightly builds of CM 13 from Cyanogenmod for the Motorola Razr (Spyder). All the other ones you are referring to, are outdated. These are the latest unofficial builds from Stargo's FTP-server, which he built at last and hosted on his own server.

Official

UMTS-Spyder

nightlies:

http://download.cyanogenmod.org/?device=umts_spyder

Official

CDMA-Spyder

nightlies:

http://download.cyanogenmod.org/?device=spyder

The

thread from Stargo

to them:

http://xdaforums.com/droid-razr/development/rom-cm13-0-marshmallow-t3270951
[Motorola Droid 4] joojoobee666:
Ok, looks like we may have some confusion around wording. :p I am referring to the actual changes to the device tree on github, from which the official CM builds are created from. Specifically, the umts spyder tree here: https://github.com/CyanogenMod/android_device_motorola_umts_spyder/commits/cm-13.0

As you can see, the last changes that were made for the umts spyder were on Feb 6th. This tree and the omap4-common device tree are "combined" during build, along with a few other items, to generate the ramdisk.img, which is where the sdswap changes are at. If any changes specific to the umts spyder would have broken that, I would expect it to be in either one of those trees. However, since nothing has changed in the umts spyder tree since Feb 6th and the changes to the omap4 common tree have not broken this for the D4 I currently at a loss as to the cause.

To clarify, this is all in reference to the following comment of yours:

Since these devices are extremely similar, I cannot currently think of any reason the SDSwap wouldn't work for spyder but works for D4, including commits outside of the device tree and in the main CM trees. If there was one that made it stop working, it SHOULD have broken it for all the omap4 (maserati, targa and spyders).

I also checked with stargo regarding this, he also couldn't see anything recently committed in the spyder, omap or CM tree that would have broken this only for umts spyder.

In the meantime, can you or anyone having issues post me the output of the following commands (as root)?

mount

cat /fstab.mapphone_cdma

ls /storage -l

Thanks for being patient. :good:
[Motorola Droid 4] 3of12:
Stuck with 1.1GHz

I'm not sure why, but I flashed the 1.4GHz full scale LV kernel, and I confirmed in about phone that its running, but I have all the cpu states up to 1100MHz only, and I cannot seem to get trickster mod to work so I am dumbfounded. I'm using a droid bionic with the st paddies CM13 snapshot :confused:
[Motorola Droid 4] Bobcus Leper:
Unfortunately, Trickster Mod is broken on CM13 and all MM ROMs. Use Kernel Auditor on the Google Play Store.
[Motorola Droid 4] 3of12:
Ok so that is working, but my problem isn't solved. Faux clock works pretty similar to this, the feature set is pretty identical other than the dark theme is actually working. :eek: I think I may try the 1.3GHz full scale and see if that takes, then I can get to 1.4 with MPU control, but missing a CPU state will take a hit to stability. Has any other user had this problem? Could it be caused by the binning on the bionic is not uniform? I have a late revision lower binned 4420, so the yield is actually of decent quality and handles 1.4 GHz with the MPU increased to 110MHz. I'd certainly prefer CPU states up to 1.4 because you get more exact voltage settings, and therefore stability.

Wish me luck with other kernels in the list. I really don't think run and gun is gonna work for me because I need power efficiency
[Motorola Droid 4] frankonia:
@ joojoobee666: I tried to do that with Android Terminal Emulator. But unfortunately I failed, because I did not type-in the commands "as root". Can you explain step by step how to come into that mode?

Edit:

I finally managed to do it. The command you have to type-in is simply "su" at first.

So, here's the dump:
[Motorola Droid 4] joojoobee666:
Here's the problem:

/devices/platform/omap/omap_hsmmc.1/mmc_host/mmc1* auto vfat defaults voldmanaged=sdcard0:25,noemulatedsd,nonremovable
/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata

should be:

/devices/platform/omap/omap_hsmmc.1/mmc_host/mmc1* auto vfat defaults voldmanaged=sdcard1:25,noemulatedsd,nonremovable
/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0* auto auto defaults voldmanaged=sdcard0:auto,encryptable=userdata

So for some reason, the zip is NOT replacing the ramdisk.img when you flash it. Can you try manually extracting the ramdisk.img from the zip and overwriting the one in /system/etc/kexec/ with it to see if that works?
[Motorola Droid 4] frankonia:
Oh, I think we misunderstood us now: This was the dump of the unmodified ("raw") ROM-version (without flashing SwapSD). I thought this could help you. - When I flash SwapSD the system is not running anymore after. When rebooting I experience an endlessloop of the boot-screen. So I couldn't make any dump of it.

I'll try to patch it manually. Will tell you later if it worked or not.
[Motorola Droid 4] jul515:
I extracted the ramdisk.img from the 2016-03-19 SDswap zip, and copied it to the /system/etc/kexec/ file (after renaming the existing ramdisk.img). Flashing the SDswap zip was successful, but again resulted in a bootloop. Device is XT912 spyder with CM 13.0-20160409-NIGHTLY-spyder.
[Motorola Droid 4] frankonia:
Same result when copying the ramdisk.img into the ROM (at /system/etc/kexec/ and deleted the old ramdisk.img before) and flashing it (with Gapps) on a clean slot: System stays hanging in boot-animation, as jul515 already stated. But doing with Resurrection-Remix latest build, which should be in core the same as original Cyanogenmod.
[Motorola Droid 4] Nayber123:
I too am having the boot loop issue. I was on cm 12.1 on droid 4 with sd swap for 12.1, no problems, and since early this month have been on cm 13 and tried sd swap. The phone keeps bootlooping no matter what I try. I did a full wipe, full sbf, re-root, tried in slot 1 and stock slot (was running in stock slot with cm 11 and 12.1, and now cm 13 in stock slot is working WITHOUT sd swap. I have no idea why it's not working. I am also using 1.4 ulv 'regular' OC and that is working perfetly! (thank you very, very much joojoobee) If sd swap was working, cm 13 with your kernel would be the best rom I'd ever used! Thanks joojoobee for your hard work and help!
[Motorola Droid 4] joojoobee666:
Doird RAZR as well? Anyone with this issue try the SDSwap after wiping? Also, can anyone with this issue get logs from logcat during boot?
[Motorola Droid 4] Nayber123:
Hi joojoobee,

I don't know how exactly to get the logcat from the bootloop boot, but if you explain I will do my best. :)

Thanks joojoobee!
[Motorola Droid 4] joojoobee666:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/

Reboot the device once all of that is setup, then use the "adb logcat" command documented there as soon as the safestrap logo appears. Copy/paste that to pastebin or something as it may potentially be large.
[Motorola Droid 4] Careless_:
latest cm13 nightly, latest ULV full-scale kernel, and currently booting into fresh install with SD Swap, no boot-loop yet. When are you guys experiencing it so i can look out for it?

EDIT: boot-looped as soon as applications were optimized. i saw the animation continue, but it just sent one vibration pulse every 4 or 5 seconds.
[Motorola Droid 4] Nayber123:
Careless, that's EXACTLY what I'm getting too. Tried following the directions to get the logcat during bootloop...nothing. Went back to cm11 backup for now. I need app access for ext sd card. did ok under sdswap for cm12.1, but annoying. Hopefully it gets worked out. all I can figure is access to sd card must be hard-coded out now somehow. I don't know.
[Motorola Droid 4] Careless_:
the last CM13 nightly I ran was jan 27, and the sd card was never directly accessible for some reason. i couldnt even see it in file manger- not sure why I even ran it so long.

I just updated to 04/21 nightly and its been waaaay better and I can actually use my SD Card now. So it's possible that whatever has changed in regards to using the SD files space in the roms could be causing allocation issues with the sdswap modification.

No idea, tbh, but I just wanted to try it before trying Xposed Picture2SD module- but thats where I am now... so we'll see how it goes.
[Motorola Droid 4] jul515:
Thanks joojoobee666. I followed the instructions but was unable to generate a logcat report. My device (Razr XT912) is only shown connected with the "adb devices" command when PTP is enabled. But when I then reboot, it appears the USB connection always returns to the default "Charging". So when "adb logcat" is initiated during the Safestrap screen, the command prompt simply returns "-waiting for device-", and nothing else is reported during the entire boot sequence. I haven't found a way to change the USB default from "Charging" to "PTP" so the device USB connection remains active after rebooting.
[Motorola Droid 4] joojoobee666:
I'll bet I know why. You will need to get debugging working FIRST before trying SDSwap. Install the nightly, but not the swap. After you enable debugging and connect to it once it is booted, the phone will assk if you can trust the PC. Checked the box to say yes, go away (or whatever). Verify adb logcat works now.

Once verified, reboot to safestrap and install the SDSwap zip, reboot and try again. Adb should say "waiting for device", but once CM13 starts to boot, it should connect and start dumping the goods.:good: