yashsingh1/xdaforums huggingface dataset:
[Motorola Droid Bionic] RandomPooka:
It may actually work with JB, as long as you don't use the 10% mod. It can't hurt to try and restore your backup if it fails.

---------- Post added at 07:48 AM ---------- Previous post was at 07:48 AM ----------

Why would you want to?
[Motorola Droid Bionic] kschang:
I have an unpopular phone and current Kitkat Roms don't have all the function I need, so I am struck in jelly bean for a while longer.
[Motorola Droid Bionic] RandomPooka:
Well, if you don't have a moto omap4 device (RAZR, Bionic, Edison, for example), JBX won't do you any good anyway. If you do have one, then our devices do indeed have KK builds that are fully functional. Either way, you have to have the device that these builds are for, and if you do, you can run KK just fine.
[Motorola Droid Bionic] kschang:
SlimKat works on the Bionic (XT875)... but Tethering doesn't work. Which is a bit of a deal breaker right now. I even tried the Xposed module that supposedly fixes it.

I mean, i did try it... for about 8 hours. Unless I did tethering wrong? I set it up the same way as I did in JB. No devices will connect to it. Tried like two different tablets, both of which connected to the same phone running JB on ROM slot 1, but not to SlimKat KK on ROM slot 2.

I'll go over to the SlimKat topic and see if they have any ideas.
[Motorola Droid Bionic] RandomPooka:
Tethering works perfectly on the recent CM builds. There's a patch that needed to be applied for older ones (Beginning of March, can't remember the date) What date is your Slimkat build from? If it's based on the CM sources that hadn't fixed WiFi tethering yet, that would explain your issue.

It's been so long since I used that patch that I think I deleted it from my hard drive and device, unfortunately. On the upside, I *did* save it in DropBox .. :)

CM11 WiFi Tether Patch <-- Just flash this in TWRP like you would any ROM or other zip. Make a backup first, in case it doesn't solve your problem. Then, you can restore just the /system partition and revert back to how it was. It doesn't affect your /data partition, so there's no real need to spend all that time backing up and restoring /data unless you're like me and back up everything every time.

---------- Post added at 07:37 AM ---------- Previous post was at 07:35 AM ----------

The original thread for that patch is HERE, I believe.
[Motorola Droid Bionic] RandomPooka:
I never got around to testing it until today, but I'll confirm that 10% battery mod on JBX 3/28 is fully working. Running CM 3/30, but I think all AOSP based ROMs except PAC should work with it.
[Motorola Droid Bionic] dtrail1:
The new OTA is online.

Some of you might know this problem: when using stock rom the device tells you about hdmi cable is plugged and forces landscape mode until you turn the detection off in display settings.

Something is wrong with the pins, maybe they need to be cleaned or whatever.

If you got the same issue, you will see the kernel log sometimes is full of edid reading failures because it still thinks you plugged an hdmi cable.

This is annoying and eats battery because it always put sound and video through that hdmi port.

To avoid this annoying bug I included a sysfs toggle which you can use to turn on/off hdmi on the fly, and also a new init script (in aroma) which disables hdmi by default (you can turn it back on everytime by /sys/kernel/hdmi/hdmi_active).

Also some more new stuff has been implemented to make the kernel working more power efficient. Waiting for your feedback.

I didn't have enough time to upload the build to the other mirrors. Will do later.

Tapped from my RAZR BLADE
[Motorola Droid Bionic] RandomPooka:
Flashed with HDMI disabled, and it hung for something like 5 minutes on the CM boot animation. Will test with HDMI enabled after dinner. Currently back on the March 28th build
[Motorola Droid Bionic] milski65:
Can't test anymore. Moved on to Note 3. Wish you all the best. You all rock.
[Motorola Droid Bionic] RandomPooka:
New build up on OTA and Crackflashers.com. Going to test it after I make a backup. Hoping it installs fine "dirty" over 3/28
[Motorola Droid Bionic] RandomPooka:
Darn it. The two recent builds that have the HDMI toggle built in will not boot for me on a clean or dirty flash, with or without HDMI enabled.

