yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] rhong:
Hi sir,

The reason why im saying v004 is much better is because it boots in my phone with no problems at all aside from the fact that the battery life is very noticeable in comparison to elemental & tbalden. I have tested personally all of the 009( not just once but 3 times i think), but i guess i have no luck. it keeps on restarting on the htc logo. That is why i'm reporting based on my tests. I think there is no additional flashing to made on v009 coz im wondering why v004 is booting and v009 is not.

Thanks and kind regards,

Rhong
[One (M7) Original Android Development] poondog:
yeah makes sense in this respect.. just not for performance. Just don;t know why it doesn't boot.. you flashed 004 then 009?

strange issue. You got an adb connection?
[One (M7) Original Android Development] superleeds27:
Seems to be working fine. M7 seems like a massive ballache at the moment, on the AOSP front. Problems with sound not working in calls when mixing certain kernels and ROM's.

Roll on Official Sense 6!
[One (M7) Original Android Development] poondog:
yeah haha

You have in call sound etc working?

edit: uploading last kernel for today.. total of 8 now
[One (M7) Original Android Development] rhong:
Yes i flashed them one after the other. that means v004 then v009. then v004 again. I do have the adb connection. whta do you want me to do about it? Im so eager to try this v009 as im sure it is much better than v004.
[One (M7) Original Android Development] poondog:
are you able to get a logcat and extract from the log what the issue is? :)

ok, because sometimes when I test kernels.. if one doesn't boot, nothing will boot until I reflash the rom lol
[One (M7) Original Android Development] RUUMan:
My reply will be same. Peace
[One (M7) Original Android Development] drsamratroy:
hey m8 just a piece of advice here... that is if u haven't done it yet.... download the kangaroo files zip thru a lappie using a download manager like idm... sometimes Dropbox downloads turn out to be corrupt... I hav myself downloaded it in the same manner & flashed a version thereafter without a hiccup & m writing this from my phone only... & as no one else has reported this bootloop, it has to be a error on ur part...

Cheers...

---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------

hey what exactly do want me to upload in the results of the flashed kernels? I mean any specifics like antutu etc...
[One (M7) Original Android Development] superleeds27:
Havent tried yet, Im guessing it will be fine! Slim tends to be spot on!
[One (M7) Original Android Development] poondog:
please :)

And specify which kernel version :)
[One (M7) Original Android Development] poondog:
I use slim on my flo, its great
[One (M7) Original Android Development] drsamratroy:
well that means u want just the antutu benchmarks & overall smoothness i suppose... because battery life cant be tested as u have 8 kernels for testing & the deadline is Sunday... so each kernel for 12 hours i suppose ;)
[One (M7) Original Android Development] rhong:
Isnt it when a download is corrupted, flashing will not continue? It seems it was flashed successfully and restarted after each flash. I tried to download 1 file in my pc and flashed it in my phone but got same bootloop. Downloading the whole kernel test zip now to try as instructed by you.
[One (M7) Original Android Development] Asselalf:
Benchmark test kangaroo009_jo

Ca. 24600 points

Previous Kernel was Ahlan 6.0.0 with 26400 points (maybe its interesting for you)

Now testing batterylife

Gesendet von meinem HTC One
[One (M7) Original Android Development] RUUMan:
What do u mean by slim
[One (M7) Original Android Development] poondog:
I'll give however long it takes to get some solid results :)

Then can come the next stage of the kernel

Antutu? I got 26k on JO lolol

Slimkat is an AOSP rom
[One (M7) Original Android Development] RUUMan:
If booting problem try to go advanced wipe , wipe cache and dalvik only flash the kernel and see if the problem still persists

---------- Post added at 10:19 PM ---------- Previous post was at 10:17 PM ----------

Another thing that could cause problems is the boot loader version. I am using the 1.43 hboot. According to some posts here that I read before this hboot is better than 1.44 and above
[One (M7) Original Android Development] miten_sheth:
I dont know what happened to my phone suddenly.. But the new update gave me this.. Sticking to this kernel for now.. Lets see what the further versions have got for me! :D
[One (M7) Original Android Development] Asselalf:
Antutu X...

