yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] dallie:
Hey, could you please fix the link, alvast bedankt hé! :)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Churchill:
Is it available or not the link is still broken ??
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Mesh:
Is this rom still available somewhere or does someone still have it on his or her hd somwhere? Really could use this in case I need to send back my hermes (6th time allready)...
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] marcoryn:
Can someone re-up the image plz?? My Hermes is going to t-mob for the 3th time :mad:
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] roboraver:
Same here, I need the splash screen, my Vario has just died (Freezes on WM6 opening page), it was working perfectly after upgrading !
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] oltp:
ori wm6 now available

check the TMO website or the WM6 forum for the original Dutch TMO rom. You should be able to extract the splash yourself and maybe the rom can solve your probs.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] berkens:
Hi All,

Here the link to Dutch WM6 ROM for the T-Mobile Vario-II .

http://member.htc.com/ruudownload/t-mobile/TMobileWM6Step1-TMNL.aspx

You need to enter the serial number of your phone before you can download.

Greetings Ben...

P.S. Now I have a white screen and failing front push buttons, so I want to restore an original ROM for warranty.
[ONE Android Development] NuLLV01D:
Wow... Another Kernel! We're Blessed. Much Appreciated Mate!

FleXied from My bacon
[ONE Android Development] CounterC:
Testing now!

can you add SIO as a governer?
[ONE Android Development] Minia89:
Yes, I'll add it right now. New build will up in an hour
[ONE Android Development] CounterC:
I mean scheduler, not governor
[ONE Android Development] DerRomtester:
Your Kernel is based in Franco kernel. I would say you should post it to the android development section and not to the original android development section.
[ONE Android Development] Minia89:
I think you're right :p I was wrong posting it here. I hope some mod will move the thread in the right section.

I've also edited the OP. In the credits I've wrote "Tyr" instead of your nick :P
[ONE Android Development] CounterC:
V2 only change is SIO scheduler?

Edit: Ok I read the OP now

