yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] n3ocort3x:
that is unbelivable, the second kernel is a exact copy of an existing working kernel.. :confused: so i must be repacking

do the following please:

- extract zImage out of boot.img

-flash the modules in recovery

-boot back in bootloader

- fastboot boot zImage

and tell me if it boots after that
[One (M7) Original Android Development] jlevy73:
Both test kernels get stuck on splashscreen.

This must be frustrating without having the phone. If you ever want to teamview you can pry through my device and pull the relevant logs to help you get things resolved.
[One (M7) Original Android Development] biohaufen:
Ohhhh sorry :D I saw that the img was only 1.8MB big, so I thought that couldn´t be normal --> File is corrupt ^^ I will download and try the kernels again...
[One (M7) Original Android Development] n3ocort3x:
frustrating ?? it drives me nuts tbh :D :D

thanks to both i uplad pure zImage now and tell ya how to flash... gimme 2 minutes

zImage v1: http://d-h.st/GRr

modules v1: http://d-h.st/xXB

zImage v2: http://d-h.st/wUQ

modulesv2: http://d-h.st/NNB

- flash modules in recovery

- boot back into bootloader

- fastboot boot zImage

- reboot
[One (M7) Original Android Development] biohaufen:
n3oOne_v2_kitchen does work if you type in "fastboot boot n3oOne_v2_kitchen.img"

It also works with "fastboot flash boot n3oOne_v2_kitchen.img" ;)

I will also try n3oOne_vt_kitchen_sense.img

BOTH BOOT ! :) Sorry only my img´s were corrupted ...
[One (M7) Original Android Development] n3ocort3x:
nono dont boot the entire boot image, only the zImage posted above :)

- flash modules in recovery (for v1 modules v1, for v2 modules v2)

- boot back into bootloader

- fastboot boot zImage

- reboot

and tell me if it boots :D
[One (M7) Original Android Development] jlevy73:
Yeah, fastboot boot works, it's the fastboot flash that's causing it not work.
[One (M7) Original Android Development] biohaufen:
But also the imgs do boot :) (also when I flash them) It does really works with n3oOne_vt_kitchen_sense and n3oOne_v2_kitchen. Under Settings stands 3.4.10root@n3ocort3x-tuxbook #1

I flashed them with "fastboot

flash

boot n3oOne_xx_kitchen " But if you want I can try to only flash zImage, should I ?
[One (M7) Original Android Development] n3ocort3x:
ok thats awesome news... no dont try zimage... it will boot also. how do u guys flash boot. img normally? fastboot flasb boot boot. img is the only way i know for s on...?

fine then i can finally start working. but why it wont boot for jlevy73? other method of flasing? @ jlevy73 can u try to flash the same way biohaufen does?

[sent from an icecold mako...ncxe'ed....soon...]
[One (M7) Original Android Development] biohaufen:
I flashed them so:

fastboot flash boot xx.img (xx for the name)

fastboot erase cache

fastboot reboot

Works perfectly...
[One (M7) Original Android Development] n3ocort3x:
thats how it should be.. now waiting at jlevy if he can do the same

[MENTION=2138528]jlevy73[/MENTION] -> flash it like that and report please :)

EDIT:

two guys reported sucessfully booted... now waiting for jlevy73

EDIT2:

[MENTION=3442291]biohaufen[/MENTION] sent u pm
[One (M7) Original Android Development] LiquidSolstice:
I wonder if this is why I've been getting complaints that people can't hear me all that well.
[One (M7) Original Android Development] n3ocort3x:
I'm aware of that yeah but it seems there is still a problem with mic routing :)

VOIP?

noNeedForAsig
[One (M7) Original Android Development] mynameisjon:
I'm using Lords build with v42, but whatsapp voice still doesn't work. :s
[One (M7) Original Android Development] n3ocort3x:
Wrong thread. Go to Lords thread. It's not kernel related

