yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 4i] haikalizz:
Basically just leave it like that, haven't added much stuff yet as I'm testing out doubletap2wake... It's supported in the hardware but haven't found a way to enable it yet
[Xiaomi Mi 4i] candiesdoodle:
OK. I am trying it out without changing any settings. lets see.

Btw, i cant see any menu for Hotplug in Kernet Adiutor. Is this expected behavior?

Also cant set any temperature control sliders in Thermal settings.
[Xiaomi Mi 4i] haikalizz:
Added in latest build. Look in #3 thread...
[Xiaomi Mi 4i] davtse:
Latest kernel is crazy smooth. Zzmoove hotplug is awesome lol
[Xiaomi Mi 4i] haikalizz:
[MENTION=1498291]davtse[/MENTION] As requested, undervolt is also added in latest build. Intellimm hasn't been added yet and I can confirm that dt2w is in latest build and can be turned on by [MENTION=4832023]omerjerk[/MENTION] cm12.1 build...
[Xiaomi Mi 4i] omerjerk:
To Other people -

Yeah. On/Off option is available in my build. Link to the post - http://xdaforums.com/showpost.php?p=62843688&postcount=993

Although, that option is not available with the default kernel in my build.

You'll need to flash Sensei to see that option.
[Xiaomi Mi 4i] candiesdoodle:
i noticed that LITTLE cores cant be fixed on zzmove.

Also noticed that only Core 1 is getting active on zzmove. Havent noticed other cores coming on.
[Xiaomi Mi 4i] iamnjohnson:
Do review the battery life
[Xiaomi Mi 4i] candiesdoodle:
definitely much much better. almost zero loss when screen off on 3g :)
[Xiaomi Mi 4i] haikalizz:
Hmm, zzmoove stays on Little cores here. I will look into this but the gov stays unchanged on my device. Also battery life is better than stock, achieving 2 days of battery life on normal usage and around 1.5 days for normal-medium usage with light-medium gaming.

Intelimm won't compile due to different files but I'll see if I can fix it. Thunderplug also doesn't compile, something to do with 'lcd_register'...
[Xiaomi Mi 4i] iamnjohnson:
Which ROM are you using?
[Xiaomi Mi 4i] davtse:
we need to edit the parameters for hotplug to work.

echo 0 for disable hotplug (current default setting is 1)

i'm currently trying to play around with the settings in the postboot.sh script to see if we can get it fixed (as in its currently working fine but i want it to set on boot)
[Xiaomi Mi 4i] haikalizz:
[MENTION=4832023]omerjerk[/MENTION] build... Planning to change to [MENTION=1834166]DH-[/MENTION]harald build as ant+ is working there.

I will add instructions on how to enable dt2w on main post. Any features that you want just say, I'll look into it.

Dev Roadmap :

Frandom?

Thunderplug

Updater app?

More optimizations

Upgrade to GCC6?
[Xiaomi Mi 4i] haikalizz:
I think I've disabled the hotplug in the source. Could this be another issue? How's your battery life and performance? Any better than previous versions?
[Xiaomi Mi 4i] davtse:
i dont think its an issue, i think its how it was intended to wor? im using android tuner to change the parameters and it all seems fine. the hotplug works like this

CPU 0(big) active all the time as intended

CPU4,5,6,7, activates before 1,2,3 are activated.
[Xiaomi Mi 4i] candiesdoodle:
[MENTION=1285948]haikal[/MENTION]zz does your kernel (any kernel in general) overwrite the init.qcom.post_boot.sh file?

I may have tinkered with it at some point of time so maybe that's why my phone it giving a slightly different result.

BTW, thanks for the good work.
[Xiaomi Mi 4i] haikalizz:
It doesn't tinker with any of those files. It only overrides the old kernel as of right now. I was thinking of adding a few tweaks and an updater app into the mix but not in the near future.
[Xiaomi Mi 4i] davtse:
How do you activate undervolting? I dont see any of the files/folders to mess around with lol
[Xiaomi Mi 4i] haikalizz:
Undervolting is done automatically, haven't had overheating since the new build. Also if the settings you gave is good, I will add it to the kernel...
[Xiaomi Mi 4i] reza36:
Anyone can play COC? In my device is always force close... Im using RR rom and sensei newer version..
[Xiaomi Mi 4i] haikalizz:
COC worked for a few minutes, it loaded got until the game screen then fc... It's a problem either with framework or coc itself...
[Xiaomi Mi 4i] davtse:
Seems like standby drain isn't so good. Is it because powersuspend has not been ported over?
[Xiaomi Mi 4i] haikalizz:
Might be... I'll see if it's in the source already or not. In the meantime, new build has been uploaded...
[Xiaomi Mi 4i] davtse:
I cant see the 1.7ghz overclocked option in the latest build but can see thunderplug.

