yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] Germknoedl:
testing this rom for a few days now. i really like it so far! well done! :D

had one random reboot with some kind of data loss...

lockscreen was set back to an earlier state, firefox bookmarks gone, k9 mail account gone and downloaded pictures lost.

kinda like it went back to a restore point. :confused:

can't provide a log.

but now i'm running a logcat app to provide more info if it happens again.

flash history: stock KK -> ota L -> stock KK(screen flickering) -> stock L -> SaberMod. full wipe.

forgot to flash L radio firmware separately. can i flash it via TWRP on sabermod? do i even have to?

XT1039 EU + TWRP 2.8.7 + 41.1A BL

keep up the good work @beeeto!:good:thx mate
[Moto G 4G Android Development] Gianlu92:
As you have received the OTA update, you already have the correct modem files and you don't need to flash anything. That kind of data loss happened to me too some builds ago (many builds ago, to be honest lol), they suggested me to do a full wipe including internal storage, and then perform a clean install. I am not really sure if it did the trick, as I changed lots of ROMs in the meantime, but when I tried some more recent builds of beeeto's ROM, the problem was gone.
[Moto G 4G Android Development] hotbld5:
Hey beeto, how's testing been going? It's been pretty quiet here.
[Moto G 4G Android Development] beeeto:
Changelog

Link: Build 24

Kind regards! :)
[Moto G 4G Android Development] Travisholt92:
And you couldn't send me a message? I'm disappointed.
[Moto G 4G Android Development] beeeto:
Hey guys,

Forgot to hardcode the default scheduler set on "ROW" as default, I really like it over the new cm choice "BFQ" I suggest you to change it with TricksterMod until I release a newer build. :cowboy:

I deleted pushbullet turd, catch me on hangouts
[Moto G 4G Android Development] Frazew:
Hey ! I'll start implementing EAP-SIM this evening. Meanwhile, cherry-pick this [MENTION=5270463]beeeto[/MENTION] :D https://github.com/CyanogenMod/andr...mmit/6a9377825535356637627ca50c956563e6d68cf2 (It should allow the Moto G to be used with DriveDroid, it was implemented but got dropped after the rebase for CM12.1 I guess)
[Moto G 4G Android Development] Germknoedl:
I'm still on 23.1 - changed internal and external scheduler to ROW.

Gonna wait for 24.1 then... :D

btw.. had no random reboots since i dirty flashed 23.1 again.

awesome work, meister beeeto! :highfive:
[Moto G 4G Android Development] Sparubens:
Hi, there's a bug: when I block privacy notifications from apps (when you adjust privacy from apps in settings there's an annoying notification for every app when you ignore location access for the selected app and all), after a reboot they return and I have to block them again (longpress notification and press ''bell'' button. Guess you can't do anything about it and maybe a CM related bug. Smooth as ever though. Cheers
[Moto G 4G Android Development] beeeto:
Hey guys,

I need some assistance testing 2 builds, so if you feel like going to an adventure you can help me to try them. Both builds are identical compiled with a different set of flag optimizations, that's why one is 287.3MB and the other 279.5MB.

Please note that these flag optimizations in the compiler are not magic, so the difference will not be made by getting 30k on Antutu or something crazy like that. The difference should be noticed at everyday usage with a overall feel of the phone working better.

So yeah, enough chat, here are the builds;

Build A V/S Build B

I'm eager to see your thoughts about this so please report back.

Kind regards!

[MENTION=5984819]Frazew[/MENTION] That's great! I will be waiting pull requests then :D
[MENTION=5225233]Sparubens[/MENTION] Those cosmetic bugs are CM side, I don't really touch framework part.
[Moto G 4G Android Development] Frazew:
[MENTION=5270463]beeeto[/MENTION] Indeed, I'm setting up a new build environment, my previous one wasn't very good (Thanks for making the roomservice_and_misc repo, this will definitely save me quite some time). I've already searched for the interesting commits so it shouldn't take long (only a bit of coding to make sure it matches the newest sources). I'm also planning to see if I can manage to get HFR (High Framerate Recording) to work (That's what allows slow motion on stock rom). So yeah, you should get pull requests ! :D
[Moto G 4G Android Development] johan111:
Hi beeeto, I am running ver.B of your last test build and what I found is: min. value for CPU frequency is 300 (previously 192), lack of some CPU governors and TCP congestion algorithms. Was it your intention or just oversight?

Besides that I feel it is more smooth than build 24 so far.
[Moto G 4G Android Development] Germknoedl:
Flashed Build A...