Edit: [MENTION=6519682]Minia89[/MENTION] I don't have the SIO scheduler in V2
[ONE Android Development] DerRomtester:
No problem. I was asking a mod and he said that my thread belongs to android development section because it is based on franco kernel. :D
[ONE Android Development] Minia89:
Tomorrow I will look better at the code, the sched is in but I can't see it in Synapse too (in trickster mod is available). Maybe uninstalling Synapse and reflashing UKM will help
[ONE Android Development] CounterC:
That's the solution!
[ONE Android Development] Minia89:
Glad to see it :D
[ONE Android Development] CounterC:
I've tried elementalx governor but it gives me a lot of reboots. Changed to smartmax and everything is fine. Maybe you should look into elementalx. You are the only one that has it implemented, maybe it isn't ready for our OPO...
[ONE Android Development] jsyl:
I've been on elementalx since the release of the kernel, no reboots so far.
[ONE Android Development] CounterC:
Can you be so kind to share Synapse screenshots?
[ONE Android Development] jsyl:
Everything default, elementalx w/ undervolt -60
[ONE Android Development] Minia89:
I can confirm that I've no problems so far using elementalx governor ;) Even if it's not very believable, said by me
[ONE Android Development] CounterC:
Can someone please post screenshot of the default elementalx settings? My settings always change...
[ONE Android Development] Setting.Out:
I noticed that apps seemed to load a bit slower, I had some shuddering/lags in scrolling.. I've tried several configurations, but can't seem to find the right one?? I was running this on TeamUB with no other modifications.. Does this have touchboost?.. No other issues with all govs/schedulers.. It felt like I flashed a wrong kernel (back in the old days, aosp and cm weren't compatible, and your rom would act gummy)... I've tried reflashing the rom and kernel again clean and still the same.. I'll try another setup, what rom did you test with?
[ONE Android Development] mmurphmsu:
So when I flashed v3 of the kernel my about kernel isn't customized or is this correct?
[ONE Android Development] dmd3746:
Since NE1 when I flash the kernel it doesn't change, the stock kernel is still there instead of this one, I don't get an error saying it didn't work, has anyone had this issue, I have tried on Temasek, BlissPop, CM Resurrection Remix, and Euphoria Roms, am I missing something? I know I didn't pit any helpful info to help me but I don't get any errors if therd Is something I can do I am more than happy to do it. Also every install was clean fully wiped , factory reset, wiped system, dalvik, cache
[ONE Android Development] mmurphmsu:
Mine hasn't changed since then either. Glad I'm not the only one. I thought I was going crazy haha.
[ONE Android Development] Minia89:
For me the kernel version changes everytime I flash it, I don't know why this thing happen :confused:

Wipe dalvik and cache and try again to flash it.

Maybe a clean install of cm12s can help
[ONE Android Development] Minia89:
This late evening (UTC +1 lol) I will upload new version with zzmoove. I'll introduce neobuddy state_notifier instead of faux powersuspend or lcd_notify
[ONE Android Development] mmurphmsu:
Ok, I just wiped dalvik then cache, flashed ver2 then wiped dalvik/cache again. I'll report back what happens.

EDIT: After reboot and checking it still lists the stock kernel. Do I need to have the UKM installed for it to show up correctly?
[ONE Android Development] dmd3746:
What ROM are you running from what I understood from reading through is that this kernel should work with most Roms CM based, I am not running cm12s, will it not work with others now because it always has in the past?
[ONE Android Development] mmurphmsu:
Well I was on CM12S. Now I'm on CM12 nightlies. I flashed NEv3 and it still says it has the stock kernel but when I flashed this newest kernel it didn't say it failed. I wiped dalvik/cache before and after.
[ONE Android Development] Minia89:
Try to flash UKM and let me know
[ONE Android Development] mmurphmsu:
ok I'll try that. Can you relist on of your kernels that doesn't start with NE? I'm fairly certain those worked. If V22 is the latest one of these I'll try that.

EDIT: flashed NEv2 and UKM and about kernel still lists stock. I'll download V22 and try that. If it helps I'm on CM12.1 from today.

EDIT2: Still showing stock kernel in about phone but kernel flashes just fine. I am really stumped by this one. I've never seen this before and I've been flashing stuff for years. I may try to wipe everything and reinstall the latest CM12.1 nightly and see if it works.
[ONE Android Development] Minia89:
NEv3 is up

NEv3 introduce: state_notifier instead of powersuspend, zzmoove governor, modified all the hotplugs to work with it, removed alucard hotplug for now, VFS cache pressure 50, many commits (include latest from cm), Makefile modifications, new modified UKM
[ONE Android Development] mmurphmsu:
So there must be an issue with this kernel. I wiped everything off of my phone, put the 12.1 nightly from 4/22 and 5.1 GAPPS on my phone, booted and let it setup everything. I then went to recovery and flash this latest kernel and my about phone >> Kernel still said stock kernel was installed. I got some help from the CM 12.1 thread. They said AK kernel worked. So I flashed it and it shows up under my about phone >> Kernel now instead of stock.
[ONE Android Development] dmd3746:
I wiped everything this moring and did clean install with Blisspop, and CM12.1 nightly and tried flashing kernel NE3 with UKM, and still stock kernel? have you made any progress
[ONE Android Development] Minia89:
I can only say that with over 150 downloads of version NEv2, no one else has reported this issue. Even for me every version flash correctly.

Edit: I've tried to flash AK over Metallized and flash Metallized back and even in this case it works correctly. When CM 12s came out I installed it over stock and no issue. I don't know what to say to you. Anyone else has this issue? Apart dmd3746 and mmurphmsu
[ONE Android Development] mmurphmsu:
I'm not griping don't get me wrong, I love this kernel when I could use it. It was better on battery than Franco's. I just don't have a clue as to why it won't flash. I don't have xposed installed or anything extra besides the ROM and GAPPS.
[ONE Android Development] molonad:
Hi I tried your kernel, great work but simple ondenand doesn't work on cm12s and I have this error too, but this second error is not important for me, thanx
[ONE Android Development] Minia89:
I'm afraid because I don't have any idea about I can do to solve this issue that you face :( even because it's not a common issue (two users only have this problem).
[ONE Android Development] Minia89:
I'm on 12s too, simple ondemand is working here. Have you wiped cache and dalvik before flashing the kernel? And what UKM version are you using? If you have flashed other UKM versions before, try to flash the latest one in the op (3.8.1_Metallized).

Edit:

You nor have the voice color enhancement visible in synapse, there is something wrong with UKM. Try to wipe and reflash UKM_Metallized

Edit2: or you can simply use kernel adiutor that works great eventi with zzmoove gov profiles
[ONE Android Development] dmd3746:
I am not gripping either I love this kernel and i know anything these guys do is for fun and I greatly appreciate it, that being said of I flash V22 it works it is only on the NE kernels, I wish there was an error message, i will post a screen shot after I flash NE3 maybe there well be something there that some one else sees that knows what there looking at.
[ONE Android Development] mmurphmsu:
I'm right there with you. If I knew how to do better troubleshooting I would do that in an instant.
[ONE Android Development] Minia89:
NEv4 is up

NEv4 introduce: power efficient workqueues (synapse on/off), latest cm commits, mpdecision disable at boot
[ONE Android Development] kOoL tHuG:
Does this Kernel work on Roms based on Android 5.1.1?
[ONE Android Development] Minia89:
Yes it does
[ONE Android Development] kOoL tHuG:
K. Thanks. Now coming to my other question.

I had 5.1 Blisspop Rom with your Kernel installed working Perfectly & Smooth.

Then i dirty flashed to 5.1.1 Blisspop and now when ever i install the Kernel TWRP says install complete.

But when i go check i still have the Stock Kernel Installed. Why is that happening?
[ONE Android Development] Minia89:
Sorry for the dumb question, but do you have flashed again the kernel after flashing blisspop?
[ONE Android Development] kOoL tHuG:
Sorry for the Miscommunication. But by Install i meant i flashed the kernel after i dirty flashed the new rom.

FYI i havent installed the NEv4 Version. It just came sometime back. I had Nev3 installed and have been trying the same on 5.1.1 Rom
[ONE Android Development] Minia89:
I'm just downloading latest blisspop, I'll let you know
[ONE Android Development] kOoL tHuG:
Ok
[ONE Android Development] Minia89:
Just installed Blisspop, kernel shows up correctly

I've wiped system, cache and dalvik then I've flashed in this order: Blisspop, gapps, kernel and UKM_Metallized. I can only say to do like me and try. I have no idea about this issue, for me every version flashes correctly.
[ONE Android Development] kOoL tHuG:
I just tried to flash NEv3 and it still didn't show up.

Then i tried to flash Nev4.

Surprisingly NEv4 flashed and showed up.

P.S - I guess this was not happening coz i dirty flashed.

But u did a clean flash so it worked i guess.

Thanks for the support. Appreciated. :good:
[ONE Android Development] byAidan:
I'm new to this kernel and I'm already amazed, everything is so smooth and fast wow! ;)

Keep up the great work :)
[ONE Android Development] Ofthecats:
Hey all, I was wondering how the wave governor works. Thanks
[ONE Android Development] Minia89:
Almost is a governor based on conservative, but tuned to be smoother ;)
[ONE Android Development] darsh1994:
I have never flashed a kernel before but I have a rough idea about it! I'm shifting to stock cm12. Can anyone help me out. I'll flash it directly or clean flash?