You have outdone yourself 1.2.1 man. I set my zzmoove for battery savings and its still pretty smooth. Can't grumble though since I dont really game on my phone
[Xiaomi Mi 4i] haikalizz:
It's 1657mhz or 1.6Ghz, can't really set it up to 1.7 though... Got the oc code from yu yureka kernel. Thanks...
[Xiaomi Mi 4i] reza36:
in newer version 1.2.1 little core cannot change governor and frequency... is always back to interactive and min freq 800mhz..

but now im using thunder hotplug and set to quad core mode.. << hope can makes battery better
[Xiaomi Mi 4i] davtse:
I can upload my postboot.sh script if you want to try zzmoove with my settings.
[Xiaomi Mi 4i] reza36:
okay [MENTION=1498291]davtse[/MENTION] i want your postboot.sh script.. i wanna try it.. thanks bro
[Xiaomi Mi 4i] davtse:
This is my postboot script. Note that you have to unzip it and put it into your /system/etc folder and change permissions to rw r r.

I disabled thunderplug hotplugging and use zzmoove hotplugging instead.
[Xiaomi Mi 4i] haikalizz:
try disabling thunderplug first and set the governor again. Also I'm going to release new build around tommorow or the day next with new thermal config and updated powersuspend. I've also added quickwakeup. Source is updated on my github.
[Xiaomi Mi 4i] candiesdoodle:
[MENTION=6858217]haikalizz[/MENTION] i noticed that your kernel flashing zip deletes the "power.msm8916.so" file. why is that needed?

Just out of curiosity...
[Xiaomi Mi 4i] davtse:
following what you see in the code, which mode do you think is the best for powersuspend? hybrid, LCD panel or autosleep?
[Xiaomi Mi 4i] haikalizz:
[MENTION=4874882]candie[/MENTION]sdooodle we are msm8939, deleting the file doesn't do anything... It's just from the updater-script of RazorReborn...

[MENTION=1498291]davtse[/MENTION] I've been using hybrid. Don't know much about powersuspend but hybrid is ok for me...
[Xiaomi Mi 4i] candiesdoodle:
the ro.product.board property in buid.prop reads "MSM8916" :)

So i am not sure about no impact. i know we are on MSM8939; but interestingly the build.prop reads something else. Even the post boot scripts that are floating around rely on the MSM8916 aspect being read from the build.prop. the file posted by [MENTION=1498291]davtse[/MENTION] also has only one section - for MSM8916. thats why i am wondering what impact does it have.
[Xiaomi Mi 4i] haikalizz:
No impact as the line had always been there since the first version but that's just the power module I guess, the scripts relies on other things like thermal and cpu...
[Xiaomi Mi 4i] davtse:
Yea I guessed as much. My research so far has been pointing straight to hybrid as well.
[Xiaomi Mi 4i] davtse:
hmm my script is actually from one of the other threads, i just added zzmoove profiles into it
[Xiaomi Mi 4i] candiesdoodle:
This is where it came from i suppose: http://xdaforums.com/mi-4i/development/mod-frequecy-fix-roms-kernels-t3179787

its in the updater script.

Maybe helps with stock MIUI but cant say. havent noticed in custom ROMs, the error it tries to address

I guess you should remove it from your kernel updater and give it a shot. if it works fine, best to go without those two lines.

my opinon...
[Xiaomi Mi 4i] haikalizz:
Can anybody confirm that the kernel is working on their phones? I flashed the latest build but it won't boot, got into ROM then shutdown...
[Xiaomi Mi 4i] davtse:
Yea latest is working fine
[Xiaomi Mi 4i] haikalizz:
Weird... Last time was fine now it doesn't get pass bootanim... Using dh-haralds build 16/09/2015... What about you?
[Xiaomi Mi 4i] davtse:
I'm using wilson3q one i think

---------- Post added at 10:54 AM ---------- Previous post was at 10:05 AM ----------

did you have fsync on? it used to resultin data losses for me when i was using the s3.. couldnt boot like you say you cant now
[Xiaomi Mi 4i] haikalizz:
I did turned it on in the kernel... I will build new with fsync off...
[Xiaomi Mi 4i] haikalizz:
No luck... Kernel won't boot, it goes into home screen, hangs and shuts down...

- Edit