noNeedForAsig
[One (M7) Original Android Development] mynameisjon:
if a change happens upstream on the main CM kernel branch, does your repository automatically update?
[One (M7) Original Android Development] Secret Chimp:
Finally a kernel that works with CM that fixes the awful lag from deep sleep on the stock kernel! I actually flashed back to a Google Edition RUU because I was so frustrated with how laggy my phone felt. This lets me run CM and snaps the phone awake just as quickly as the GE and Sense kernels.
[One (M7) Original Android Development] mynameisjon:
That lag was fixed on stock. That's the reason why it's fixed. The nature of deep sleep itself is the reason why there will always be a slight lag when waking from deep sleep.
[One (M7) Original Android Development] Secret Chimp:
My mistake - I meant to say the stock Cyanogenmod kernel, not the stock GE/HTC kernels.
[One (M7) Original Android Development] LiquidSolstice:
No actually. In-call. I had to switch out to a Sense ROM.
[One (M7) Original Android Development] SecUpwN:
which kernel tuner do you recommend going along with this kernel for AOKP 4.3?
[One (M7) Original Android Development] ess.boyer:
Hey [MENTION=4635674]n3ocort3x[/MENTION], could you share your local manifest for your PAC build? I'm ready to get cookin' :) Thanks mate!

For my first trick, I'm going to add some functionality to the gallery. For starters, the ability to show/hide albums, create new albums, and copy/move to albums. It seems absolutely ridiculous to me that they aren't standard features.
[One (M7) Original Android Development] SecUpwN:
What's the flashable ZIP to download?
[One (M7) Original Android Development] eyosen:
Trickstermod.

---------- Post added at 08:04 AM ---------- Previous post was at 08:03 AM ----------

What???
[One (M7) Original Android Development] SecUpwN:
I am on HTC ONE with AOKP 4.3 and would like to know which file from this thread to use. I'm confused as the OP says "Installer" with "Back button". Which file to download?
[One (M7) Original Android Development] n3ocort3x:
on a day trip atm but will upload when back home, no problem :) But i track some other stuff from other repos so u have to modify it to ur likings.. just to let ya know
[One (M7) Original Android Development] semdoc:
If you want all buttons like stock configuration (back =back, logo=menu, home=home): You should flash THİS.

and;

If you want home key which opens menu (back=back, logo=home, home=menu): you should flash THIS.

After then... You can adjust all values using Trickstermod from Playstore :)

Cheerz ... I'm pretty happy with first one :)
[One (M7) Original Android Development] qkall:
Just as a FYI - latest pac man nightly now works perfectly with v42. :)
[One (M7) Original Android Development] ess.boyer:
Yeah, exactly. That's why I was hoping for your manifest ;)
[One (M7) Original Android Development] n3ocort3x:
http://d-h.st/qNE

I edited some comments so u dont get confused :) have fun and i wish a succesful build :) [MENTION=4685302]ess.boyer[/MENTION]
[One (M7) Original Android Development] Bliszcur:
performance option

sorry for noob question . why i didnt see any performance option on setting?
[One (M7) Original Android Development] eyosen:
Didn't mean to hit thanks. I hate tapatalk sometimes.

