yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] fermasia:
Weird... I took the patch from Omnirom's gerrit (is/was unmerged) but can't find it anymore. Anyone has a link to help me out?

Btw, I'm not sure if what's there follows CM's commit or not. Anyone using the last build can confirm unusual batter drain? I can't be 100% sure since I'm trying other stuff alongside these changes.
[ONE Original Android Development] taufiqs:
that's why i'm asking for it. In cm gerrit, it is has been confirmed and they reverted it back. i've just flashed latest omni without touch driver + your kernel (which including touch driver).

i'll have you the information regarding the battery drain.
[ONE Original Android Development] nadiros:
I don't understand, aren't the new touch drivers kernel only? Sounds like you're saying there's another element ROM side?
[ONE Original Android Development] taufiqs:
oh sorry for the incomplete information. There are two unofficial omnirom builds, one with new touch driver; one without. I'm using the latter. Just in case the driver is being installed twice and resulting problem (stay paranoid *pun intended).

btw, which ukm version are you using now?
[ONE Original Android Development] darkobas:
Ive abandoned the commit so its under abandoned commits
[ONE Original Android Development] fermasia:
Thanks, then I'll revert the commit on the next build.

For now guys, you can fall back to the previous version if you encounter any problems.
[ONE Original Android Development] husky69:
Used v5 for a day or two, didn't find battery drain increased, but touchscreen accuracy improved seriously.
[ONE Original Android Development] gianton:
[MENTION=5190317]fermasia[/MENTION] Just finished setting up v5 with Omni ROM 05/16 build, everything is running smooth. GPU idles at 330 MHz where in all other CM based kernels idles at 27 MHz. Is this a known bug?

Thanks for your hard work.
[ONE Original Android Development] husky69:
Maybe the effect of the aforementioned (and now abandoned) modified synaptic driver?
[ONE Original Android Development] fermasia:
Looking into it and some new changes. Can anyone confirm if this behavior is presente on previous builds or in stock Omni kernel?
[ONE Original Android Development] gianton:
I will dirty flash the stock kernel and check. Also lost 15% overnight with v5, new touch drivers in kernel causing this. Hope you'll revert the previous drivers in next release.

Edit: stock kernel idles at 330 MHz too.
[ONE Original Android Development] fermasia:
Then perhaps we can ask maxwen in Omni's thread and see if he can comment anything about it.
[ONE Original Android Development] DerRomtester:
Maybe the sysfs is reporting it wrong

https://github.com/DerRomtester/one_plus_one/commit/5fe8efb605bf42746584adf61fe471afe2aa2f8c
[ONE Original Android Development] fermasia:
Yeah, I agree, I'll test a build with that and see.
[ONE Original Android Development] aPollO2k:
Is f2fs support built in?
[ONE Original Android Development] fermasia:
Not quite yet, no.
[ONE Original Android Development] fermasia:
Version 5.1 released

New version is out, here's the changelog:

- Reverted new touchscreen firmware (due to battery drain)

- Added and tweaked franciscofranco's thermal driver

- Added Faux's simple GPU algorythm

- Fixed incorrect GPU idle freq sysfs reporting

- Added some randomness tweaks

- Synced to up-to-date Omni's source

You'll find the donwload link in the second post.