Changed the architecture config to MSM8939, it was set to MSM8916, hope thise fixes it...
[Xiaomi Mi 4i] davtse:
You will need to restore.. The data loss can't be recovered by flashing a new kernel
[Xiaomi Mi 4i] haikalizz:
Fixed it by enabling powersuspend and enabled quickwakeup...
[Xiaomi Mi 4i] haikalizz:
New build up. Changelog is in #3 post. Thanks for using Sensei Kernel, hope you guys are enjoying it. :)
[Xiaomi Mi 4i] candiesdoodle:
New thermal engine configuration file included...

Does it get used? Didn't see anything in the scripts that indicates so.

Does this one have better battery managemwnt? Looking forward to using.
[Xiaomi Mi 4i] haikalizz:
I forgot the lines. Will put in the lines tommorow along with new build...

Battery is like before, it flunctuates between 1.5-3 days of life depending on usage. Hybrid has been set as default powersuspend mode. Do we need KCAL? Doesn't seem like much use...
[Xiaomi Mi 4i] davtse:
Yup battery standby is back to the usual now. Super smooth. Wondering what GE quick wakeup function does
[Xiaomi Mi 4i] ajaxcbcb:
may i know which hotplug is recommended. my phone cant achieve any deep sleep, it keeps waking at 200mhz. :(
[Xiaomi Mi 4i] haikalizz:
Try thunderplug, it's made for octa-core devices. I've kept it to run atleast 2 cores when sleep so phone doesn't go into very deep sleep.
[Xiaomi Mi 4i] ajaxcbcb:
ah. finally got deep sleep. would like to ask whether considering to add fast charge support?
[Xiaomi Mi 4i] haikalizz:
Yeah, forgot about that. Going to add it soon along with yankactive and autosmp. Right now, keep your device under 50°c and battery will charge fast.
[Xiaomi Mi 4i] davtse:
actually i'm wondering, is autosmp still needed since you have thunderplug?
[Xiaomi Mi 4i] PavelPerm:
In your kernel dont work game clash of clans, but in restruction remix kerenel thid game work fine! What it thise??
[Xiaomi Mi 4i] haikalizz:
I'm waiting for intersectRaven to release the source of his kernel. Some had said that COC works on his kernel.

[MENTION=1498291]davtse[/MENTION] Yeah, thunderplug is nice and all. Might not need autosmp, I will just leave it unactivated in the source.
[Xiaomi Mi 4i] PavelPerm:
https://github.com/intersectRaven/msm-main/tree/ferrari ??
[Xiaomi Mi 4i] davtse:
[MENTION=6858217]haikalizz[/MENTION] I was wondering if the undervolt parameters can be tweaked by ourselves. it used to be in /sys/devices/cpu for my older devices. is it in a different folder for the mi4i?
[Xiaomi Mi 4i] haikalizz:
[MENTION=1498291]davtse[/MENTION] haven't modified the undervolt manually since it was included. I don't know much about manual undervolting...

[MENTION=4391460]PavelPerm[/MENTION] COC was caused by a display driver error. [MENTION=4832023]omerjerk[/MENTION] had asked about it on the Supercell forums. Maybe it's caused by the rom itself?
[Xiaomi Mi 4i] PavelPerm:
[/COLOR]

Do you fixed it in your kernel?
[Xiaomi Mi 4i] omerjerk:
I don't know what causes that error. It's really tough to find out which commit in the kernel actually created the bug and which one in mi4i-dev fixed it.

That's why I started again from the stock kernel and started to cherry-pick commits very cautiously.

With my kernel source, Clash of Clans is working and there are no random shutdowns/reboots either.

I'll be releasing a new build in 3-4 days after some more important cherry-picks on the kernel tree.
[General Questions and Answers] gekkehenkie11:
Since I'm getting a bit tired of IDA pro crashing on me, I thought ,let's try some native API hooking. I found this interesting page on the subject:

http://www.evilsocket.net/2015/05/04/android-native-api-hooking-with-library-injecto/

However I couldnt get it going. I was wondering if anyone here has done something similar ? Probably the wrong forum (there dont seem to be a lot of reverse engineers here), but I didnt know which other forum to use. So probably 0 replies but who knows :)
[One (M9) Q&A, Help & Troubleshooting] BriniaSona:
So right now my phone says it's getting the 5.1 update OTA. I am using TWRP. When I try to install the update it goes to the TWRP everytime. I dont use custom roms, just what came with the phone. How do I update the phone?
[One (M9) Q&A, Help & Troubleshooting] BriniaSona:
Found out I need to return it to stock recovery before I can install an OTA update. So I tried using instructions found on the web made for the noob I am. But when I use the CDM console it tells me that it can't open the recovery file.

\

What do?

