yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] THADDIUS25:
I wouldn't think u would have to build one from scratch since flar has a compatible kernel with Sprint.
[One (M7) Original Android Development] poondog:
As far as I can tell, he may be using the same kernel (zimnage) for both devices. Since he only has one source and defconfig. You can try if you want :D
[One (M7) Original Android Development] Ktan188:
For the Joey kernel , in Trickster mod it keeps showing the min as 1500ghz. When I go check the info page it changes back to 384ghz. Is this normal, or just something to ignore?
[One (M7) Original Android Development] Keasby:
Think this is a trickster mod bug, maybe kernel related...

Don't know exactly, but this happens with other custom kernels too.

Don't worry about that ;)

Tapatalked with ARGE and Joey Kernel from HTC One
[One (M7) Original Android Development] myrigon:
It seems I do have this bootloop issue on sinless 2.1.1. Kernel install, and first boot is fine. However, if I do a full reboot, I get bootloop. Have to dirty flash rom to fix it. Soft reboot is okay ,that's why I didn't notice until now. :p
[One (M7) Original Android Development] poondog:
It's fine, that's how the phone boosts itself don't worry
[One (M7) Original Android Development] Clark Joseph Kent:
That will be enough....and that will be the only warning. Thread Cleaned & Thank You.
[One (M7) Original Android Development] Ktan188:
Quick question, I know sweep 2 sleep is the default setting on this kernel. Does it cause any battery drain? Also is it possible to add an option to add the default HTC max frequency on to this kernel? Just want to test somethings out.

Thanks, great kernel by the way. Awesome battery life
[One (M7) Original Android Development] poondog:
Sweep to sleep doesn't drain battery, as the screen and touch is still on anyway. Only 2w options will cause draining because it will keep the screen on when it would otherwise not be

Nah screen off max is capped by a HTC binary that's closed source

Cheers
[One (M7) Original Android Development] bailie1912:
Is there any other links for the latest Joey kernel keep getting a bad download?
[One (M7) Original Android Development] Denpech:
http://cs3-1.4pda.to/4101445/JoeyKe...2541e00000000aaad7346fc3a3f35977473211fdb23cd
[One (M7) Original Android Development] frankcck:
Is the reason why here's so quietly these Australian treasures are AWESOME =b

Thanks [MENTION=4379011]poondog[/MENTION]

ViperOne @ HTC One
[One (M7) Original Android Development] poondog:
I never had a problem with devhost.. except for when their servers go down
[One (M7) Original Android Development] bailie1912:
Wasn't letting me download through the HTC browser so I installed chrome and it downloaded fine :)
[One (M7) Original Android Development] poondog:
Joey changelog is now in post #6

Thanks [MENTION=4751514]Krocko[/MENTION]
[One (M7) Original Android Development] poondog:
yeah chrome ftw
[One (M7) Original Android Development] myrigon:
A little update on the bootloop issue I was having..

Still no idea of the cause, but I flashed sneakyghost's full wipe FUU, and no longer have the issue. Heavy hammer wins again! :sly:
[One (M7) Original Android Development] poondog:
[MENTION=1102297]Sneakyghost[/MENTION]

FUU fixes everything.. Except your phone :D
[One (M7) Original Android Development] Magpir:
Can I have the link to the FUU thread
[One (M7) Original Android Development] poondog:
Its in one android development should be easy to find
[One (M7) Original Android Development] herwegan:
[MENTION=4379011]poondog[/MENTION] you're a kernel-expert ;) could you please tell me if these kernel wakelocks are normal?

Thanks in advance!
[One (M7) Original Android Development] poondog:
I'm a noob :)

Most are related to wireless networks, WiFi especially. Was WiFi on and not connected to network? I always turn WiFi off when I'm not using it
[One (M7) Original Android Development] herwegan:
:P

Thank you:) yes, wifi was on. But i was wondering more about the powermanagerservice, cause i've never seen it before with such high amount..
[One (M7) Original Android Development] poondog:
Power manager service is a combined wakelock consisted of userspace wakelocks