Cheers :good:
[ONE Original Android Development] markvd90:
Could you also do a build with the new drivers? My phone is nearly unuseable without it:(
[ONE Original Android Development] nadiros:
V5 has the drivers you want. Unusable phone vs latest tweaks....easy choice
[ONE Original Android Development] fermasia:
Indeed, you can use V5 for now. I'll try a 5.1 build with the new touchscreen drivers as soon as i can.
[ONE Original Android Development] fermasia:
You'll find a new 5.1 version with the new touch driver in the second post. Enjoy :good:
[ONE Original Android Development] markvd90:
Thanks man, really appreciate it.
[ONE Original Android Development] fermasia:
Can somebody provide feedback about the last versions? I'd like to know how it's performing on other's devices.
[ONE Original Android Development] gianton:
Working great, just flashed so can't comment on battery life yet. I'm running the normal build with old touch screen drivers on latest Omni unofficial build. GPU idles at 27 MHz now, but I'm missing vibration feedback setting.
[ONE Original Android Development] nadiros:
Same as gianton [emoji6] Running smooth on latest Omni with ondemand and faux's simple GPU. Battery seems OK so far. Thanks for your time, and sharing.
[ONE Original Android Development] tmimaesk:
Hello, I am just wondering,

does verison 5.1 include the new touchscreen driver without the battery drain? or is it the first touchscreen driver that had the battery drain.. Thanks!
[ONE Original Android Development] nadiros:
5.0 had the old battery drain ones. 5.1 reverted them. Guess we'll have to wait and see if there'll be a 5.2 [emoji6]
[ONE Original Android Development] fermasia:
New Version released (5.2)

Hi everybody.

Version 5.2 is up (check the second post for the download link). I've included the new touchscreen solution implemented by CM and did some minor tunning in Bricked Hotplug.

Enjoy :good:
[ONE Original Android Development] nadiros:
Thanks so much for the update OP. Running flawless so far on the latest Omni. Off topic but does anyone have info on this latest CM touch driver? Synaptics drivers would be closed source, so how have they fixed....or have they fixed these touch issues? The fix a few weeks ago seemed to boost my screen even though I don't suffer from ghost touches etc. With this fix I don't think there's a difference. Just curious, and a search didn't come up with boo.
[ONE Original Android Development] fermasia:
It looks more like a workaround on how the firmware is implemented than a different firmware, but I'm just guessing here, maybe someone can give us a more accurate clarification.

About it's effects, I think someone having touch issues with the old firmware should report about how this new solution actually works.
[ONE Original Android Development] daryelv:
I'll give it a test. My phone definitely has touch issues when it warms up. It's been 100+ degrees here lately, so it will be a challenging test. The CM12.1 fixed my touchscreen issues, but I was having 3-4 reboots during the day because of other issues in that ROM. Will let you know how it goes.

-Daryel
[ONE Original Android Development] fermasia:
Great, please let me know when you have any results to share. Thanks.
[ONE Original Android Development] daryelv:
Running solid today with no touchscreen issues so far. Did some Ingressing around noon today and saw the battery temp go over 100. Usually when it gets above 90-95 I start seeing touchscreen issues that require a reboot. I hope others are seeing the good results I am.

-Daryel
[ONE Original Android Development] markvd90:
Sadly, for some reason the kernel ain't working for me. Still touch issues.

Which is strange, because all other kernels with the per panel firmware are working great.

Not whining, just giving some feedback :thumbup:
[ONE Original Android Development] ghmail2:
has this kernel wifi bugs? it disconnects the wifi in sleep

来自我的 A0001 上的 Tapatalk
[ONE Original Android Development] nadiros:
Works great for me. No disconnections. Is WiFi even a kernel thing?
[ONE Original Android Development] adinkwok:
Yes, the wifi drivers are located within the kernel
[ONE Original Android Development] fermasia:
There's been no changes to kernel wifi drivers (which is true, they are kernel side, yet not everything about wifi is kernel side - let me disagree).

It works fine for me right now, so no, this kernel hasn't got "wifi bugs". But I'll be trying a prima drivers update in my next build so you may try and see how it goes.
[ONE Original Android Development] fermasia:
Thanks for the feedback but sounds weird. Try the new build from eagleyetom that has the touchscreen fix (same I've merged) inbuilt and see if you still have problems. If so, it should be something about how the fix is interacting with Omni's code instead of CM's, but would be weird if it works well for everybody else and not for you.
[ONE Original Android Development] markvd90:
Just flashed his latest build, touchscreen is flawless..:confused:
[ONE Original Android Development] nadiros:
Hey just figured I'd touch in about 5.2. Been running it since its release and its been a pleasure. I find when discussion here is quiet, some times it's just because everything works. Thanks fermasia for the build [emoji6]
[ONE Original Android Development] fermasia:
Thanks for the feedback!
[ONE Original Android Development] fermasia:
Version 6 (beta) - Released

New version is up. Link's on the second post, changelog on the third one. As usual, feedback about performance and stability will be apreciated. Enjoy! :good:
[ONE Original Android Development] nadiros:
So far, so good. Its labeled as v4 but we know its v6.

Was fiops always the default scheduler? I prefer it anyway so one less thing to adjust. Will report after a few days of use. Thanks for sharing.

*edit

Is it just me, or is there no 1900MHz step? I usually under clock to this frequency. Seems odd.
[ONE Original Android Development] fermasia:
1. Bogus, as I cleaned up commits I wiped the one updating the localversion!

2. Not allways bit for some tome fiops has been the default sched.

3. I think I've messed up the freq table. I need ti sort that out or revert all that.
[ONE Original Android Development] hp13:
Great kernel with Omni Rom. This combo beats any CM 12.1 rom + kernel hands down. This is my opinion. Thanks for you great work. Fluidity is great on this. I will test out the battery (screen on time) and report back in few days.
[ONE Original Android Development] fermasia:
Version 7 - Released

Guys, I've made some major changes. As we are moving to official nightlies for Omni, I thought this kernel should go back to what it was originally meant for - stay close to Omni's stock and provide useful optimizations to enhace the experience. So well, I decided to remove a bunch of things (both Mako_Hotplug and Bricked_Hotplug, aditional cpufreq govs, Franco's thermal driver and sound contro) keep the eseentials and work onto stock's hotplug driver (CpuQuiet) and the stock's governors. I also compiled with google's toolchain and found that results are better (using 4.9 instead of 4.7 or 4.8 that's what Omni is using by default). The result, for me, it's a simpler kernel that's performing smooth enough and much more battery-wise, and well, closer to Omni's source code. Hope you agree about these changes, and of course, profit!

You can find a more detailed changelog in the thrid post and the link to download in the second post.

Cheers :good::good::good::good:
[ONE Original Android Development] nadiros:
Well thanks, and I can appreciate your philosophy here. Its all too easy I imagine getting caught up adding in everything but the kitchen sink. I've ran your kernels for awhile and made the move from v5.2 to this latest one. Looking forward to testing it out. Thanks for sharing.

*edit

Update - around 24hrs and running like a champ. I've had other factors affecting my battery so I won't comment yet. I run underclocked, smartass with some tweaks, and fiops. Performance is fantastic.
[ONE Original Android Development] dankatz1:
Just popped in to say thanks.

Using version7 since last night.

While playing an online MOBA game with interactive governor the phone (not surprisingly) turned really hot.

Changed to smartmax governor and zen scheduler and everything is smooth and cool while doing the same stuff or playing the same game on LTE!

Thanks again.
[ONE Original Android Development] fermasia:
Thanks for the feedback. After a few cycles I'd appreciate to know how your battery drain behaved.
[ONE Original Android Development] fermasia:
In this last version I went back to Omni's stock thermal driver, I'll probably add back franco's so I'd appreciate if you could compare them under the same conditions and tell me how it went. Thanks!
[ONE Original Android Development] dankatz1:
Eagerly waiting!
[ONE Original Android Development] nadiros:
Idle drain seems to have improved. Like everyone else, battery life is sporadic on lollipop for me between play services and mobile radio active.

I really appreciate the screen control and option for fiops scheduler. I underclock to 1958Mhz CPU and 462 GPU with little to no noticeable difference in performance. Using Kernel Auditor to tweak. I do game just not super resource intensive titles. Approximately 5hrs SOT is what I'd say I'm getting per my usage. Ideal kernel, on a great ROM.
[ONE Original Android Development] chrcol:
kernel works fine but the UKM-Mod app after installing in recovery doesnt show up in app drawer.
[ONE Original Android Development] fermasia:
UKM is not an app, you'll need to install Synapse from the playstore after flashing the zip.
[ONE Original Android Development] hp13:
V7 download link is down. Can someone please reupload it?
[ONE Original Android Development] fermasia:
Lol, I fu**** up the link when editing the post. Check it now, it's solved.
[ONE Original Android Development] nadiros:
[MENTION=5190317]fermasia[/MENTION]

Hey in case you don't check your PM's, you'd mentioned a version of your kernel that runs with Oxygen firmware? I'd love to try it if you care to share [emoji41]
[ONE Original Android Development] fermasia:
I saw your PM minutes ago and have just answered it. I'll be having a new version ready tomorrow (or later tonight, maybe). The new firmware is giving no trouble but you won't notice any difference unless you had touchscreen issues (and I'm not saying that OOS firmware will 100% solve it either!). If not, I can't notice any differences at all.
[ONE Original Android Development] fermasia:
New version available (7.1)

New version uploaded - link's on the second post and changelog in the third (but's basically just trying out OOS firmware).

Enjoy :good:
[ONE Original Android Development] OmegaBlaze:
Just to let you know, your latest build works fine on AxxionPop ?
[ONE Original Android Development] musklor:
Do you know which ROM have an omnirom base?
[ONE Original Android Development] OmegaBlaze:
Axxionpop. Darkobas. Omni (Official). That's about it.
[ONE Original Android Development] Knox316:
[MENTION=5190317]fermasia[/MENTION] or anyone, do you have any specific battery friendly profile to use on synapse for this kernel?
[General Topics] jamie3000:
Hi All,

So here is my situation. I can generate huge amounts of mobile traffic. All legit, nothing dodgy. I've tried a lot of affiliate networks and most of them are poorly ran with even worse systems. So I'd like to work directly with a developer who has a few games under his belt that I can promote for him/her.

I'm willing to give a free trail of the traffic to see if its a good fit for you as long as you're serious about the venture.

If anyone is interested then please add me on skype and we can talk business :) jmcostello21
[ONE Q&A, Help & Troubleshooting] tenyrnote:
After I received my bamboo style/swap my mic for in and out going calls suddenly stopped working. I had followed the directions for installing the new back cover that were provided by OnePlus one which included the first step, which was to place my headphone jack halfway down the hole and gently bend to create a gap in order to provide a space so I could insert the plastic tool to remove the current stock cover. Long story short, I realized that my headphone stem had broken off at the tip and was jammed in the hole making the phone think that I always had the headset connected and therefore the mic on calls was inoperable. I then took the back off and removed several screws to remove the plate that covered the 3.5mm jack hole. I carefully took tweezers and removed the broken tip and put the phone back together and voila... my phone mic is back to working order. I am not saying that this is the issue with everyone or anyone, but it fixed my issue.
[LG G Pro 2] kevinngck1:
My F350S is working well with root (no bugs so far in 3days heavy use)

I am not sure this method will work on F350L/K, D838.... so be careful. And sorry for my bad english.

Note: I am not responsible for any damage do it at your own risk..

Here is what I've done:

Instruction:

1) Flash back to LG GPro2 Stock 10e KKrom by using TOT method

2)Root it

http://xdaforums.com/showthread.php?t=2670428

3)Flash Philz touch recovery (LGRecovery_F350.apk)