I get the single vibe bump as the kernel initializes, and it starts the boot animation, then just hangs permanently during the boot animation.
[Motorola Droid Bionic] raymechanic:
I have to enable hdmi and disable 10% mod to get it to work with pac-rom
[Motorola Droid Bionic] qqzwc:
There are no any problems in my Mokee 44.2.

Are you using ART mode?
[Motorola Droid Bionic] RandomPooka:
I'll have to give that a shot. I'd gotten in the habit of enabling 10% so didn't think to try it the other way.
[Motorola Droid Bionic] RandomPooka:
Finally got a chance to flash 4/4 without 10% battery enabled. Works great. It also flashed just fine with HDMI disabled. This is good, since I don't have an HDMI cable anyway. It's not like I use it, so I'm glad I can shut it off.
[Motorola Droid Bionic] dtrail1:
I have to take the server down, cannot hold the costs all the time and don't won't to ask for something (hate it), and don't receive any donations atm. Everything will be slower and less accurate, no OTAs, but it's the best option so far.

Edit: maybe anyone knows about a root server possibility?

Tapped from my RAZR BLADE
[Motorola Droid Bionic] dtrail1:
Anyone using PayPal or Neteller? I need to exchange something.
[Motorola Droid Bionic] qqzwc:
No,I only use alipay in China....
[Motorola Droid Bionic] raymechanic:
Anyone have problems with update me? It reads that there is an update but won't let me get it
[Motorola Droid Bionic] dtrail1:
What? Actually the shouldn't be one yet. I just rolled it out for RAZR to let them test first before publishing for other devices. I did a mistake with the OTA server then.

Tapped from my RAZR BLADE
[Motorola Droid Bionic] dtrail1:
You guys noticed the update last night? That one was wanted, need feedback!

Tapped from my RAZR BLADE
[Motorola Droid Bionic] raymechanic:
Got it last night. Doing good. Running pac-rom with 10%off and hdmi on, with all the tweaks, under volted 100. Lte stays connected like I need it. Thanks for all that you do
[Motorola Droid Bionic] RandomPooka:
The most recent build is working well here, too. My usage has been pretty heavy, so I couldn't tell you what idle battery life is like on it.
[Motorola Droid Bionic] dtrail1:
New update coming very soon...
[Motorola Droid Bionic] qqzwc:
https://github.com/pengus77/lge-kernel-star (kerner2.6/CM10/CM10.2，very stable)

https://github.com/pengus77/kowalski (kernel 3.1/CM11，not stable)

This kernel for tegra2(LG P990) is the most battery-saving with no lags kernel I have ever seen，especially during screen off. And it also has high performance.

Could you borrow some codes from his commits?
[Motorola Droid Bionic] dtrail1:
sure, I will.

Anyone could help with exchange from different e-wallet (neteller) - so I can give it back to you - small donation with refund ;)
[Motorola Droid Bionic] qqzwc:
Thanks for your reply！ THIS IS his thread http://xdaforums.com/showthread.php?t=2097788

Power saving,high performance,no lags!

Sorry about donation or exchange， I am a student and I’ve not got a bank card .I only use alipay with a little money (Chinese Yuan)
[Motorola Droid Bionic] dtrail1:
thx! No worries :)
[Motorola Droid Bionic] dtrail1:
I have included a lot of back- and 'forward'- ports, patches and stuff from the other kernels, known as most power saving ones for Android. SO this update will be a real BETA TEST!

Well, I could keep it on hold, but maybe it'S better when many users test it, so I can get useful feedback. I will describe and warn you in the OTA notification.
[Motorola Droid Bionic] dtrail1:
Kernel Guide 1.7

*by Placca

- updated information

- updated pictures

- typo fixes

- improved pagination in PDF version

- page numbers in PDF version