Default scheduler is still "bfq" - am I allowed to switch to "row" for testing? :D
[Moto G 4G Android Development] beeeto:
Yay! Of course, but make sure you use ROW on both builds :D

Intended, it seems that 192Mhz use the same voltage as 300MHz so there's no point using it. I have yet to measure the voltage consumption to make it official, remember these are testing builds :)
[Moto G 4G Android Development] beeeto:
I'm taking a little break from Cyanogenmod to develop stock kernel meanwhile you guys try both builds I left here.

Also I wanted to say thanks to an anonymous user who sent me a donation. It is amazing to see such a supportive community with these projects I do on myspare time, it makes me really happy. That is the main reason I'm not leaving this device any time soon.

Kind regards as always. :laugh:
[Moto G 4G Android Development] wurstel:
Whats the difference between a and b?
[Moto G 4G Android Development] arthurpl:
A is the first letter of the alphabet and b is the second... (in Polish actually is third :D)

Geez men, are you so f...king lazy to check a few posts earlier?
[Moto G 4G Android Development] johan111:
Well, I spent one day with ver. A and one with ver. B with similar usage and I would say ver. A is bit more fluent. Moreover on ver. B Opera mini and CM browser crashed when query for internet search was typed into the address bar. In contrast, UC browser worked fine.

Battery life was pretty the same on both builds, and it was really long life as always with beeeto ROMs :)

And I noticed that SELinux mode was enforcing which prevents Viper4A from running. So I simply changed it to permissive. That's for people who have a problem with V4A and can't figure out what's wrong.

I also had an issue with ver. A backup. The restored system stuck at boot animation. But it might be related to Online Nandroid Backup which I used to take a backup.

Thanks [MENTION=5270463]beeeto[/MENTION] for your great work!
[Moto G 4G Android Development] Germknoedl:
Build A is/was very smooth. I really like(d) it!

Switched to Build B a few minutes ago.

Right after flashing: annoying popups "google play has stopped..." and I wasn't able to connect with my account.

So i reflashed gapps - which I didn't have to do on build A.

Still popups.. Then they disappeared. Hopefully straight to hell. Now I'm able to connect.

Mystery? Magic? Or me just being n00b?;)

Running both on row scheduler.

@johan111: after reading your experience with build B.. logcat activated!

Other Question: how long does it take until your wifi has a connection? ~10 sec?

@beeeto: have fun with your kernel stuff! Please don't forget us. :crying:
[Moto G 4G Android Development] johan111:
Regarding Wi-Fi connection time, yes it is about 10 sec when activated from quick settings tile. And ~3 sec when switched from Wi-Fi menu. Do you have/had the same?

I have already left ver. B and I am not going to go back, so sorry, but logcats won't be taken unless beeeto really needs them
[Moto G 4G Android Development] Germknoedl:
Oh, I meant that your experience made me start my logcat app.

It always takes ~10sec in my case. I guess that's normal on L/CM.

Mostly I'm using power toggles to activate wifi.

So far it seems that build B uses a bit less RAM.

Y'all have a nice weekend! Beeer! :silly:
[Moto G 4G Android Development] Travisholt92:
Did you do a clean install of build b? If not, that is your issue.
[Moto G 4G Android Development] Germknoedl:
Well...

Installation Instructions:

Upgrading from a previous build:

1.- Flash the ROM

2.- Flash any add-ons you want

3.- Wipe dalvik and cache

4.- Reboot into ROM

In my case: flashed build B, supersu, wiped dalvik and cache.
[Moto G 4G Android Development] Travisholt92:
If you're having gapps issues it's because beeeto has been testing different toolchains and optimisation flags which require a clean flash when switching between builds to avoid force close errors. (I'm having the same issue but I've been too lazy to clean install)
[Moto G 4G Android Development] wurstel:
Install the "a" build. No fc's (had them in b, dirty flashed a over b coming from v24, just wiped system/dalvic/cache), battery life is insane (i'm not kidding). Performance is on par with optimized stock. So everyone upgrading should flash a.

(Running it on a xt1039)?
[Moto G 4G Android Development] Germknoedl:
@Travisholt92: Ok. Didn't know that.

Regarding laziness: same here!

gApps issues are gone for now.
[Moto G 4G Android Development] beeeto:
The guy is right, build B has different set of optimizations that most likely will cause errors on dirty flash.
[Moto G 4G Android Development] Travisholt92:
Check your hangouts. I have a building related question for you

---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------

I for instance sometimes have an issue where when I open an email it will fc upon loading. Which I know is caused by dirty flashing.
[Moto G 4G Android Development] Germknoedl:
Theoretically... When flashing from B to A -> full wipe is recommended?
[Moto G 4G Android Development] bl4ckbluntz:
Hello