Edit: I just need step by step help on what to do. I just rooted it so I could have BB10-like gestures and stock android navigation buttons. I didnt know it would screw me over for OTA updates

Edit 2: I got it work, now the update fails and goes to bootloader and tell me this, i am using the carrier supplied OTA update.

"this package of fir"htc_himaulatt" devices; this is a "htc_himauhl""
[One (M9) Q&A, Help & Troubleshooting] Ramsey:
This phone is a real hassle to update.

You won't be able to do OTAs until you return it to stock, and to do that, you'll have to run an RUU so that it removes TWRP and root. Make sure to re-lock the bootloader. So run the RUU of the latest version if it exists if you can then you won't have to OTA, or run the RUU that matches your phone's OS version and then take the OTA.
[One (M9) Q&A, Help & Troubleshooting] BriniaSona:
TWRP is removed using a stuck recovery image

the bootloader is relocked using commands from a video I watched on how to do it, it displays relocked when open.

however, now instead of getting the yellow error from before, I now get sent to the bootloader screen and nothing happens.

Edit: when I try to boot into recovery through the boatloads it gives me an error message saying it can't and takes me back to the white screen.
[One (M9) Q&A, Help & Troubleshooting] clsA:
I guess you missed the whole part about restoring your system partition to stock

From the backup you made after installing TWRP .

You need an untouched system partition and Stock recovery.

At this point you should look for the RUU for your phone
[One (M9) Q&A, Help & Troubleshooting] BriniaSona:
GG didnt make a backup.

Can you link me to one at all, and all the instructions needed to make things work. Sorry for the hassle, I really don't want to do this without help now, incase I mess things up more than they already are.

EDIT: this it it right? http://xdaforums.com/one-m9/general/htc-one-m9-dump-t3060545

Except there's now Canada option.

EDIT 2: I wish it was as easy as BlackBerry which everyone seems to think it out of date, http://crackberry.com/install-leaked-os-autoloader
[One (M9) Q&A, Help & Troubleshooting] clsA:
Theirs a thread in the general forums for Canadian files
[One (M9) Q&A, Help & Troubleshooting] BriniaSona:
So I'm downloading the bell one and using download mode and adb to input the show commands?

''Fastboot output

(bootloader) product: htc_himaulatt

(bootloader) version: 1.0

(bootloader) version-main: 1.32.666.30

(bootloader) boot-mode: download

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA11000

(bootloader) cid: BM___001''

Edit: Didnt work, so I am using these commands, but now I need to s-off, so I'm going to do that now. http://xdaforums.com/showthread.php?t=1907796

if you read this and I havent added and Edit: 2, then answer this.

what command erases everything and put it back to default, like how it was when i bought the phone.

Edit 2: re-unlocked the bootloader.

Device is giving me the same error as when I started. "this package of fir"htc_himaulatt" devices; this is a "htc_himauhl"
[One (M9) Q&A, Help & Troubleshooting] BriniaSona:
I downloaded a stock bell RUU. Went into adb and used

"fastboot update "filename""

I got an error saying there wasnt enough space.

EDIT: failed to load '0PJAIMG.zip': Not enough space

and when i try to sideload it it says the file can not be read.

Can someone just tell me what to do from the beginning, instead of telling me to look myself. Looking myself has only gotten me more lost and confused.

I need step by step instructions with links and files.

Please.

I just want my phone to be the way i bought it, No root, no bootloader changes, no twrp, just stuck everything.
[One (M9) Q&A, Help & Troubleshooting] BriniaSona:
MY phones current status.

Rooted, Bootloader Unlocked, Stock Recovery installed.

What do I do from there, where do I find the correct Bell RUU, how do I flash it, where does it go so it can be flashed.
[One (M9) Q&A, Help & Troubleshooting] Flippy498:
I think I found the correct RUU for your firmware version. The problem is you will have to pay if you want it since the website isn't for free. Sorry that I wasn't able to find a cheaper source. (Link)

Edit: Forget what I said. I just saw that there is a TWRP backup in this thread. Using it should be much cheaper than the RUU.
[Nexus 7 (2013) Q&A] MimKoRn:
My Nexus 7 is permanently awake. It is not rooted, so I could not easily check for wakelocks. I did try the method to run wakelock detector on a non-rooted device, however, and it started working for a moment, until I restarted Nexus. While it was working, it showed a 97% Awake state for a day or two of running.

However, the wakelocks were minimalistic. At first, there was Any.do showing some good amount of holding awake state, but it was far from permanent wakelock. In a moment however the top 3 wakelock holders disappeared and only minimalistic wakelocks stayed. The minutes of awake state of the wakelocks shown would not add up nearly up to an hour of awake state, whereas the device was awake for more then 24 hours already.