PDF: http://www.mediafire.com/view/mcbyd2vblp1373h/JBX_Kernel_Guide_v1.7.pdf

CHM: http://www.mediafire.com/download/qs4uubaozsmuzea/JBX_Kernel_Guide_v1.7.chm
[Motorola Droid Bionic] RandomPooka:
APN backup/restore for more solid data connections

[MENTION=3322848]JakeDHS07[/MENTION] originally posted THIS TIP over in the Razr thread for JBX, and I thought it would be worth bringing a copy here. I know it's not actually a JBX issue, but the APN settings are always a problem with AOSP based ROMS.

..

..

..

I have never had signal issues and have always had LTE and never even seen the orange Google server problems everyone speaks of. Therefore I highly suggest everyone do what I did as clearly it helps.

1. Boot into stock ROM

2. Download Titanium backup and APN Backup & Restore

3. Using Titanium make APN a system app

4. Go into a explorer (Root Explorer or the like) move APN app from /system/app to /system/priv-app. (Required for jelly bean plus).

5. Open APN app. Ignore message and tap disable ICS check.

6. Backup the apns from stock ROM.

7. Boot into CM

8. Repeat steps 2-5 as necessary

9. Restore Stock APNs to CM choosing to overwrite and existing duplicated. (Keep clutter down)

10. If you choose to you can then make a backup of the now merged stock and cm apns that have been merged under your cm slot (I did just in case I ever need them)

This should help anybody that has issues. If anybody with a XT912 Verizon doesn't have time or has a recent version of CM that they don't like the apns for I have a stock +CM APN backup from months ago that will work for you and all you would have to do is go into APN backup and restore under cm and restore the file I give you (after setting up the app like I told you obviously). So if anybody wants that I will upload later. Also in case anyone is wondering the app needing to be system app was due to a permissions change that began in ICS where apns became unaccessible to other apps and the move to priv-app became necessary upon jelly bean due to further permission changes. But if you follow my instructions everything will work on 4.1-4.4 and you should be good to go with more stability and fully working LTE, 3G, everything.
[Motorola Droid Bionic] kschang:
I can't seem to figure out what I did wrong. I downloaded 4 different kernel files... the 3.0 2014 0323,, the 0410, the 0219, and even the older 2.1 0121. ALL four, when attempted to install via Safestrap, says "cannot cat /tmp/aroma/install.prop" and quits with "status 7". I've tried downloading from both DEV-HOST (as per Kernel guide) and Crackflasher. Same thing.

What am I doing wrong?

---------- Post added at 02:21 AM ---------- Previous post was at 01:35 AM ----------

Now I feel stupid. I was NOT using latest Safestrap 3.72, which is based on TWRP 2.7.X, which supports the NEW AROMA format. I was on 3.71, which is the OLD TWRP (2.4.x I think)

Once I got Safestrap updated properly, the Kernel flashed properly.

Maybe the great Placca can update the guide to show what a dunce I was
[Motorola Droid Bionic] RandomPooka:
I know it worked in SS v3.65, so I don't know why it wouldn't work in 3.71
[Motorola Droid Bionic] kschang:
If you get an error "installing" through Safestrap, update Safestrap. :) That's easy enough.
[Motorola Droid Bionic] kschang:
Semi-dumb question: how important is it to keep up with the latest release? I keep getting that annoying "Update me" notice that I'm using 3.1.6 while the latest is 3.2.1. 3.1.6 was quite stable for me, after about 8 or so hours.
[Motorola Droid Bionic] RandomPooka:
I'm actually happier with the 04/10/2014 build than with the 04/16/2014 build. If you go into the "UpdateMe" app, you can disable autochecks on everything and just check manually. I freeze the app entirely.
[Motorola Droid Bionic] dtrail1:
1.11 Intelli-Plug

Intelli-Plug is a kernel side replacement driver for Qcomm's MPDecisions. It handles CPU scaling depending on the current CPU/tasks load.