Download Link: https://www.androidfilehost.com/?fid=95784891001610872

4)Boot into Philz recovery, wipe/factory reset then flash this (F350S Lollipop update zip, BIG Thanks to [MENTION=6277132]jk02031[/MENTION])

Here is the thread from XDA by [MENTION=6277132]jk02031[/MENTION]

http://xdaforums.com/lg-g-pro-2/general/f350-s-k-l-lollipop-update-zip-t3018436

5)IMPORTANT!!!! After apply the update.zip don't reboot your device!! Flash supersu immediately !!! (SuperSU-v2.37.zip)

Download link: http://pan.baidu.com/s/1nt5KBRN

6)Reboot your device and well, your device rooted.

Screenshots:
[LG G Pro 2] glasseffects:
This has become the preferred rooting method in absence of custom recovery. you could also flash Xposed for Lollipop while you're at Kitkat.
[LG G Pro 2] TomeG2kc:
Sorry, how I should understand your comment about Xposed? Is this mean, I can root Lollipop BEFORE installing, by Xposed for Lollipop?

Please, explain.

--==||==--

WySwiftKey'owane i wyTapatalk'owane z mojego LG G Pro Drugiego Wspaniałego.

--==--

Swiftkeyed and Taptalked from my Great LG G Pro The Second