maybe there is a difference between Antutu & Antutu X
[One (M7) Original Android Development] Large Hadron:
Ok, downloaded them all. Now to pick one at random and flash :)
[One (M7) Original Android Development] dictionary:
Yup, no matter what I do, 009 kernels all cause me to bootloop. Won't have my PC for next couple of days to get a log, but something changed since the 004 kernels that doesn't play well with my apps. I flashed svn55 and then flashed 009. It booted up and worked. I then started to restore apps. In the middle of this I got a hard reboot, and then bootloop. Had to reflash 004 to get it to boot. Only kernel modifying app I use is Trickster, but as far as I know, it doesn't do anything after I restore it until I actually open it, and give it root permissions. I didn't this time around. I'm totally stumped on this. Have done the clean flash, Dalvik and regular cache wipes. No change. I also install xposed, but I never installed the framework. The hard reboot happened in the middle of a titanium restore. I never restore system data/apps, and I've restored all the same apps before with no issues.
[One (M7) Original Android Development] FanDroid09:
[MENTION=4379011]poondog[/MENTION]

I'm at work now, but later this evening I'll try and get em all downloaded and give you a little break down with antutu numbers, and what I find as far as smoothness.

Also a list in order of best to worst battery life for all 8 tests.... :p
[One (M7) Original Android Development] ZeroInfinity:
Quick benchmark testing

Kernel:---------------- Antutu Score:

kk009_BR----------------26648

kk009_CF----------------27108 <------ awww yeahhhh

kk009_FA----------------26549

kk009_JO----------------26882

kk009_LK----------------26983

kk009_SM---------------27044

kk009_ST----------------26502 <----- why must you hurt me in this way?

kk009_XG----------------26731

Notes:

Took around 40 mins to benchmark all the tests and (took a few mins) to cool down the phone to make sure that it doesn't throttle.

No kernel tweak app used, all stock kernel settings. All these benchmarks were done exactly a minute after bootup lockscreen.
[One (M7) Original Android Development] FanDroid09:
Dammit... Took my glory. :mad:

haha.
[One (M7) Original Android Development] ghostENVY:
H , I was having the same Issue a while back . I'm not a noob by no means , so I was getting upset that wiping cache/dalvik wasnt working when trying to install Kangaroo. It wasnt until i did a full FUU reboot that my phone started to accept the kernel afterwards. I searched HTC One Development thread and I was able to find it maybe this will help .:highfive:
[One (M7) Original Android Development] dena994:
I spent 10 mintes looking for last aosp kernel but i hadn't found it..someone can tell me the number of the post or give me the link? Thanks

Inviato dal mio One utilizzando Tapatalk
[One (M7) Original Android Development] poondog:
<3

Thanks zero

Don't worry take your time :)

http://xdaforums.com/showpost.php?p=51466716&postcount=1431
[One (M7) Original Android Development] Large Hadron:
SM's pretty good. I confirm 27k antutu (for whatever benchmarks are worth), but more importantly it's snappy in real usage - certainly as good as anything else I've used. Sitting in standby (good signal, data and WiFi off) it lost 1% in 3 hours, though as is often the case when you see that type of thing it drops quicker than you expect at first when you start to use it again (I suspect the meter sometimes lags). Won't be able to do real battery tests and look at more than one, so will prob flash another tomorrow morning. But this one could be a keeper.

Viper 5.8, no cpu tweaks (except the default 384MHz screen off speed is probably set).
[One (M7) Original Android Development] myrigon:
Can now confirm st as fully stable. Battery within usual expectations for your kernels (v good). Going to try JO now.

##edit## jo test has markedly lower bench than st, by 1000~1500. Seems to drop framerate more often in 3d test.
[One (M7) Original Android Development] neniick:
kk009_BR----------------26459;26300;26402

kk009_CF----------------26074;26123;26060

kk009_FA----------------26605;26304;26618

kk009_JO----------------26304;26044;26297

kk009_LK----------------26235;26286;26453

kk009_SM---------------26693;26353;26488

kk009_ST----------------26208;26362;26412

kk009_XG----------------26259;26275;26276

My benchmark results.

Verstuurd van mijn HTC One
[One (M7) Original Android Development] poondog:
Screen off won't work because there is no sysfs for it

It should be set by HTC at 1026

Thanks all should be stable :)

Yeah I'm finding similar results

Cheers mate :)
[One (M7) Original Android Development] superleeds27:
Just posted this in the Battery Stats thread, RE:AOSP

http://xdaforums.com/showpost.php?p=51603618&postcount=2940

Im not a 'heavy' user at the minute, but surely standby should be better than that! My phone hates AOSP!
[One (M7) Original Android Development] poondog:
Why did you post that it's bad advertising :)