https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/PowerManagerService
[One (M7) Original Android Development] herwegan:
So is there a way to determine the single wakelocks that are combined in this combined wakelock?
[One (M7) Original Android Development] poondog:
Delete your apps :D
[One (M7) Original Android Development] herwegan:
:laugh: damn it..
[One (M7) Original Android Development] poondog:
Less apps and less syncing--> great battery :)
[One (M7) Original Android Development] herwegan:
Well i've never experienced this before and i don't have many apps.. i guess one app has a sync bug with 4.4.2..
[One (M7) Original Android Development] Ktan188:
Sorry for the off topic. But do anyone know how to recalibrate the battery so the phone can read the battery level correctly. My battery seems to be off. When I unplug the phone as soon as the green light pops up. The battery drops 6% right away. I have to leave it plugged in for a few more minutes after the green light to make sure it is fully charged. Also, when I'm using the phone for 10+ mins. the battery level stayed the same. But as soon as I put the phone to sleep it drops 2 or 3%. Any suggestions? Thanks
[One (M7) Original Android Development] Magpir:
This is a Rom or kernel problem.
[One (M7) Original Android Development] poondog:
Hi

You should be charging for like an hour+ after green light pops up. The way the battery is read is a rough estimate.. That's why originally phones didn't have %

With current technology the % is quite inaccurate

My old nexus 7 used to go for ages on 100% then drop heaps

The thing I'd blame is the actual battery and current technology
[One (M7) Original Android Development] gordonpn:
It's also related to the way lithium batteries work. When it reaches close to 100%, it starts to trickle charge.
[One (M7) Original Android Development] poondog:
Yes

This is what I mean :)
[One (M7) Original Android Development] adakaya1994:
I have the exact same problem with all roms or kernels.. When you fully charged your phone don't plug out charger fully power down your phone wait for green light and again do not plug out charger, power on your phone wait green led and plug out then it will act normal.. Or you need to wait longer on the green led when phone fully charged..
[One (M7) Original Android Development] tibere86:
A bit off topic, but could anyone point me to a good write up on how to set up a kernel building environment? Just Ubuntu-fied my old laptop and would love to build Joey on my own :)
[One (M7) Original Android Development] Ktan188:
I think there's an kernel development intro somewhere in the development thread
[One (M7) Original Android Development] anarchychris:
This has never actually happened to me but I've heard that the following process works

- Charge to %100

- Remove cable (% will drop)

- Reinsert cable

- Charge to %100

- Remove cable (% will drop hopefully less)

- Repeat until the % doesn't drop

Thanks

Chris
[One (M7) Original Android Development] poondog:
This is what I used to setup on my new linux install (wiped going from Ubuntu 12.04--> 13.10)

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

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

Baby you light up my world like nobody else
[One (M7) Original Android Development] anarchychris:
That's just how I roll
[One (M7) Original Android Development] poondog:
you don't know you're beautiful
[One (M7) Original Android Development] Ktan188:
Someone is secret One Direction fan... lol
[One (M7) Original Android Development] poondog:
Christopher will understand

for the record I don't have any one direction on my phone
[One (M7) Original Android Development] anarchychris:
He doesn't keep one direction on his phone. He keeps in his CD and DVD collection. He also has a One Direction Tattoo. :eek:
[One (M7) Original Android Development] poondog:
Dear Christopher

Here is my CD collection
[One (M7) Original Android Development] anarchychris:
lol, my CD collection is buried somewhere (long forgotten) . If i did have one it would definitely have One Direction.
[One (M7) Original Android Development] poondog:
apparently, m8 name has leaked

HTC One Direction
[One (M7) Original Android Development] Ktan188:
Didn't know people still use CDs now
[One (M7) Original Android Development] poondog:
I only get CDs when I really want the whole album at good quality. This is what I rip to flac

Otherwise I have them for my car :)

And to support the artists
[One (M7) Original Android Development] HolyAngel:
Vinyl is where its at :wink:
[One (M7) Original Android Development] poondog:
It'd just be a ninja disk or a frisbee to me
[One (M7) Original Android Development] herwegan:
[MENTION=4379011]poondog[/MENTION] i really like your concept in this kernel with performance/battery compromise and s2w/s2s. it's all i need out of the box. thank you :good:
[One (M7) Original Android Development] poondog:
Thanks for the kind words, hopefully we can see 4.19 base kernel soon!
[One (M7) Original Android Development] tibere86:
Thanks!

---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------

Thanks poondog, great resources.
[One (M7) Original Android Development] poondog:
No problem good luck
[One (M7) Original Android Development] Ktan188:
Which I/o scheduler do you guys recommend row or deadline for good battery life?
[One (M7) Original Android Development] poondog:
Deadline for everything imo
[One (M7) Original Android Development] herwegan:
I was able to get rid of the huge wakelocks... Nice stats now :good: :D
[One (M7) Original Android Development] poondog:
No kernel issue :D See :)
[One (M7) Original Android Development] nickabbott:
Hi,