Usually Intelli-Plug turns the secondary core(s) OFF as soon as the current CPU load reaches a specific defined status (i.e. goes below 30% or any frequency below 400 Mhz). But as we already know hotplugging during the device is actively used (screen is on) it's more supposed to eat battery than saving some juice.

Why? Simple logic: a Dual-Core running both cores each at 400 Mhz needs less power than running only one core at 800 Mhz! Also turning secondary core(s) constantly On and OFF again needs power for sure!

Therefor I changed the hotplug behavior a little bit, so it's now by default only allowed when the device enters sleep mode.

But isn't it the same like "Dynamic Hotplug" ??

NO! Simply because Dynamic Hotplug also turns the secondary core OFF in sleep mode - but then the second core will stay OFF as long as the device is sleeping / the screen is OFF. This can cause a higher battery drain in some cases because even when a big task arrives at the CPU, it will be handled with only one core enabled, probably at most highest speed (frequenc) set available by user. This also can lead to lockups or freezes in very less cases and is responsible for slow wakeup processes (when user wakes up the phone sometimes the screen needs some time to come up).

But Intelli-Plug always allows the secondary core(s) to be enabled if needed - also during sleep! This potentially saves some juice as the CPU doesn't have to handle bigger/BIG tasks with it's half of available power, and even protects against potential lockups and/or laggs, while also avoid slow device wakeup on device resuming by user.

To sum it up:

For intelli-plug hotplugging is now only allowed when the device enters sleep.

To enable hotplugging universally just change the value of the following entry whether to 1 (on) or 0 (off):

sys/module/intelli-plug/parameters/int_hotplug

*Unfortunately I don't have enough space in the OP to write all this into the FAQ, that's why the I only added the sysfs path, but the description is simply here
[Motorola Droid Bionic] kschang:
Now for a "whew! that was close!" moment of relief....

I was mucking with JBX kernel, as after an initial low power consumption (5% per hour), my phone all of a sudden started sucking down 12-14% per hour of juice, and this is on an extended battery! Battery mix insists it's Bluetooth share that's eating the juice (I do use Bluetooth A2DP quite a bit) at 27% (and the Podplayer Doggcatcher just behind at 20%). Until I did something, I can't remember what, and it won't boot any more! (It may have been trying to undo the setup through recovery by uninstalling the kernel there). It just goes black, after the moto logo and safestrap. waited 3 minutes, NOTHING. Pulled battery.

Tried all sorts of things for a whole morning, as I don't have a Nandroid backup of this! (WTF?!) I decided to reflash SlimKat on top of the setup (dirty flash), then wiped Dalvik and Cache. It booted right up, no problem.

So now you know... you *can* dirtyflash the same ROM.
[Motorola Droid Bionic] dtrail1:
Time for an update!
[Motorola Droid Bionic] dtrail1:
dirty flashing is what I always do..mostly
[Motorola Droid Bionic] RandomPooka:
Same here. I LOVE it dirty
[Motorola Droid Bionic] wilkster:
I just installed the 2014-04-10 JBX ROM for bionic/targa over CM11 (2014-04-25) and the combination seems to be running smooth. Things do seem a bit snappier. I did notice however that the battery percentage is changing in 10% increments vs. 1% as before JBX. I went back and disabled the Motorola 10% Battery Indicator and reloaded the kernel but the 10% increment didn't change. I looked in the OP/FAQ and din't find any info on this. Is there something I missed to re-enable the 1% support?

Cheers,
[Motorola Droid Bionic] dtrail1:
Reflash Rom is the only way for now.

Tapped from my RAZR BLADE
[Motorola Droid Bionic] kschang:
Yeah, reflash, but you can "dirty reflash".

Don't forget the AOSP WiFi Tether fix.
[Motorola Droid Bionic] dtrail1:
Update is online, guys.

The changelog is too large - or I'm too lazy atm :P