I installed the build A

It seems that this is a great build !!!

Good work Beeeto wow
[Moto G 4G Android Development] danny8:
Sometime after departing from good ole' SaberMod, I'm returning to the fold. :)

I just installed [Build A] of SaberMod 24 (or is it Build A of 24.1?) plus tk_gapps pico version.

It runs really smooth so far. No FCs at all, only issue was a lag or hang at the "enable location" dialog. Home key was able to get around that.

For anyone not following this thread closely, don't use Build 24 from the OP of this topic. Use Build A from this post instead.

Also, don't forget SuperSU to enable root access.

I'm just trying to help out, anyone please correct me if I'm mistaken. Looking forward to latest build! Thanks!
[Moto G 4G Android Development] ssirK:
hello all,

i flashed build A and gave the phone to my mom, seems to be working nicely, ill post here if she calls me for tech support!

thx again for all your build beeeto, it was a pleisure flashing and using them ! :)
[Moto G 4G Android Development] beeeto:
Thank you for using it!

Best of luck with your new phone :)
[Moto G 4G Android Development] Travisholt92:
Build A is pretty great, multitasking is no issue at all (which is a must have since I have Facebook installed). Thanks for the build bud
[Moto G 4G Android Development] Hastaloego:
did build A change anything on how LMT works http://xdaforums.com/showthread.php?t=1330150 ?

suddenly the Killapp options doesnt work anymore
[Moto G 4G Android Development] WiCiO_MeDi:
so... build A is a candidate for b25? :)

just asking 'cause I want to flash my moto G one last time.. :eek:
[Moto G 4G Android Development] Travisholt92:
Build A is great, you need to do a clean install of it however.
[Moto G 4G Android Development] WiCiO_MeDi:
this part wont be a problem since i'm selling my beloved G :(

gonna miss you gey.... blah! guys! :silly:

this topic has been most entertaining ever!

p.s.

yeah, the ROM is also the BEST :good:
[Moto G 4G Android Development] Hastaloego:
sell it to beeeto [emoji12]

Gesendet von meinem XT1039 mit Tapatalk
[Moto G 4G Android Development] beeeto:
Oh come on guys, please don't leave me alone with Travis :crying:

Being serious, it always made me kind of sad when people moved to a newer device, call me a sensitive witch.

Oh well, here's the kernel of Build A which is brings a noticeable improvement over older releases.

Link: Beto's_Kernel_V5.0.zip

I have yet to merge the extra features such as governos and TCP options, they'll be avalaible on 5.1

Regards!
[Moto G 4G Android Development] Hastaloego:
dont worry beeeto. Asus ****s up the German release of the zenfone2, so I guess in gonna stick for a while ?

Gesendet von meinem XT1039 mit Tapatalk
[Moto G 4G Android Development] Travisholt92:
I'm just waiting to have you alone ;D. I'm going to be switching to the galaxy S4, keeping my moto g for practice/test building.
[Moto G 4G Android Development] keenofhiphop:
yeah it should be frequency lock.

However, I like ROMs with various optimizations built in and I thought about whether or not Feravolts optimized Toolchain could improve this ROM as well:

https://www.google.de/url?sa=t&sour...XDnce1_kjjKN_9cOQ&sig2=U0hrfCb6TF2ghq8NzhIZhA

Probably you already heard about it, however my first phone was an Xperia X10 and FeraVolt really gave new life to this device.
[Moto G 4G Android Development] EternalFlame:
Hey beeeto,

you mean "wakelock blocker" option ?

It´s build in in BlissPop (v2.1)

cheers and keep this up ´cuz i will try your builds when i got more time :)
[Moto G 4G Android Development] Bastlwastl2010:
No Camera Issues here, but i use Camera Zoom FX and the Google Cam
[Moto G 4G Android Development] Kayant:
It wouldn't really help because our device is using cortex a7 which is newer and supports some things that architecture doesn't. There are already toolchains optimised for our device ;) like so - https://github.com/Christopher83/arm-cortex_a7-linux-gnueabihf-linaro_4.9.