And how is a custom kernel better? Sorry for a nooby question:p

Also what is f2fs? I've been wanting to know that :confused:
[ONE Android Development] Minia89:
You can flash directly on top of cos 12, do a wipe cache and dalvik just in case. Remember to flash UKM_Metallized from kernel folder also, it will give you the necessary support to use synapse app from play store, needed to tune the kernel settings (or you can simply use kernel adiutor without flashing UKM). A custom kernel can be better because it can give you more choices, resulting in better battery life or performances or both :D and is much more upgraded compared to stock one. Make a long story short, f2fs is a "new" system partition that can increase your smartphone performances in r/w. You can use it only if you format your opo in this system partition and if you use a dedicated rom who is able to use it.
[ONE Android Development] darsh1994:
I won't mind doing a clean flash!

So I'll full wipe

Flash ROM

Flash SuperSU

Wipe cache and delvik

Flash kernel

Then the umk from the OP

Then reboot. Correct?:D

P.s. Thanks for all the help!
[ONE Android Development] Minia89:
Right ;) if you do a clean flash is not needed to wipe cache and dalvik again :p
[ONE Android Development] darsh1994:
Thank you. Will get back soon after flashing:D
[ONE Android Development] mmurphmsu:
Just an FYI, I did a complete wipe last night, data, system, internal storage and formatted data, installed latest CM12S, let it install all my apps, then tried flashing Franco's R42 and it worked. Then went back into recovery and tried to flash your latest kernel and it didn't work.
[ONE Android Development] dmd3746:
Update: I have always flashed in this order, ROM, Firmware if needed, gapps, kernel , ukm, Supersu,

This time I flashes kernel last instead of supersu and kernel was there correctly, very excited I can use it again, I would be very shocked of that was a coincidence.
[ONE Android Development] darsh1994:
I don't need to wipe internal storage right? :/
[ONE Android Development] Minia89:
Right ;)
[ONE Android Development] darsh1994:
Done! Cm12 is a bit buggy :/