But this build gives me solid reults on battery life and performance. Seems some things are right in order now.
[Motorola Droid Bionic] wilkster:
Loaded 2014-04-27 Version, so far working fine. A couple items in the logs that don't look right however:

Getting these about every five seconds (was also seeing this on the prior to kernels as well). No obvious demsg errors on SELinux startup

04-27 16:54:09.513 I/auditd ( 4880): Starting up

04-27 16:54:09.513 E/auditd ( 4880): Failed on audit_set_pid with error: Protocol not supported

04-27 16:54:09.513 I/auditd ( 4880): Exiting

Also getting about 12% RX_Wake locks with WiFi on, have been seeing this in recent CM releases. Don't see it on stock.

Will continue to report anything unusual.
[Motorola Droid Bionic] RandomPooka:
Running the 4/27 JBX and the 4/24 Liquid Smooth. Getting random lockups with side reboot. Occasionally battery pull is required. Hard to get a semi accurate idea on battery life until I figure out what settings I have with JBX that are causing the problem. Inclined to believe it's the memory tweaks. The clock speeds and voltage I was using ran fine on the 4/25 CM11, so I'm thinking LS has included memory management tweaks that conflict with the JBX scripts I was using.
[Motorola Droid Bionic] RandomPooka:
Ditching LiquidSmooth. Various reasons, one of which is instability with JBX on Bionic.
[Motorola Droid Bionic] dtrail1:
With the latest uodate JBX ther instability with LS is history - fon RAZR at least.

You and all others might want to read my detailed review/guide about JBX settings (starting in Aroma) here:

http://xdaforums.com/showpost.php?p=52350860&postcount=74

Also added it to the OP under Instructions - named it now "Installation Guide" and fixed/added some things.
[Motorola Droid Bionic] RandomPooka:
Just posting an update. Running the CM11 released today on May 4th, and the May 1st JBX. Seems to be doing fabulously. Battery life is fine, performance is fine. No real issues to speak of that I've yet found.
[Motorola Droid Bionic] kschang:
Running it with SlimKat latest and with screen off it's sipping at about 5% per hour. However, when the screen's awake, even with utilities like Lux Lite it's quickly draining batteries at 15-18% per hour. (and this is AFTER that full calibration that dtrail recommended) Is that "normal"? :)

I'm going by BatteryMix graph and Xposed KitKat batterystate enabler.
[Motorola Droid Bionic] RandomPooka:
You're not likely to see much battery savings while using the phone. At least, I've never been able to say I've had luck with that. Use it, and it will drain with a quickness.
[Motorola Droid Bionic] Ismokel:
5/1 jbx + cm 5/4 = win
[Motorola Droid Bionic] RandomPooka:
Anyone try the 5/5 M6 CM with JBX yet? I flashed it this morning, but had audio issues and had to restore my backup so I could go through the day with a functional phone.
[Motorola Droid Bionic] dtrail1:
Keep in mind that your phone and battery needs to settle for about one week after the calibration.

Also, why using the xposed battery stats module? It's not needed anymore and needs some power itself (see logcat).

Btw: I have a nice average drain with active screen.

Tapped from my RAZR BLADE
[Motorola Droid Bionic] kschang:
It's more like battery stat enabled, unless that's enabled by slim kat already?
[Motorola Droid Bionic] dtrail1:
It's not needed anymore because such apps like Better Battery STats are already supporting KitKat.
[Motorola Droid Bionic] kschang:
Running BetterBatteryStats XDA ed. now, rather than my normal "BatteryMix". It has nice stats but almost a bit too geeky. Doesn't "WakeLock Detector" do the same thing?