http://xdaforums.com/showpost.php?p=58273710&postcount=763
[Moto G 4G Android Development] ebol94:
Hey [MENTION=5270463]beeeto[/MENTION] many people here claim they have Lollipop Kernel. Did you have the opportunity to take a look at it ?
[Moto G 4G Android Development] beeeto:
Yep, I have bringed in my features to the new kernel, but I won't build with it yet becouse its causing issues like screen tearing. We need to wait until have official Lollipop bootloader to see those issues gone. Meanwhile I am trying to polish stuff as much as possible. Don't want you guys to use a ROM with those problems. :o
[Moto G 4G Android Development] Pupet_Master:
I wonder how this ROM Kernel would work on other Roms based on CM12.
[Moto G 4G Android Development] Darius_AWS:
If you need lp boot loader just ask :) somebody post a working one on firmware topic
[Moto G 4G Android Development] beeeto:
New build is up and running buddys. Sorry for taking so long, but had to reinstall my Linux system and my ISP was behaving like sh~t, I couldn't even sync my sources (And I'm supposed to have 80mb of DL speed). Anyway, if you are an advanced user please go down this post if you want to provide me some help in further builds.

Changelog:

Link: Build 4

I have removed my recommended settings so I REALLY would like to know your experiences with this new implementation of Intelli-Plug and MP-Decision, I'd like you to also test Simple_ondemand governor for GPU so we can find the best setting to keep the temperatures as low as possible. I need some help becouse I am a little biased against Intelli-plug thinking it worked best on kitkat.

Regards and a big hug to all of you :cowboy:

Special thanks to [MENTION=5161352]JustArchi[/MENTION] for his amazing work.
[Moto G 4G Android Development] Bastlwastl2010:
Thanks a lot..

Will test it and give feddback in 2 - 3 days.

And you must not apologize for the lack of updates, we all (i think so) have a "real" life with work (for the money) and familie. :)

The only thing is: Give us a feedback if (i hope in a far far away future) you have no time or desire to continue the rom :cowboy:

I hope my english is so good that you understand what i mean

Thanks a lot again for your work
[Moto G 4G Android Development] beeeto:
Guys, as I have suspected, there it is an issue with Intelli-PLug and Lollipop (Well, not exactly LP but CM12). There's a setting under performance tab called "Enable per-app profiles", this setting tends to play with hotplug enabling MP-Decision on heavy tasks such as Antutu (Auto enables it no matter if Intelliplug is already running, the result of both hotplugs running is a loss of almost 10% battery per hour and soft reboots). So knowing this and assuming that not many people read this thread I have 2 possible ways to deal with this:

1.-Disable Intelli-Plug or MP-Decision