Please suggest the best settings in synapse :p
[ONE Android Development] darsh1994:
I guess something went wrong with the flash! It's lagging and the benchmark score also went way low to 41727:confused:
[ONE Android Development] Minia89:
For high benchmark scores use performance governor (antutu score doesn't mean nothing, anyway). For me and reading at user's posts, the kernel doesn't lag. I'm on stock settings (the kernel lag a bit during the boot and for something like a minute after, then works great).
[ONE Android Development] darsh1994:
This is all I get
[ONE Android Development] Minia89:
CPU performance governor :D
[ONE Android Development] Minia89:
NEv5 is up

NEv5 state_notifier changes, latest cm commits, introduce: uberdemand governor
[ONE Android Development] darsh1994:
No need to flash UKm again right? Sorry first time:(
[ONE Android Development] NuLLV01D:
If You've already flashed it...then there's no need
[ONE Android Development] byAidan:
I flashed NEv5 earlier and it's working great, it also has stopped my wifi from disconnecting once my phone is locked, thank you so much! :good:
[ONE Android Development] indian84:
NEv5? Did I miss something??

EDIT - Yes, I did. Flashed now.. :)
[ONE Android Development] Minia89:
I think that I'll change default governor for next release. I'm testing zzmoove by zanezam with profile number 6 (zzopt) and is working great.
[ONE Android Development] cerealguy:
[MENTION=3279788]ZaneZam[/MENTION] is my idol since S3 days! :D

Btw thanks for sharing your kernel...it's very good!!![emoji106] [emoji106]
[ONE Android Development] CounterC:
How is battery life?
[ONE Android Development] cerealguy:
4-5 hrs of screen on time with a middle usage( whatsapp, facebook, tepatalk, little games) and.....it's f***ing smooth!!!!
[ONE Android Development] darsh1994:
Tried overclocking?:p
[ONE Android Development] Hiro Nakamura:
Hello,

how do i use f2fs with this kernel?

My guess would be i wipe everything and format data and cache to f2fs. Then flash the latest nightly with your kernel, am i right?
[ONE Android Development] molonad:
smartmax :)

hey :) smartmax governor doesnt work like it should , all cores are online all the time , on all kernels i tried is smartmax bugged , only on cm12s, so not really good choice to set this to default governor :-/ , is cm12s officially supported by you ? becouse ak kernel isnt :)

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

Netxt bug i found is hellsactive doesnt work , when i choose it , device was restarted
[ONE Android Development] Minia89:
I think I'll change default governor on next release ;) hellsactive works here! I don't have issues here, so I think it's not something related to kernel. Cm12s supported here. I was on it until two-three days ago and everything works good.
[ONE Android Development] molonad:
i tried it after clean flash with all stock settings... so dont understand it
[ONE Android Development] CounterC:
Also simple ondemand gives reboot on applying in Synapse under GPU governer...
[ONE Android Development] Minia89:
Does Hellsactive works for you? I have no issue with it. Yes, simple ondemand is bugged, don't use it for now (also on AK doesn't works) and if you want your battery last longer, use simple governor tunables on msm-adreno-tz, it works great. Simple ondemand is not needed with it ;)
[ONE Android Development] Minia89:
Tomorrow I will modify smartmax because I've seen that it doesn't load his parameters correctly, eventi if is not related to cores online alla the time. This issue happen only with bricked hotplug, the governor isn't "fully compatibile" with it and I think that there's nothing to do about it :D with msm_hotplug, intelliplug and mako, cores shut down like they would do
[ONE Android Development] ZaneZam:
your idol? oh thx that's very nice but too much *g* i'm really just a everyday normal guy : https://www.youtube.com/watch?v=5PsnxDQvQpw :D

not much to "idolism" here *g* anyway i'm happy to be able to make u guys happy, that's my real motivation to go on with things

(beside of the possibility to tune my own devices a little bit *g*) hope u can also enjoy upcoming stuff, even if it takes a bit.. ;)
[ONE Android Development] Mbennett156:
NEv5 has a very significant lag when it comes to turning on the screen - takes up to 3 or 4 seconds to do so
[ONE Android Development] Minia89:
Activate wakeup boost in synapse
[ONE Android Development] byAidan:
Just flashed NEv6, seems to be running great, so fast like always.

I will let you know if anything else happens!

Thanks again for the hard work :good:
[ONE Android Development] Minia89:
NEv6 is up

NEv6 introduce: HYPER governor, latest UBER toolchain 6.0, tuned interactive governor, tuned smartmax governor, latest alucard governor changes, latest impulse governor changes, fixed simple_ondemand gpu governor (now works, no more reboots choosing it)
[ONE Android Development] velvetwafer:
Bootloop with Temaseks 12.1 on F2FS
[ONE Android Development] Minia89:
NEV6 up again