Also, if the battery charging slope goes up, levels off at about 60%, then goes up against in steady slope until 100%, does that mean I need to recal the battery again?
[Motorola Droid Bionic] shawnn125:
anyway to enable 1% battery stat? I couldn't find in this threead.
[Motorola Droid Bionic] kschang:
You probably have to nuke the whole ROM to get back your original 1% bat if you installed the 10% batt mod. There's an earlier comment on this by Dtrail, I think.
[Motorola Droid Bionic] RandomPooka:
Just go into recovery and reflashe the rom without wiping anything. Then reflash JBX and make sure not to select 10%. No worries. No data lost.
[Motorola Droid Bionic] kschang:
My battery's definitely cooked. I took it out and I can feel both "cells" is bulging out from the middle. Crap. Good thing replacements are cheap and plentiful on Amazon.
[Motorola Droid Bionic] raylgo:
This kernel doesn't seem to be compatible with the GSM hack... o_0 Wanted to try it out too.
[Motorola Droid Bionic] KC69:
5/22 jbx is out on crack flasher. Fixin to flash it on gummy.
[Motorola Droid Bionic] KC69:
i havent had time to flash this newest jbx , has anyone tried it ?
[Motorola Droid Bionic] RandomPooka:
I've been running it yesterday and today without issues.
[Motorola Droid Bionic] RandomPooka:
Just thought I'd add that with the 5/22 build, I get a hard reboot after every phone call. Doesn't happen with 5/01
[Motorola Droid Bionic] chrisp6825:
Running the 5/22 build here for the past 2 days and haven't had that issue.

Also on the 5/24 build of cm.

So far everything seems very stable.

---

Also I wanted to note, one of the bundled tools (not kernel tweaker or trickster mod, I forgot the others name after I uninstalled it), won't run without gapps flashed. I'm not sure if anyone else here runs without gapps, but just though I'd throw it out here.

tapa'd on my bionic
[Motorola Droid Bionic] RandomPooka:
Perhaps it was something new in the 5/25 and 5/26 build, because I don't remember it happening until after I flashed those.

I'm about to jump to an LG G2, but my Bionic will live on as a wifi only device for my kids and JBX will be a must on it and my wife's.
[Motorola Droid Bionic] qqzwc:
Why not try OnePlus One?
[Motorola Droid Bionic] RandomPooka:
Mostly because the G2 was in my price range!

-- Update --

G2 stock software is so clunky feeling, compared to CM11 .. But the battery life on both Stock and CM11 (for the kitkat OTA firmware) is insane, compared to what I was getting on my omap device. At work, coming off of a full charge, I was down to 98% after 2-1/2 hours (in pocket asleep) and like 95% after 5 hours or so. A little usage here and there with texting and such
[Motorola Droid Bionic] chrisp6825:
On 5/22 build still. No tweaks to the media processing clock. Getting freezes (full system freeze, with audio sputtering the last few ms of sound repeatedly)

I'll play with it, update, and try to pin point it more later. Just wanted to post about it for a second.

---

This was happening very rarely and sporadically. I believe it usually happened when the phone was under a heavy load. I haven't seen the issue again yet.

tapa'd on my bionic
[Motorola Droid Bionic] Casey Walt:
overclocks... not permanent

the black screen was fixed but the oc doesn't stay permanently. I set it at 1.3 GHz and 1.2 GHz and it works but it doesn't stay no matter how i set it i am using cm11
[Motorola Droid Bionic] dtrail1:
Use the frequency lock to make it persistent.

Guys, an update is coming as soon as I will have rebuilt the device tree repos for targa and Edison.

Gesendet von meinem XT910 mit Tapatalk
[Motorola Droid Bionic] Oggie7797:
Sorry for noobish question but I'm not a big fan of trickster mod and would rather use kernel tweaker. Can I simply delete trickster with root browser or do I need to wipe system and reflash ROM gapps and kernel? Didn't wanna break anything :p thanks for the sweet kernel

Tap'd from my Paranoid Bionic

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

The problem i have is I want the max frequency on 1.3 and when go to to settings it says I'm on 1ghz and I'll set it at 1.3 and every time I get on trickster I get a root warning saying it's malware but that doesn't concern me lol trickster just persists in setting the CPU to 1ghz and it's annoying

Edit: Never mind figured it out lol

Tap'd from my Paranoid Bionic