I enjoy working things out for myself but sometimes a little helping hand is great!

I'm going to attempt to build your kernel from source and I've got a toolchain and the clone of git hub and now I'm just a bit lost with what to do now. Usually you do make clean or make bravo or some kind of code eg make kangaroo but where do I find it or what is the right command please?

I'll keep on investigating but the two guides you posted kind of do different paths to the make bit and I'm not sure which to follow.

I'm looking to keep the kangaroo alive a little longer and stick with my 4.3 android build :)

Cheers!

EDIT: Using the below seems to be doing something!

make ARCH=arm CROSS_COMPILE=/home/android/toolchains/arm-cortex_a15-linux-gnueabihf-linaro_4.8.3-2014.01/bin/arm-cortex_a15-linux-gnueabihf- > compileLog

EDIT 2:

Now it seems that I may have cloned the wrong github source?! Should it be:

kangaroo-m7-MKII

or

KANGAROO-kernel

Please!

I did the MKII one and I'm getting errors compiling the smartmax governor.

EDIT 3: I hashed out the smartmax governor from the makefile and it's built now, not sure if it's worked right or not but will try later!

#obj-$(CONFIG_CPU_FREQ_GOV_SMARTMAX) += cpufreq_smartmax.o

EDIT 4: WOOHOO it worked! :D It's loaded up and after a reboot it's still loaded up so I guess it's worked!?

I copied out the modules and the zimage into the 9th jan zip and it's worked fine, obviously without smartmax because I hashed that out of the build!

So, [MENTION=4379011]poondog[/MENTION] if you can advise what I need to fix to leave smartmax in, that would be brill please!

Now I just have to make sure the build is stable and I can look at applying a ton of changes that I can see on the linux github and the updates to joey and elemental!

EDIT 5!!!: So I'm guessing that because I didn't use the makefile within the root of the kernel folder it built without all the -marm and cstate flags? I guess I can add in all the flags to the command below?

make ARCH=arm CROSS_COMPILE=/home/android/toolchains/arm-cortex_a15-linux-gnueabihf-linaro_4.8.3-2014.01/bin/arm-cortex_a15-linux-gnueabihf- > compileLog

Or will I have used the /arch/arm/vfp/makefile one instead?!

Argh, lots of learning / researching ahead!

EDIT 6 (Hopefully this is useful to others):

To build with poondog's config you need to do make kangaroo_defconfig

them edit the makefile in the root folder and change the bit where it points to /home/poondog/toolchain to your own path.

Then make -j4 or however mamy threads you want to run.

I think this has worked, it's compiled anyway so I just need to test it!

Which way is best please poondog? And have I done something wrong / stupid?!
[One (M7) Original Android Development] poondog:
Hello nice long post :D I will do my best to answer

You are fine to post your things here I can help

This is how I build:

in Makefile (the one in root of source) change my path to toolchain to yours

1. make clean

2. make kangaroo_defconfig (pulls this from arch/arm/configs and writes to .config in root)

3. make -j3 (my computer overheats with anything higher :D)

You have the correct source for 3.62 base android 4.3

What errors are you getting when compiling cpufreq_smartmax.o? I don't remember, its been a while since I have compiled kangaroo kernel since I switched to kk sense ages ago

I do already plan on upstreaming the next kernel (4.4.2 sense whenever source is out) to 3.4.y latest (atm its 3.4.79, kangaroo is 3.4.75)

If you are planning on this you will see many errors in the diffing because HTC have decided to remove the comments present in the main linux kernel, so when the patch -p1 command looks for comments to make its changes it won't find them so you will be left with rejects. Just a heads up :D

Every makefile is used, when that directory is flagged by the compiler and previous makefiles. The main makefile is the one in root, the other ones are only for their specific folder (only the arch/arm/vfp folder for example)

Thanks :)
[One (M7) Original Android Development] nickabbott:
Many thanks for your help and advice! I will use the makefile method of building as I can be sure it's using the correct build flags. I tried with -letsseeifthisworks and it failed so I know it's using the correct build makefile! And the changes do make a difference!

I'll update when I re-run the build and will post the error that comes up in here about smartmax, it might not happen now I use your build makefile, it definitely did when I ran the command with the toolchain link in.

I've not seen any guides on how to upstream but that looks like something I think would be good, but will be a pain if like you say it will throw a bunch of errors! How is that done please? I guess you would just run something like:

git merge https://github.linux.????? -ver3.4.79