You can adjust kernel parameters with trickstermod. Certain roms also have adjustments available under device option in settings.
[One (M7) Original Android Development] Mucky2:
Work this for ParanoidAndroid 3.99´?
[One (M7) Original Android Development] jaygajay:
I'm on PAC-Man Rom Sept nightlies and I've tried to flash the v42 kernel but after my phone boots it will run fine until my screen goes to sleep then I'll get a soft reboot which will keep happening Everytime it boots back up and go back to sleep then it soft reboots again. Is anybody else experiencing such issues or know of any suggestions I could try?
[One (M7) Original Android Development] ess.boyer:
Try changing your governer to smartmax. I was getting RR's with smartmax_eps and others have had issues with on demand.
[One (M7) Original Android Development] ryancnap:
does this work on att m7 or do I need to convert to ge?
[One (M7) Original Android Development] ess.boyer:
This is not a GE build. It's AOSP. Check the OP for the link to the ATT thread for this ROM.
[One (M7) Original Android Development] jaygajay:
The default is smartmax. I changed it to interactive but no luck and back to smartmax with no luck still . I even changed the minimum frequency to see if that was a problem. I'll probably have to log cat later on todsy
[One (M7) Original Android Development] ess.boyer:
You'll also want to post the last kmesg. Look at the 2nd OP for how to do that, if you're not sure how.
[One (M7) Original Android Development] ryancnap:
so after reading through the OP and changelog..ie, "removed useless governors"..no chance for wheatley huh? ;) still, gonna try your recommended tuneables for smartmax.
[One (M7) Original Android Development] bjc112:
I like Wheatley too but smartmax gets it done big time! Zero complaints with strong battery life and great performance.
[One (M7) Original Android Development] LiquidSolstice:
Just want to chime in; I'm getting consistent reboots every time I turn the screen off or back on again when I'm on a phone call. Using this kernel on the official PAC builds.

Some people suggest I try Neo's build, so I'm doing that now. I hope there's just something wonky with PAC, because I love that ROM and I love this kernel. :(
[One (M7) Original Android Development] jaygajay:
PAC-Man Rom Sept 8 Nightly flashed with HTC_IR_Module.zip and v42 Kernel.

I hope this helps. I started logcat just before I press the power button for the screen to go to sleep.

last_kmsg:

https://www.dropbox.com/s/w61sfopm1lfqvzl/last_kmsg

logcat:

https://www.dropbox.com/s/61erg1i29f2rq8p/logcatALLwarnings.txt
[One (M7) Original Android Development] jaygajay:
Did you flash anything else other than PAC and the kernel?
[One (M7) Original Android Development] ess.boyer:
Looks to me like supersu is crashing and borking the android ServerThread. Bad news. Can you try removing SuperSu and rebooting?

If you're still getting crashes, please produce new log/kmsg.
[One (M7) Original Android Development] abhisheak.bansal:
Hi,

AFAIK the default max gpu frequency in 400mhz

but i can't find it in trickster mod, only 487 ;320 ;200 ; 128 are listed

so is there some workaround to set max frequency to 400mhz

I don't prefer to overclock.

Any help is much appreciated
[One (M7) Original Android Development] ess.boyer:
I'm pretty sure that n3o is planning on adding the 400mhz step back into the kernel, as it was removed.
[One (M7) Original Android Development] ryancnap:
anyone know in a very general way how this device handles UV? I'm coming from the lgog where we had four differently binned CPUs and -75 was a pretty high UV.
[One (M7) Original Android Development] LiquidSolstice:
Just SuperSU. I messed with a custom hosts file but ended up restoring it.

So I have no idea...
[One (M7) Original Android Development] dc4:
Every device will be different, I'm currently using -100 UV across the board with smartmax_eps @ 81-1998.
[One (M7) Original Android Development] LiquidSolstice:
Neo, is it possible that there are certain commits in the current CM codebase that your kernel isn't quite up to date with yet? I don't mean to knock your kernel whatsoever, I would rather not use any AOSP at all rather than use AOSP without your kernel. But some moderate research is showing that people on the most bleeding edge of their ROM-of-choice's nightly builds are experiencing these reboots during calls.
[One (M7) Original Android Development] n3ocort3x:
Will check back home.. Busy with rom and tablet stuff last days :) report back to u or if u don't want to wait compare cm with my github

noNeedForAsig
[One (M7) Original Android Development] LiquidSolstice:
I appreciate that. I really need to sit down and learn how to properly use git and even self-compile. Is there any sort of tutorial you'd recommend? I pick up on things fairly quickly...
[One (M7) Original Android Development] ryancnap:
81 is your min freq..?
[One (M7) Original Android Development] mj084:
[MENTION=4775233]ryancnap[/MENTION]