My battery is sooooo much better
[One (M7) Original Android Development] dictionary:
Do that same test, but don't enable the 2g toggle. I experienced the same thing when selecting that on AICP. Battery would drain crazy fast when screen was off. Put it back to normal, and all well. Definitely not the kernel. Giving Poondogs kernel a bad name. Lol
[One (M7) Original Android Development] superleeds27:
Wasn't to bad mouth your kernel, i know the kernel isn't the issue. I'll edit the post so people are aware of this.

I really do believe its my phone, Anything AOSP is horrible!

Edit: I enabled the 2g Toggle last night to try and stop the drain, although it's just as bad!
[One (M7) Original Android Development] poondog:
^^

I find AOKP to be good for m7

Yeah I know you're not intentionally, but it just seems so maybe for some users? No harm done, all good man

Perhaps try with AOKP :)
[One (M7) Original Android Development] superleeds27:
Yeah maybe ill try it.

Edited post in batt stats thread ;)
[One (M7) Original Android Development] poondog:
Cheers mate :)
[One (M7) Original Android Development] dictionary:
Agreed. I'd try AOKP. Slimkat gave me poor battery life, but I got exceptional with AOKP. Also try out the build from the developer of Elite/Lunar Kernel. His aosp build for m7ul is great.
[One (M7) Original Android Development] poondog:
Although slim runs great on my flo :)
[One (M7) Original Android Development] dictionary:
Yup. On my now deceased Flo, Slim is/was phenomenal.
[One (M7) Original Android Development] poondog:
I'm sorry to hear, what happened to the flo? On my though nothing beats sense
[One (M7) Original Android Development] dictionary:
Back pocket, car seat, applied downward pressure. Screen shattered. LCD still works, but digitizer is kaput. If the digitizer wasn't fused to the LCD I'd fix it myself. Part is like $90. Local shop says they want $120 to fix it. People sell them mint for $200+, so I'm at an impasse on fixing it. ;(

And I usually hate sense, lol. I only buy HTC for their build quality, but must admit sense 6 @ 360dpi changes all that. Mmmm
[One (M7) Original Android Development] Rad ryan:
[MENTION=4379011]poondog[/MENTION] 24 hours long test of cf. My subjective opinion is very nice. No dropped frames, smooth ui, great gameplay, good battery (for on-demand). Rom = Renovate svn r55. Here are my results from version cf (gsam reading was gotten from playing nba jam most of time hence why screen time is low, last pic is %/hr while browsing tapatalk and net) :
[One (M7) Original Android Development] Rad ryan:
[MENTION=4379011]poondog[/MENTION], in the next release would it be possible for you to apply the patch to enable an app to be able to accurately report the cpu times of all 4 cores at the same time? I think it would really help with your blind test to be able to see what frequencies are relating to the performance and battery the phone is currently getting.

Also, my cpu temp has been staying pretty high :( , not just on your kernel, but on all the new kernels. Do think you could use your genius :D to figure out a way to possibly have the temps slightly lower without sacrificing performance? The only way I can think of, and this is vague and general, would be to somehow increase the performance of the lower freq range (from bottom up to around 1350000) so the cpu doesn't hit the high frequencies as much. When I had my cpu underclocked to 1.35ghz my cpu temp stayed in the high 20's - low 30's :)

Lastly, I flashed 009xg and got bootloop, so I tried flashing 009br and it didn't boot. I then used the superwipe script to erase both cache and boot partition, then dirty flashed rom for the stock ramdisk /kernel, booted up, rebooted again, then booted to recovery, wipe both cache, install 009br and it booted fine and running great. Anyone who can't boot v009 try that. Is it possible that the ramdisk is somehow getting corrupted and that why some ppl have install issues?
[One (M7) Original Android Development] Large Hadron:
I've been busy enough that I've not been messing with the phone much the last day, so limited range of tests. But here are my impressions so far, for what they're worth:

SM: Antutu: 27k (27178, 26916)

UI feels smooth and snappy. No lags.

Drain ~1% in 3 hours standby (WiFi & data off), but seemed to drop the first couple of

percent faster than I'd expect once back in use.

LK: Antutu: 27k (27065, 26923)

UI smooth and snappy. Feels marginally more hesitant than SM, but

too borderline to be sure it's a real effect.

Drain 3% in 4.5 hours standby (WiFi & data off).

XG: Antutu: > 27k (27387, 27234)

On first use felt marginally more hesitant than the others. Just

small delays opening folder organiser, slight hesitation when

unlocking. But subsequently no problems. Probably just not preloaded something.

1% standby loss in 3.5 hours (WiFi & data off).
[One (M7) Original Android Development] FanDroid09:
Hmmm, will share my benchmark results in the next couple hours. I'm noticing that I have been getting consistantly higher antutu scores than others. Over 28k on most tests. Wonder why that is... I haven't touched kernel settings on any of them.

EDIT: RESULTS: ran antutu at least three times on each kernel. As far as smoothness goes, I didnt notice a big difference for the most part. Ran into some micro stutters on CF and XG. If i had to pick, I feel LK and BR MAY have been the smoothest.

Antutu: On average the scores come out pretty close. To be honest i'm seeing a variance of +/- a few hundred points, so the performance difference may not really be noticeable.

BR-28019, 28307, 28454

CF-28060, 28115, 28206

FA-28246, 28255, 28236

JO-28055, 28296, 28154

LK-28196, 28416, 28369

SM-27931, 28140, 28190

ST-27898, 28136, 28120

XG-28252, 28286, 28162
[One (M7) Original Android Development] myrigon:
I think maybe there are just little differences between handsets, also ROMs, and allowing for different apps etc. I've been using antutu x, which seems to be issuing slightly lower scores. My best benchmarks are on ViperOne, though my published ones are on IC sense 6.
[One (M7) Original Android Development] poondog:
Wait for nexus 7 2014 by HTC then :)