From the root of the kangaroo folder? Or something like that! I'm missing the correct paths and branches though!

I've seen many patches applied by flar and yourself that are taken from the main linux github and others that aren't, so I'm at a loss as to what to apply and what not to so I guess all the patches that are confirmed GOOD will be in the latest upstream versions in which case I wouldn't need to apply patches individually I can just upstream to the latest version.

There's probably not much I want to change really, your jan 9th build is working perfectly fine but I've seen a lot of people say building without -marm works well and your latest build used it so wanted to try myself to see if it does indeed make a difference or not!

Then I can alter a few defaults to my own liking, originally I would have put the max freq back to 1728 or whatever it is but to be honest, I don't even notice a difference with it running 200mhz slower, and it will run cooler as well. I don't game and to be honest don't really call people, just text and browse the internet!

I might play with the thermal run cool bits to match flar's run extra cool as I prefer my phone to be cooler / not running as hot and that's probably it!

Then start all over again with Viper updates to 4.4.2! Lol. I've just got a perfect build running on 3.1.0 RC2 I think and don't want to update until I really have to!
[One (M7) Original Android Development] poondog:
of course the Makefile changes make a difference :) Thats what they're there for :D

The way I merge patches is by downloading them manually from kernel.org or lkml, and patch them (the diffs) in with the command

patch -p1 < (nameofpatch).diff

I will update the 3.4.10 base to the latest if you're keen on waiting :D

Also with thermal.. in my latest Joey kernel its running on like a xxxxxxxxxxxxtra cool setting, it throttles at about 60C so basically any time you feel the phone heat up it will cool back down.. or attempt to anyway. Its a 3 stage throttling algo from CAF/tripnraver

And with ViperOne 5.0.0.. you won't have to start a kernel again, because I will :)

Sorry about the late reply. I have a plan of attack for 4.4.2 kernel source though :P
[One (M7) Original Android Development] nickabbott:
Thanks for the heads-up on how you do the patching, I'll have to give it all a play and see how I get on!

My previous coding attempts on the HTC Desire was all done manually, line by line copy and paste style or I just printed it and re-typed the code in!

I'll have to go through your Joey kernel changes and see what can be picked out to update the Kangaroo kernel :D

Looking forward to Viper 5.0.0 though and your new kernel! I'm not one for continuosly updating for updates sake but they have added quite a few new features I'd like to the newer releases and I'm feeling a little left out!

So far the issues I've had / errors with compiling are:

HOSTLD scripts/kconfig/conf
fs/Kconfig:299:warning: type of 'ASYNC_FSYNC' redefined from 'boolean' to 'string'
warning: (ARCH_MSM_KRAITMP && ARCH_MSM_CORTEX_A5) selects HAVE_HW_BRKPT_RESERVED_RW_ACCESS which has unmet direct dependencies (HAVE_HW_BREAKPOINT)
warning: (ARCH_MSM_KRAITMP && ARCH_MSM_CORTEX_A5) selects HAVE_HW_BRKPT_RESERVED_RW_ACCESS which has unmet direct dependencies (HAVE_HW_BREAKPOINT)
#
# configuration written to .config
#

The above happens when doing the make kangaroo_defconfig bit

I imagine it's not game changing as it still builds alright? And we're running A15 cortex not A5 so the other errors can be ignored?

I've just built your kernel again using the make -j4 process and not the one with the crosscompile code make ARCH=arm and the toolchain path and there's no error with smartmax now?! Strange!

If I do this:

make ARCH=arm CROSS_COMPILE=/home/android/toolchains/arm-cortex_a15-linux-gnueabihf-linaro_4.8.3-2014.01/bin/arm-cortex_a15-linux-gnueabihf- > compileLog

It also doesn't do the error any more?! Strange! maybe i didnt get a good git clone or something?!

I didn't think your response was late so no need to apologise, I just appreciate the help you can give :) And good luck with the 4.2.2 changes, I'm sure I'll give up on my current mission and just use your latest kernels soon! :highfive: lol
[One (M7) Original Android Development] poondog:
You might have to patch it manually in some parts of the linux update patches because they don't apply automatically

afaik the errors/warnings when you make defconfig don't matter.. they don't upset the compiler or anything. The async one is fixed in joey kernel

And, maybe you had something changed for smartmax to work. I don't remember it not compiling though