here is a table of voltage specs for all kind of cpu's:

CLK.......ACPU 0....ACPU 1....ACPU 2....ACPU 3....ACPU 4....ACPU 5....ACPU 6

.384000... 950000... 950000... 925000... 900000... 875000... 875000... 875000

.468000... 950000... 950000... 925000... 900000... 875000... 875000... 875000

.594000... 950000... 950000... 925000... 900000... 875000... 875000... 875000

.702000... 962500... 962500... 925000... 900000... 875000... 875000... 875000

.810000...1000000... 975000... 937500... 900000... 887500... 887500... 887500

.918000...1025000...1000000... 950000... 925000... 900000... 900000... 900000

1026000...1037500...1025000... 975000... 950000... 925000... 925000... 925000

1134000...1075000...1037500...1000000... 975000... 950000... 937500... 937500

1242000...1087500...1050000...1012500... 987500... 962500... 950000... 950000

1350000...1125000...1087500...1037500...1000000... 975000... 962500... 962500

1458000...1150000...1112500...1075000...1037500...1000000 .. 987500... 975000

1566000...1175000...1150000...1100000...1062500...1037500 ..1012500...1000000

1674000...1225000...1187500...1137500...1100000...1075000 ..1050000...1025000

1728000...1250000...1200000...1162500...1125000...1100000 ..1075000...1050000

I (ACPU 3 is mine) use these voltage settings from n3ocort3x here:

http://abload.de/image.php?img=screenshot_2013-09-01nxax7.png

with smartmax governor...with ondemand (and CPU OC to 1998 MHz)I got a complete death of phone and only get powered on when charger pluged in:silly:
[One (M7) Original Android Development] n3ocort3x:
See one post below

noNeedForAsig
[One (M7) Original Android Development] n3ocort3x:
U can join our community (link in sig) I wrote a few tutorials about this stuff and share it there. Also u can discuss with me lord and the others about that stuff.. We are helpful people and try to help where we can there. So feel free to join :) there u can also see what me and the others are doing atm... :) for me it's ROM device and tablet stuff atm

noNeedForAsig
[One (M7) Original Android Development] dc4:
Yes.
[One (M7) Original Android Development] LiquidSolstice:
Gladly! I look forward to it.
[One (M7) Original Android Development] gilbus:
where can i find the IR-Module zip? googled for it but nothing :/
[One (M7) Original Android Development] n3ocort3x:
just checked back with CM Kernel Tree, and this kernel is up2date. nothing changed
[One (M7) Original Android Development] LiquidSolstice:
Here you go Neo. I posted this in the PAC thread too since almost everyone there uses this kernel.

After doing some more testing, I've found that I can consistently force the phone to reboot by using the speakerphone and either letting the screen turn off or manually turning the screen off.

Here we go. Logcat attached.

Steps to Reproduce:

Call anyone.

Place on speaker.

Manually turn off screen.

Wait about a second.

Boom. Reboot.

https://www.dropbox.com/s/x89mu08mknabwzc/reboot-crash-logcat.txt
[One (M7) Original Android Development] ess.boyer:
Take a look at this block:

[ 09-10 19:44:45.335 11293:11313 I/ActivityManager ]

Start proc com.google.android.music:main for service com.google.android.music/.playback.MusicPlaybackService: pid=18429 uid=10075 gids={50075, 3003, 1015, 1023, 1028}

[ 09-10 19:44:45.836 11293:11640 I/ActivityManager ]

No longer want com.vipercn.viper4android.xhifi (pid 18125): empty #11

[ 09-10 19:44:45.846 11293:11639 W/ActivityManager ]

[b]Scheduling restart of crashed service com.vipercn.viper4android.xhifi/.service.HeadsetService in 19456ms[/b]

[ 09-10 19:44:55.346 11293:11313 I/ActivityManager ]

Start proc playboard.android for service playboard.android/com.parse.PushService: pid=18506 uid=10121 gids={50121, 3003, 1028}