==

TomeG2kc aka Tomasz G.
[LG G Pro 2] glasseffects:
In the absence of custom recovery for Lollipop rooting requires one to have a rooted Kitkat with custom recovery installed. Now to have Lollipop, we flash a flashable variant of Lollipop and THEN while we're still in recovery, we flash SuperSU. This is perhaps how you have a rooted Lollipop and most of us followed this process.

Since we now have Xposed for Lollipop, it can be flashed at the same stage when we flash SuperSU. So when we reboot the device, we have a rooted Lollipop with Xposed preinstalled.

Hope this clarifies any doubt.
[LG G Pro 2] TomeG2kc:
I see, so this mean, we have only one chance to install some .zips thru recovery - after install Lollipop but before reboot?

--==||==--

WySwiftKey'owane i wyTapatalk'owane z mojego LG G Pro Drugiego Wspaniałego.

--==--

Swiftkeyed and Taptalked from my Great LG G Pro The Second

==

TomeG2kc aka Tomasz G.
[LG G Pro 2] glasseffects:
As long as we don't have custom recovery for Lollipop, this limitation persists.
[LG G Pro 2] kevinngck1:
You can flash this via adb to get custom recovery back:

http://pan.baidu.com/s/1mgHZuLM
[LG G Pro 2] samtheman:
Thank you for the link... would you mind explaining exactly what the file is and if it will work with a d838? I would love to have recovery for my LG Pro2 with Lollipop :)