No problem good luck
[One (M7) Original Android Development] ghostENVY:
Hi , Poondog I've been stuck with a bootloop with your newest Kernel on all the roms I've tried. I just updated to 5.0 Viper (clean install) , downloaded your kernel (wipe dalvik) and still no dice. I have tried several kernels with no issue (ElementalX and Tbaldwin's Kernel). I have the newest 4.19 base installed , Newest TWRP. I have gone back to your Jan 24 update and this one boots without an issue. I should note that I once accidentally flash your kernel when there was no OS installed would that cause an issue ? Any help would be appreciated Thx. :highfive:

Just so you know I have an AT&T Model M7_UL CID: 11111111 S-OFF Radio 4A.23.3263.28
[One (M7) Original Android Development] myrigon:
I had this issue a little while ago, no idea why. The full-wipe FUU from sneakyghost's thread fixed it. Might sound a little extreme, but I was worried that the bootloop issue may have been the run up to a more serious issue, so I nipped it on the bud. The issue has never resurfaced.
[One (M7) Original Android Development] poondog:
I actually tested the 30 Jan joey kernel on insertcoin 7.x which is 4.19 base, then checked it was working with an early viper 5.0.0

I can't see what the problem is, I doubt being att is the problem. Obviously you need an os for the phone to boot

After sneaky fullwipe, after panicking I did recovery flash, then reflash rom and kernel no issues
[One (M7) Original Android Development] myrigon:
I don't think it was the kernel, but some particular interaction with another problem which was causing the bootloop. I got the bootloop on two different ROMs with Joey, kernel, even after wipe from recovery, so I think it was something deeper.
[One (M7) Original Android Development] poondog:
I was just informed in my vivo thread that an un-insecure (secure?) boot.img creates problems with the anykernel format I use. This is the case on stock roms, most custom roms have insecure boot.img. Buit viperone idk, remember its still a GPE 4.4.2 kernel (as all are) so hopefully no issues when proper source is used :)
[One (M7) Original Android Development] myrigon:
Need saaauuuuce! :sly:
[One (M7) Original Android Development] poondog:
sauce plz nao

y dey do dis 2 me,,,,,
[One (M7) Original Android Development] Jbb3393:
Enjoying Joey on viper 5! Just got a random reboot though and figured I'd have you take a look and see what caused it. Thanks https://www.dropbox.com/s/i6j7obklttt6dfi/last_kmsg
[One (M7) Original Android Development] poondog:
Seems to me like something triggered a reboot, userspace. Nothing unusual as far as I see skimming through it..

Maybe incompatibility, maybe rom side problem. You clean flashed viper? I had issues dirty flashing from insertcoin
[One (M7) Original Android Development] ghostENVY:
Hey brother I did just that and It worked !

Thx Poondog for the awesome kernel!:highfive:
[One (M7) Original Android Development] poondog:
[YOUTUBE]6Cp6mKbRTQY[/YOUTUBE]

:D
[One (M7) Original Android Development] Jbb3393:
Hhmm... Yep I actually updated with a wipe all firmware then sideloaded the Rom and kernel.
[One (M7) Original Android Development] poondog:
Perhaps this will fix itself in new source. Or maybe it's the voltage
[One (M7) Original Android Development] Ktan188:
Is there a set screen off max frequency on this kernel? It says it is 384 while stock is suppose to be 1134
[One (M7) Original Android Development] poondog:
Hi

Screen off max should be limited to 1026MHz by mpdecision. I have not touched it. By default, the stock kernel has this too. 384 should be the screen on/off min

Where does it say 384 max screen off?
[One (M7) Original Android Development] Ktan188:
It's on the viperone 5.0 cpu tab.
[One (M7) Original Android Development] poondog:
ah that will not be correct. Since there is no screen off interface (its inbuilt not userspace visible) then viperone does not see it. It just has the option there for kernels with the interface.

That tweak will not work, so whatever you do the screen off max will always be 1026
[One (M7) Original Android Development] ghostENVY:
Hey Poondog is your dual core test kernel worth a try over your newest 4.4.2 GPE kernel?

Thx

:o
[One (M7) Original Android Development] poondog:
The new kernel though is more advanced.. You could try it, if you want

Quad core though is fine most of the time. If you want to save more battery change the thermal settings and governor to be more aggressive
[One (M7) Original Android Development] Hopie:
works joey from 30.1 on viper 5.0?

or is it a base problem?
[One (M7) Original Android Development] Ktan188:
Works just fine
[One (M7) Original Android Development] poondog:
Compass and something doesn't work like every kernel based on gpe 4.4.2
[One (M7) Original Android Development] tbalden:
Check the gyro driver. On TeamSeven and ElementalX it works fine (with some modification).