[ 09-10 19:44:55.636 11293:11346 I/PowerManagerService ]

Going to sleep by user request...

Look like the first thing to crash is Viper audio mod stuff.

I tried to reproduce using your steps and was unable to. No crash for me (I have no mods installed). I'm guessing there's no easy way to remove the Viper stuff, but I'd suggest trying without it - maybe NAND/wipe/reinstall and see if you can still reproduce it, and/or poke around the Viper thread to see if anyone has reported similar issues there, and post your log.

Perhaps others here, both with and without Viper audio would try to reproduce and submit their findings.

Hope that helps!
[One (M7) Original Android Development] LiquidSolstice:
Doh. I should have tried that first.

Are you on stock kernel? I'm going to load up a stock build and see if I can find it.

Also, what error-level do you recommend I logcat at? Fatal or Error?
[One (M7) Original Android Development] LiquidSolstice:
After trying my absolute hardest to get it to crash on a fresh full-system-wipe, it seems I spoke way too soon. It was definitely the vipermod. There was quite a lot of weirdness with this flash to be fair, everything from an overly difficult process of installing viper to SuperSu issues to TWRP telling me root needed fixing on each reboot.

I'm going to do this all over again one more time as cleanly as physically possible. My apologies for implying that your kernel could have had anything to do with it Neo, and thanks a ton for the patient help, ess.boyer.
[One (M7) Original Android Development] ess.boyer:
Hey, my pleasure man. I (and many others around here) just want to see everyone running happy and free of troubles :)

I can say, after installing every single release of PAC 4.3 released (including ALL of n3o's interim builds), dirty and fresh,I have never seen TWRP give any error, or indicate that root was borked.

From what I've seen in passing, installing SuperSu, is 1) Not recommended and 2) causes lots of problems, sometimes in unexpected ways. I don't really see why SuperSu is needed, since the AOSP roms are rooted, but I'm sure there must be some reason, since people keep doing it. (I don't mean to sound snarky here - I just honestly don't know what the reason is).

Anyway, I hope you're able to report this issue to the Viper dudes so they can hopefully find & fix.

(PS - For diagnosing app crash, I usually find the W (Warning) level to be good - keeps the debug/info stuff out, but allows you to see the error/fatals themselves, as well as potentially useful precursors given as warning level output. If you find that too verbose, simple re-run at E. If it's too terse, crank it up to D.

Cheers,

Ess
[One (M7) Original Android Development] LiquidSolstice:
So oddly enough, after a clean install, I decided to try Viper again. And lo and behold, it still works flawlessly, including audio effects.

So it seems that I just somehow monumentally screwed up my last flash of PAC.

The reason I use SuperSU is because Titanium Backup behaves with it. I remember someone saying something about legacy settings in TiBu to make it function properly with superuser, so who knows. Maybe that's what I need to do.
[One (M7) Original Android Development] willew4:
cm-10.2-20130910 and teaMsevenAOSP_v42

I have been using the various nightlies, and teaMseven kernels, since the beginning of August. Up until the nightlies from 20130902, various functions have become very unstable, including the dt2w and camera. Yesterday, I did a complete wipe and fresh installation of cm-10.2-20130910 and teaMsevenAOSP_v42. Thank goodness the camera now works, however, dt2w, s2w, and pocket detection don't work. Upon restoring a nandroid backup, everything works but the camera. :crying:
[One (M7) Original Android Development] jaygajay:
I did remove SuperSu and dirty flashed the same build again without the HTC IR Module this time and no more reboots. The only reboots I get is during a call when the screen is off and then I try to turn the screen on it reboots.

Here is a new log and kmsg.

https://www.dropbox.com/s/amy020b8x6k1b0q/last_kmsg.txt

https://www.dropbox.com/s/n4is8dyhepxvwwk/logcatWarnings.txt

I'll try to wipe and install fresh to see if that solves any problems that SuperSu may have left.

---------- Post added at 09:33 AM ---------- Previous post was at 09:08 AM ----------

Here is a fix I found so that we can restore TB backups without using SuperSu. I believe this is what you were referring to when you say using legacy settings.

http://xdaforums.com/showpost.php?p=45317574&postcount=13

After saying that you flashed the ViperMod once more without SuperSu and everything is working fine then I have to assume that SuperSu really did some damage and borked the whole PAC Man Rom. I'm going to do a fresh install and see what my results are.
[One (M7) Original Android Development] xsycox:
Two questions:

1. Is it better to wait for an update due to those lately problems with the kernel and PAC (4.3)?

2. I cannot find the difference between those two 4.3-kernels. Home menu or menu home?!
[One (M7) Original Android Development] mj084:
[MENTION=3779540]xsycox[/MENTION]

Home menu --> HTC Logo used as HomeButton

menu Home --> HTC Logo used as MenuButton

:)
[One (M7) Original Android Development] xsycox:
Great, thanks. What is the standard option?
[One (M7) Original Android Development] mj084:
the "standard" is, that HTC logo isn't used in stock ROM's or stock CM...

u can decide what u prefer;)