2.- Warn you about using Intelli-Plug so you guys can disable "Per app profiles" feature. (Utopic, since many people doesn't read everything I write here)

What do you think about this guys? Disabling per app setting is not an option couse becouse means digging into a lot of code that I don't want to look and doesn't guarantee to solve the issue.

[MENTION=6147790]Pupet_Master[/MENTION] I think saw some post of yours about Intelli-Plug, is this the issue you were talking about?
[Moto G 4G Android Development] Pupet_Master:
Well Yes and no.

Yes in the aspect that the issue is indeed that both intelliplug run at the same time. How ever even with the performance in app profile disable at the reboot it turn both on again.

My "solution" was to use a Kernel Adiutor profile for disable MP Decision at each boot.

Also another issue was it vs the pink kernel. The Pink Kernel disable MP Decision on the command line of the kernel build.prop where this one here does now. Yet it is good it does not as with the Pink Kernel i had terrible stability issues and with the kernel of this ROM it is ultra smooth (and i use this kernel on another ROM so i can bet that with it own ROM it would be insane fast).
[Moto G 4G Android Development] sbpetro:
[MENTION=5270463]beeeto[/MENTION] - I disabled the per app profile setting as suggested and set the CPU to interactive / GPU simple on demand. Everything works great. I did a few reboots to make sure per app performance setting did not come back on and every is good! Very smooth performance. I will report back with how the battery does.
[Moto G 4G Android Development] Caleb_cz:
Wow, Build4 is really fast, app launching is way more faster than Build3. I had problems with soft reboots with Build3, but i thought, its becouse of dirty flash from OFFICIAL nightly. Now i disabled per-app profiles so lets see whats happend with Build4.

I have a small question. Files in /sys/module/lowmemorykiller/parameters still have strange (--w--w----) permission. Do you guys use Moto G Multitasking Fixer or something like that?

I'm really excited about this rom, and i doubt motorolas lollipop will be any better. Thank you for hard work !
[Moto G 4G Android Development] rfsteel:
I've been running Build 2 & 3, before upgrading to Build 4 last night, I found with the earlier 2 builds that when streaming media via bluetooth, the audio was very choppy and would stop when trying to multitask, i.e. using the browser to another app.

Having upgraded to build 4, the music streaming is a lot clearer, and no more stopping when multitasking.

One problem I did have with build 4, was applying superuser once the build was installed, whatever method I tried, the phone wasn't been rooted, in the end I had to resort to running the CF-Auto-Root script;

http://xdaforums.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406
[Moto G 4G Android Development] beeeto:
Back to business, there's new build up, kernel changes are strong with this one. I made a list with some relevant stuff, for a more detailed view please visit my github.

Changelog

Link: Build 5

To sum up, I'm really happy with the the direction I took with my kernel, ROM feels snappier as ever and I *think* battery life will be good becouse we are using one of the best Hotplugs on XDA (Intelli-Plug). Don't forget we still need to add Graphite, Strict aliasing and O3 by SaberMod to the equation, so I think there's a lot of margin to get this ROM even better. :fingers-crossed:

Kind regards!

-----------------------

Edit:

[MENTION=437126]Caleb_cz[/MENTION] Honestly I have not played with these values yet, since I feel memory managenement suits my needs for now. But I'd love to you guys -if you want- play with them, if you find good values and permissions for lowminfree file I'll gladly make them by default on the ROM if everyone is having good experience with them. Once again I think [MENTION=6147790]Pupet_Master[/MENTION] have made some scripts for lowminfree and have experience messing with these values on other kernels but not mine. You both can always test values and use this thread to discuss them, that way we can all try.

And who knows, maybe we can fix what motorola couldn't? :cyclops:

[MENTION=474009]rfsteel[/MENTION] Thanks for your feedback mate. To enable root you must activate it on developer settings OR flash latest SuperSu (This one is weird couse we don't get superSU icon but it works). Regarding your comment about multitasking, that improvement may be caused by Strict-Aliasing optimizations implemented a few builds ago. They are not present on Build 4 couse I have rebased my build branch to implement JustArchi optimizations, so expect it to work even better when I do. ;)
[Moto G 4G Android Development] Caleb_cz:
I tried many combination of permission and values, but problem appears after few hours of using phone. For example - today (3hours uptime) i wasn't be able to use Google maps navigation together with Spotify. I know our Moto G has only 1 gig of memory, but come on - 2 apps multitasking isn't possible?

I had same problems in Kitkat, feedly + chrome, spotify + google maps, entering one apps kills second. I think this must be serious bug in motorola's kernel.

My old nexus 7 with 1gig of ram has little bit more free memory becouse of lack of gsm services, but multitasking in really another dimension. For me, this is really annoying bug, sometimes whole device is quite unusable.
[Moto G 4G Android Development] scattoit:
I have the same problem. I can't use Google navigation and listening music via bt in my car.
[Moto G 4G Android Development] rfsteel:
I tried multiple root .zip files, and ensured developer mode an debugging were enables before installing the zip;

supersu.zip

SuperSU-v1.86.zip

UPDATE-SuperSU-.zip

I tried with CWM 6.0.5.0 and TWRP 2.8 all with the same results, failure. I even had the same issue after installing Build 5, the only solution was to use the CF-Auto-Root script.

I'm also afraid to say that the music streaming to bluetooth stutter is back, but now when multitasking it now takes a lot longer before the streaming pauses, so there is some improvement.

I will try using the AwesomePlayer instead of NuPlayer in the Media Developer Options to see if this has any improvement and post my findings tomorrow.
[Moto G 4G Android Development] Bastlwastl2010:
[MENTION=5270463]beeeto[/MENTION]

The link to your source

https://github.com/IndieBeto/cm12kernel

dont works ?? (Page not found)

FIOPS gone in the new Kernel?
[Moto G 4G Android Development] pozidrivphil:
Hahaha :)

I know what you mean though, the mobile device turnover is just too fast!

I'll stick around a bit longer though, can't let you have travis all by yourself!

Haven't flashed your latest build yet, hopefully I'll have some more time soon (the prospect of a clean flash always makes me postpone a flash)
[Moto G 4G Android Development] WiCiO_MeDi:
s4 is mediocre, had one until my mom ran it over with her car... yeap, it really happened :/

i'm sticking with moto, just switching the letter ;)

maybe beeeto would go there too..? beats hanging with travis, alone ;P
[Moto G 4G Android Development] SalvH:
I'll still be on the xt1039 for at least a couple of months more!

We can simply flash that over build 23.1, right?
[Moto G 4G Android Development] EternalFlame:
Haha, don't worry beeeto, i´m still around, despite i switched to a LG G3 (i got it for just 100 bucks) but i maintain my old Moto 4G for my mum so guess i´m hooked no matter what to this thread,

+ the Moto 4G community is awesome IMO :)