Android system processes were shown too.

Do you know what could be causing a permanent awake state of the device? Can I do anything about it other than rooting the device? Towelroot is not working and I know of no other rooting method that would not leave my device flashed to the factory state (do not wanna lose state of the device).

(I have a duplicate question like this on the stack exchange community, however I presume I might get more case-specific attention here at xda http://android.stackexchange.com/questions/119829/nexus-7-2013-is-permanently-awake )
[Xperia Z2 Q&A, Help & Troubleshooting] bmot:
rooting guide

CAn anyone explain how to root this searched and searched but not sure what is right as comments say out of date etc.

Am wanting to sort the sound issue only got it yesterday its on 5.1.1 d6503

already downloaded flashtool and installed drivers.

Never rooted before as i had a iphone i used to jail break the bootloader is unlockable which i will do when i get home but not sure what exactley i need and steps to follow
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] crazymook:
So I dont think I started seeing this issue until 5.1 and I know what the service actually IS (its for Sprint billing, prepaid I believe to be more specific). But it is starting to become a battery drain, a minimum one for now thankfully. I cant figure out what triggers it to come on and I dont see any way to turn it off. Doing a general search on the internets show its a rampant problem on a lot of Sprint phones and there doesn't seem to be any solution other than Sprint saying to reset your phone, which is ridiculous.

Anyone else experiencing issues with this?

Shows up in GSAM as "System (id.itsonservice)".
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] tx_dbs_tx:
Sprint itson is imbedded into the system and runs continuously. You will have to root your phone and manually remove all of it's components or flash a custom/stock OG5 rom that already has Itson removed. And Itson does more than just billing, pre-paid and what not.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] crazymook:
I'm more curious why it never showed up as a battery drain until now.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
It's only recently been turned on. Before it was there but dormant in kernel, root directory and system directory. If you read its history in XDA, once on, it's a drain. A regular hemorrhoid; if untreated, it bleeds your battery.

Developers have been removing it both externally and with custom kernels. Freeza took the stock source and removed that as well as some other things that make it compatible for root. It's treated at both kernel and ROM updater-script.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] xxSTARBUCKSxx:
Have mercy.. that was a painfully correct visual and comparison of the itson parasite and its side-effect. *still cringing*

So true, nevertheless.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
I would like to add that I'm not likening developers to proctologists. It's a simple procedure but only intended for your phone (maybe your sanity will improve for the better). So you can thank your developers in open fashion rather than a private session that you wouldn't want to have discussed in public.

Although the doctors do a great service to those that really need relief and should be appreciated as well.
[Galaxy S6 General] shanes17:
Hi everyone, I dont post often (if ever) but wanted to share my experiences with my Samsung Galaxy S6. I previously owned a Moto X (1st gen), which for those who do not know had strictly on screen back/home/toggle buttons. That said, the S6 has a physical home button with capacitive buttons on each side for back/toggle. You are probably thinking, 'yeah so?', well hear me out.

This is a big change for someone who is used to simply 'tapping' (or barely touching) a button to get to home screen versus having to physically push down a button. I often use one hand navigating my phone, so trying to click the home button down on the S6 with one hand without the force of this nearly pushing it out of my hand is somewhat frustrating. I find myself often having to use two hands just to get back to the home screen, just typing this out makes me frustrated. GREAT phone though, I just do not understand why Android doesnt make it an option across the board for all phones to have virtual home task bar at the bottom of every screen. Yes, it may take away some screen space, but with the way it worked on most phones the buttons go away when watching video in full screen mode and only reappear when your finger taps the area.

I realize some prefer the physical home button, but let me tell you the way Moto designed their phones made a physical home button completely unnecessary. They use a technology that 'wakes' up the phone as soon as it senses your presence near the phone (like your hand reaching for it), then tap the screen and viola! Phone can be unlocked without pressing down firmly on some 'physical' button.

Now, I dont know if its possible, but if anyone could manage to do this I would be the first one in line to buy the app. If there was a way to make the S6 home button more like a capacitive button so that when placing your finger on it to 'unlock' using fingerprint scan it 'awakes', that would be amazing. Adding to that, when unlocked if you simply put your finger on the button and it went to home (versus physically pushing the button down with force, causing me to use another HAND!), well I would probably send you a personalized thank you vid with a check.

Anyone else feeling the same on physical buttons vs virtual?
[Galaxy S6 General] ere1nion:
https://play.google.com/store/apps/details?id=ca.yesoft.handysoftkeys

Might help you!