I use logo for menu...
[One (M7) Original Android Development] ess.boyer:
You can install Trickster Mod (from Play Store) and use that to enable s2w, l2m, pocket protection, etc. I noticed with the v41 or v42 kernel, they weren't enabled by default anymore, but Trickster Mod gets you back in the game fast.

---------- Post added at 02:20 PM ---------- Previous post was at 02:14 PM ----------

Personally, I haven't found an issue yet with the 09/10 nightly, and teaMseven v42 kernel. Running fast, smooth, great battery life, phone/camera/etc working fine. Give it a try! Just make sure you have a NANDROID backup in case you find something that you can't live with. Everyone here has a different idea of what is stable enough to be a daily driver, since we all have different needs. Personally, I could care less if bluetooth and IR are ever working, for others, that's the whole reason they bought the device in the first place. So to each his own! Just give it a try, is my advice.
[One (M7) Original Android Development] n3ocort3x:
status update:

I know things were merged for OTG, but i hadnt got time so far to work on kernel further. (Have some troubles with Gerrit atm which i want to solve first). Kernel should be updated tomorrow / or late night today... but i think tomorrow evening is the most realistic scenario :)

Just before someone asks :)
[One (M7) Original Android Development] n3ocort3x:
OP updated to V43:

teaMsevenAOSP_v43_CM 10.2

- synced with CM

- changes on 14th septemper see HERE

- fixed USB OTG / CM CRCPALMER, I take no credits for that
[One (M7) Original Android Development] popy2006:
Hey n3ocort3x.

Since in the CM10.2 thread nobody hears me ill try it here.

There are bluetooth AD2P issues (short dropouts every couple of minutes).

Could you please point me in the right direction what i and others can do to help you or the cm team to sort this issue out?

Here are the posts in CM thread:

http://xdaforums.com/showpost.php?p=45554039&postcount=2477

http://xdaforums.com/showpost.php?p=45553012&postcount=2475

thx

pOpY
[One (M7) Original Android Development] v3rtex:
What is the default gpu frequency of a htc one?
[One (M7) Original Android Development] mj084:
Max is 400 MHz...
[One (M7) Original Android Development] mattisfaction:
With your latest Pac and kernel, overclock to 1.836, under clock to 0.27, smartmax governor, only the thermal set to custom levels, and look at current stats, plus still going

Thanks mate, your a star
[One (M7) Original Android Development] Jterry31:
The governer and hotplug values are not sticking when i edit them using trickster mod. I have set to apply on boot in setting. Is there any solution?

Thanks
[One (M7) Original Android Development] mj084:
think thats normal...
[One (M7) Original Android Development] eyosen:
Check under /system/etc/init.d directory for scripts messing with trickster settings.