Also how do you install a zip file using ADB? Any online guide I can find says you need to boot the phone into recovery first (which of course we dont have)
[LG G Pro 2] samtheman:
I couldn't contain my excitement so went ahead and installed the linked recovery. I installed adb on my pc, set my LG pro 2 to usb debugging, extracted the linked zip to my desktop and ran the .bat file. Within 20 seconds I had a custom recovery on my Lollipop :)

I haven't tried installing anything with the recovery yet - but it seems to be working so far with my 838 32g version.

Manny thanks!
[LG G Pro 2] kevinngck1:
Sorry for my bad that i have not provide any instrustion for this zip. A big thanks for your test, comment and it is a huge help to another gpro2 user!! I will edit this post ASAP for more clearly guide.
[LG G Pro 2] glasseffects:
Thank you for the information. I wasn't aware of it. It appear to be intended for F350. Can it be flashed on D838?

Thanks.
[LG G Pro 2] kevinngck1:
As [MENTION=446079]samtheman[/MENTION] say, yes you can
[LG G Pro 2] Ahmed Xperia p:
Can you please upload this recovery on some server? i am unable to download from the link :eek::confused:
[LG G Pro 2] samtheman:
I think it's best to direct that request to the OP who first posted it - kevinngck1.

If he wants me to upload it somewhere else I will.

All the best
[LG G Pro 2] Ahmed Xperia p:
nevermind .Managed to download somehow. Thanks anyway
[LG G Pro 2] amir.:
Can u please upload it on mega?? Thanx in advance..
[LG G Pro 2] Ahmed Xperia p:
May i know how you flashed this recovery? I tried adb,fastboot. flashify but no luck. Any help or tutorial would be appreciated. Thanks F350s Future 3.1 rooted

---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------

Ok
[LG G Pro 2] vy69gazerock:
Hello, is this recovery work to official lollipop that updated via KDZ?
[LG G Pro 2] xb360:
Is this recovery in English or Chinese?
[LG G Pro 2] samtheman:
It is in English on my device
[LG G Pro 2] xb360:
Thanks for the reply. I'll try this method.
[LG G Pro 2] yplim2300:
Does it work for other ROM ?
[LG G Pro 2] atir usman butt:
Lolipop custom recovery?
[LG G Pro 2] kotty:
thanks for the guide ..my phone was rooted now with lollipop n i install SD card fix also working .I'm using D838 singapore set 32GB.

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

remember the ROM must put at internal memory ..the recovery can't read ext SD card ..
[LG G Pro 2] zoreli:
Im on Lollipop 5.0.1 D838 and that not working .
[LG G Pro 2] kotty:
actually this method quite easy ,just flash back to KK ,install towelroot apk to root ,then install recovery apk .and u ready to flash lollipop ROM with root ..
[LG G Pro 2] zoreli:
But when you on offical 5.0,1 D838 , there is no way to ROOT device :confused:
[LG G Pro 2] kotty:
i think u need to flash back to kitkat first then follow the step ..

---------- Post added at 07:36 PM ---------- Previous post was at 07:32 PM ----------

sorry forget to mention that i flash this http://xdaforums.com/lg-g-pro-2/development/stock-pure-tw-5-0-1-32g-flashable-t3028701 after install recovery apk ..
[XPERIA X10 Q&A, Help & Troubleshooting] mroczek123:
Hi. I've done something stupid xD. When i tried to flash kernel to stock i didnt exclude baseband and now i have (no service) problem. In about phone shows baseband version 2.1.71. Whats more interesting, phone finds network operators normally but when i try to connect (phone dont connect automatically :/) shows "your sim card doesnt allow connection to this network". Thanks for any help in advance ;).
[GiONEE Elife E7] Jerry69:
I can't find any! What is the latest version? I have on my phone software version e7_031_V5831

I need some .zip roms to flash with twrp!
[Note Edge Q&A, Help & Troubleshooting] lightdelegate:
hi

i'm about to buy and just realize that there are again so many models ...

i am in Thailand and there is a F model.

in my note 4 i have the F and i know its is the European model but now i see there is also model F ...

from the other side i see that F and FY have same Roms so is it the same model ?

funny but couldn't find it by searching the net or the forum.

thanks in advanced for your answer.