Nice results, thanks :)

Yeah I willl merge that CPU time stuff once this test is over

CPU temp should have very little to do with the kernel since it is mainly stock with optimizations. If the clocks etc have changed (only slimBUS is changed) then maybe it would be kernel. Otherwise, thermal will come in later :) Maybe I will drop some voltages soon, that always helps with battery and temp

Shouldn't need superwipe though, all you need is reflash rom. But idk what happened, seems fishy :) Ramdisk should not be the issue because I use anykernel, which basically will use the existing ramdisk you have with my zimage

Thanks :) Seems everyone is finding them all different lol

Which ROM? Something magic here :D
[One (M7) Original Android Development] dictionary:
Hopefully, if they do make it, they won't drop the ball like my HTC Flyer. Thing is collecting dust due to their horrible support, and lack of open sourcing things so we can fix it ourselves.
[One (M7) Original Android Development] poondog:
Its a Nexus, should be no problems :)
[One (M7) Original Android Development] FanDroid09:
Running latest Maximus. I believe its using the latest sense 5.5 base. Ran a few more benchmarks still rarely dipping below 28k :highfive:
[One (M7) Original Android Development] poondog:
Good old sense 5.5 :)

Proves benches aren't anything because sense 6 is way smoother.. but between kernel tests like these it will give an indication of which is best :) obviously though we can't compare results across roms and devices, only results from one person at a time :)

I'm prepping a 010+ release for when these tests are conclusive.. huge thanks to those who contributed <3
[One (M7) Original Android Development] FanDroid09:
Ya haha. I have a backup of Maximus, Viper, IC sense 6, and Slim. Bounce between them every once in a while :p

Exactly, as far as real world usage goes benchmarks are pointless haha.

Ya I'll agree with you there... Sense 6 is smooth as silk, can't wait till official base rolls out. Not to say the port isn't damn good.
[One (M7) Original Android Development] poondog:
I only have like 2 backups max at a time.. How do you fit them all lol

I just hope official base is smoother/as smooth, as HTC bases for m7 are getting slower and slower imo

Btw I'm working on fixing the no boot issue
[One (M7) Original Android Development] drsamratroy:
So these are my test results -

1. BR - 27126,27223,27132...one of the smoothest...dint lag at all... :good:

2. CF - 26965,26990,26929...the worst of the lot for me...stuttered quite a bit...least favorite... :eek:

3. FA - 27113,27065,26992...the smoothest...the best fps on asphalt too...my favorite :victory:

4. JO - 27113,27065,26992...very smooth too... :good:

5. LK - 27061,27168,26955...average...not bad...smooth enough...

6. SM - 26933,27052,26853...this too was average...

7. ST - 26986,27058,27096...was quite good... :good:

8. XG - 26900,26995,26946..dint like that much...stuttered sometimes...very average...

All these were on Viper 5.8.0. with theme...

Tested each kernel for around 3 hours so cant comment on battery life.

Also played Asphalt 8 on all of them...recorded FPS was around 27-29 in all the versions with FA topping it at 30 fps...

Also on 3DRating for OpenGL ES 2.0, BR recorded the highest reading of 3353...rest were around 3200 - 3300...

On Quadrant, JO recorded the highest 12299 for me, rest were around 11600 - 12200...

So, on my personal conclusion, these is how i would rate the versions -

FA>BR>JO>ST>LK>SM>XG>CF

Hope it helps... :highfive:

P.S. - dint have bootloops on any version...very stable...guys who are having it can wipe cache & dalvik b4 installin...sud help i think...
[One (M7) Original Android Development] FanDroid09:
Not easily, I cut down my music collection quite a bit, cleaned out some old stuff I don't listen to as much. Its safe on my laptop In case I need to cycle it back in haha :cool:

Pssshhhh... If it's not I'm sure the Roo will smooth it out :p

Hmmm so you figured out what's up with that? I flashed every test without a single problem.
[One (M7) Original Android Development] poondog:
Cheers for these tests, thanks for your input :)

It's not a user error afaik for no booting issue though unfortunately, something fishys going on

Yeah haha I guess, 32gb is enough
[One (M7) Original Android Development] RUUMan:
I just tried the cf version to judge battery life but under gsam is what I always check first. Some gsam stats. Ignore the screen on time . I am just showing The other stats

edit: cf seems to be identical with 004 just a bit more smoother
[One (M7) Original Android Development] drsamratroy:
Just so you know, i had installed the stockish Bulletproof & got the following results on the exact same settings :-

Antutu - 27305, 27230, 27305

Quad - 11964

3D - 3425

Asphalt - 30 fps

P.S. on a sidenote, have so got used to d2w & s2s that they almost feel like default in m7... missed it terribly in the test kernels... hope u execute them soon...Cheers
[One (M7) Original Android Development] poondog:
Bulletproof has way more development and things, I'm adding in slowly. I'm hoping to break 28-29k with stock clocks.. even 30 :D SO many things I have left untouched so far hahaha
[One (M7) Original Android Development] drsamratroy:
great... personally for me i loved ur Joey for its awesome smoothness, battery & thermals... plz don't forget abt that ;)
[One (M7) Original Android Development] poondog:
why would I forget :) This kernel is going to be my most worked on :)
[One (M7) Original Android Development] poondog:
Ok some tests for the people with booting issues :)

In my kangaroo dropbox folder

https://www.dropbox.com/sh/y46ps2d8t0xgb36/V5owYtMOH0

Please see if 005 boots, then 0061 :D Thanks
[One (M7) Original Android Development] joni2012:
Battery life number?

Enviado desde mi HTC One mediante Tapatalk
[One (M7) Original Android Development] myrigon:
[MENTION=4379011]poondog[/MENTION] , is there anything that still needs testing, other than the no boot cases?
[One (M7) Original Android Development] poondog:
?

Yeah those kernels are still not getting conclusive results :)

I'm working on other parts of the kernel now for the next update.

Someone please test 0061 in the drop box link, I'm 99% sure the booting issue is fixed cause I spent 2 hours debugging it lol

This weekend or just after will come 015 release :)
[One (M7) Original Android Development] Rad ryan:
24 hr test of 009br [MENTION=4379011]poondog[/MENTION] This v009BR results. My subjective opinion is that this is a great version. The UI is smooth and fluid, the battery life seems better than CF version, although I did have a little more than occasional stuttering on NBA Jam and it's graphics scores were consistently lower than CF version in Antutu(not by much though), but overall it is excellent version. In these results I will include a couple runs on CF-bench and here is why I decided to do that ( http://xdaforums.com/showthread.php?p=1535394 . Let me know if you want me to keep including CF-bench in results, it essentially is a pure cpu/ram benchmark. Here are my results for 009br(the last shot is %/hr this morn while browsing Tapatalk, making this post, and 1 game of NBA Jam which is where the numbers change to - 10% and up to - 30% then Tapatalk after. Also, the first 2 gsam shots is from yesterday while playing games mostly and 3rd one is from this morning, and the last gsam shot is yesterday wit no game play only net browsing) :

Next up? any request poondog or anyone?
[One (M7) Original Android Development] poondog:
The candidates are

BR

LK

SM

ST

CF

:)

Although I'm finding the ones that are the smoothest seen to give crap benchmarks.. Lol

The test I'm on now has lower scores but is smooth and sips battery politely so far
[One (M7) Original Android Development] RUUMan:
what is the difference between 0005 vs 0061?
[One (M7) Original Android Development] herwegan:
56 ;)
[One (M7) Original Android Development] Mikey:
My quick testing with: Rom- IC2.1.3-Factory Reseted

I ran 3 AnTuTu Benchmark tests per kernel

Kernels 005 0061 and 009_BR (for now)

https://drive.google.com/folderview?id=0B2TainPw3RB2S1BwbUVOdlNZQUU&usp=sharing

Oh, no kernel tweaks either of any sort