Fixed bootloop with f2fs
[ONE Android Development] Minia89:
NEV6 up again lol

This time is the right version, sorry guys.
[ONE Android Development] Gormsen:
I'm having a really strange issue. I can't for the life of me seem to flash the kernel. I go into TWRP, wipe cache and dalvik, flash kernel zip and ukm, then reboot. But when I go to about phone it still says Franco r42, so does FKU, and Synapse throws me an error.

Anybody got any ideas, besides full wipe, which I don't really wanna do ;)
[ONE Android Development] indian84:
Dirty flash your current ROM. That should get rid of Franco. Flash ukm installer. Delete synapse data.

Flash latest kernel from OP and flash ukm.
[ONE Android Development] Gormsen:
Just tried that, but now I'm just back on CM12S stock kernel.. I've never experienced anything like this.. Maybe I had a bad download? Gonna redownload and try again ;)
[ONE Android Development] Minia89:
NEv7 is up

NEv7 enabled msm-hotplug instead of bricked, tuned msm-hotplug (more conservative), tuned smartmax, tuned a bit cpu-boost: ENJOY THE SMOOTHNESS

Edit: the boot up process after wiping cache and dalvik could be very laggy and slower than normal, but don't worry about that. After the first boot everything will turn to normal :D

Edit2: version 7 removed for now. Boot up process soooo slow, kernel can't work like this.
[ONE Android Development] velvetwafer:
VERY VERY VERY Laggy....meaning...App Optimizing is not yet finished after over an hour. It works...but....well. If its finished in half an hour ill be happy :D

This doesnt feel right.

EDIT:

Awesome! Im waiting for NEv7 v2 ;)
[ONE Android Development] Minia89:
NEv7 is up (again)

NEv7 enabled msm-hotplug instead of bricked, tuned msm-hotplug (more conservative), tuned smartmax, tuned a bit cpu-boost: ENJOY THE SMOOTHNESS

if you encounter after wiping cache and dalvik a laggy app optimizing phase that seems infinite, do a dirty flash or wipe system and install again rom and kernel
[ONE Android Development] darsh1994:
Doesn't show nev7 in synapse! It is showing nev4 :/
[ONE Android Development] Hiro Nakamura:
Installing issue

When installing apps the phone gets pretty laggy and it takes minutes to install the app. I'm using the latest kernel here.
[ONE Android Development] DerRomtester:
Just set min max freq inside the defconfig
[ONE Android Development] Davey212:
Waiting...

Flashed NEv7(2) on cm-12.1-20150428-NIGHTLY, wiped cache and dalvik, at the 'Android is starting...' screen and its seriously taking like over 2 hours optimize 269 apps. :confused::confused:
[ONE Android Development] Minia89:
Nothing change :(
[ONE Android Development] byAidan:
What I did was flash the nightly, wait for the rom to boot and optimise apps (should be a lot quicker) and then boot into recovery again and flash the custom kernel and UKM :)
[ONE Android Development] Minia89:
I tought that full wiping solved the problem, but after flash with fullwipe if you flash again the kernel, it lags at app optimization. So I remove NEv2 until I fix this issue. Sorry for the inconvenience guys
[ONE Android Development] Minia89:
Yes, if you do a clean flash, kernel works good, but if you flash it without it, it stay a loooong time on app optimizing. So I remove it until I find a solution.
[ONE Android Development] byAidan:
[MENTION=6519682]Minia89[/MENTION] I've found out how to speed up optimising apps and it's very weird, if you keep tapping on your screen really fast the apps will optimise at (pretty much) normal speed but as soon as you stop tapping it all goes really slow again, you can tell this by watching the spinning icon, compare how smooth the animation is when tapping and when not tapping.

Not sure if this helps you figure anything out? :p

Anyway gotta keep tapping my screen i'm on 101/133 ;)
[ONE Android Development] abhi08638:
That's sounds like either the CPU boost driver or the governor's input boost frequency is kicking in. If its the former then you only have to hold the screen if its the latter then you need to repeatedly press it
[ONE Android Development] darsh1994:
[MENTION=6519682]Minia89[/MENTION] it's working fine for me!

In phone settings it shows NEv7 but on synapse it doesn't! Any help with that?
[ONE Android Development] DerRomtester:
Synapse is buggy just press the restart Synapse button inside Synapse vor reflash ukm.
[ONE Android Development] Minia89:
Very very weird lol. I've tried to tap the screen like you say and it speed up the boot process :D I only know that is something connected to msm_hotplug at boot instead of bricked. If I chose bricked in kernel source like every previous version, the kernel works good