yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Original Android Development] ->---:
I searched for a link to the app thread in your signature but didn't find some.

Some posts earlier I read something about 600MHz GPU clock. Is that implemented? In my case the app does only show 450 as maximum.

Thx for the info about WLAN. Why is that broken and needs a additional flash every now and then? I'm asking just for interest.
[Xperia Z1 Original Android Development] gallardo5:
Ive just noticed that your kernel doesnt support init.d scripts. Have you got any plans on implementing it?
[Xperia Z1 Original Android Development] Androguide.fr:
The app thread is in the Xperia Z1 Themes & Apps forums, here: http://xdaforums.com/showthread.php?t=2663224 (I can't add anything to my signature, it's already at max length)

600MHz GPU OC is indeed implemented, but for some reason it doesn't work for some people while it does for others on the same build, couldn't identify why yet.

About wlan, basically Sony's 4.3 driver was breaking almost as soon as you do any changes to the kernel, so the FreeXperia team managed to implement a custom wlan driver (pronto wlan), built as a module and which doesn't break.
[Xperia Z1 Original Android Development] Androguide.fr:
Yeah, I will add init.d support soon, I didn't realize there wasn't up until yesterday, I kinda assumed the CM kernel had init.d support implemented.

EDIT: after investigation, init.d support is indeed implemented on the kernel side, the sysinit call is in init.cm.rc:

# sysinit (/system/etc/init.d)
service sysinit /system/bin/sysinit
user root
oneshot
disabled

And the sysinit code itself (in Omni at least):

#!/system/bin/sh

export PATH=/sbin:/system/sbin:/system/bin:/system/xbin
/system/bin/logwrapper /system/xbin/run-parts /system/etc/init.d

I don't see what's wrong, need to look into that more.
[Xperia Z1 Original Android Development] Poesini:
Seems Doom committed the changes for LCD Control (although I would like is gamma control) :)
[Xperia Z1 Original Android Development] Androguide.fr:
Yup, merged those this afternoon ;)

I'm almost done implementing the control in Pimp My Z1, then I'll release both the new kernel build and the new app build.

Next kernel build might take a little while though, as I'm going to have to rebase my kernel onto the new caf-based CM kernel, with the 4.4 Sony sources merged.

Thankfully, [MENTION=3877985]prbassplayer[/MENTION] had seen the merge coming and informed me so I started to re-implement some of the features onto the new sources this week (see this branch of my kernel)
[Xperia Z1 Original Android Development] prbassplayer:
I merged earlier to slim, with the exception of a av patch I need., pain in the butt lol. Do you keep your device on (no reboot) for more than 24 hours? I've noticed after about 18hours a nasty memory leak manifests itself. Could you keep an eye on it?
[Xperia Z1 Original Android Development] Androguide.fr:
Sure, I haven't tested a build with the new sources long enough to get this leak but if it manifests I'll make sure to save the kmsg and let you know.
[Xperia Z1 Original Android Development] Poesini:
I would love a CAF ROM too yay :p
[Xperia Z1 Original Android Development] Androguide.fr:
2014-04-04 build

Changelog

Downloads
[Xperia Z1 Original Android Development] CappyT:
tested, not booting... keeps rebooting on kernel logo and status led is not blinking, like it was before.

Cannot even enter in CWM.
[Xperia Z1 Original Android Development] prbassplayer:
Yup I actually flashed the kernel to debug a problem I'm having f2fs with my setup ended up fastbooting my kernel back. No logs wouldn't get initialized enough to get in to recovery lol
[Xperia Z1 Original Android Development] madalone:
same here. flashed 20140403 through fastboot and all is back to normal.
[Xperia Z1 Original Android Development] Androguide.fr:
Well that's pretty weird.

Here is the f2fs build I have on my device: http://d-h.st/NdM i know for a fact this one works fine as it's the one I'm running right now and used to debug the color calibration control in Pimp My Z1.

I'll take a look and rebuild a working ext4 build later today.

EDIT: after rebooting the device indeed bootlooped a couple of times before the purple led, but on the 3rd it booted fine, strange.

Just give it some time if you have the issue I guess.
[Xperia Z1 Original Android Development] Juzman:
The ext4 build is running fine on mine. :)
[Xperia Z1 Original Android Development] lowrider_05:
with this and the other 04042014 kernel i can´t go to recovery it just flashes a blank backlight but no recovery had to reflash 0403 to get recovery back.
[Xperia Z1 Original Android Development] gallardo5:
Latest F2fs build is working fine for me with 3/04 cm nightly, didnt updated to 4/04 nightly as it was causing bootloop for me.
[Xperia Z1 Original Android Development] Androguide.fr:
Yeah, CM nightlies more recent than 04/03 are probably not gonna work until I get the caf-based/Sony 4.4 branch up to speed.
[Xperia Z1 Original Android Development] gallardo5:
Are you planning to do that? I read in cm thread (not fxp one, byt official in general section) that sony 4.4 branch fixes camera for good and is makes rom much smoother
[Xperia Z1 Original Android Development] Androguide.fr:
Yes I do, I already started getting some of the features onto the new sources, here's what I posted yesterday about that:
[Xperia Z1 Original Android Development] gallardo5:
As your app doesnt support UV but kernel does, could you tell me the path to voltage table? I would like to make init.d script for it but couldnt find it anywhere. Thanks :)
[Xperia Z1 Original Android Development] Androguide.fr:
Sure, the path is:

/sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

I'll try to get voltage control implemented in the app soon.
[Xperia Z1 Original Android Development] prbassplayer:
No it doesn't. It's better but still flaky. Every other problem seems to be gone though, (except that random memory leak)
[Xperia Z1 Original Android Development] gallardo5:
What do you mean by "fluky"? Sorry, didnt understand you there
[Xperia Z1 Original Android Development] prbassplayer:
Driver is slow to initialize and sometimes doesn't do it properly, giving me a still image in preview and afterwards a" cannot connect", requiring a reboot. It's flaky, off, not right. Don't get me wrong it seems a lot better but it's not fixed. As far as I know they are still using jb camera stack and blobs. Not sure why, I'd imagine my blobs/camera stack where giving to much trouble.
[Xperia Z1 Original Android Development] Androguide.fr:
About the camera, I noticed they still didn't merge this commit, which I merged like 3 weeks ago.

It really helps, it fixes the still frames (you have a black viewfinder instead of the still image) and makes the camera start quite a bit faster (as in the black viewfinder disappears much faster than the still frame would).

It also seems to help with the camera instance not being closed properly by the app, causing the "Cannot connect to camera" dialog, although it doesn't fix it entirely.

I did post about it in the FXP thread but I guess it got unnoticed or they had seen it but don't want to merge it for some reason.
[Xperia Z1 Original Android Development] gallardo5:
Is this commit for rom or kernel? What I want to know is if I will have CM with your kernel, will this commit be there or CM has to merge it to their rom? So many questions today but I feel like taking carw of my phone today :) thanks in advance
[Xperia Z1 Original Android Development] Androguide.fr:
This commit has been implemented in my kernel for about 3 weeks now, if you're running my kernel then you aleady got it.
[Xperia Z1 Original Android Development] Nonda95:
DT2W works better than in DoomKernel?

Wysłane z mojego C6903 przy użyciu Tapatalka
[Xperia Z1 Original Android Development] Darkmasterhk:
sdCard issue

Hey, I just tried this kernel and expect 2 little problems it's awesome.

First your 04.04. has no/not working recovery.

Second I'm not able to mount my sd card (64gb), I tried it

with 2 filesystems ext4/exfat. (log from mouting try exfat attached)

Anyone any idea?
[Xperia Z1 Original Android Development] ekanix20:
No

Skickat från min C6903 via Tapatalk
[Xperia Z1 Original Android Development] gallardo5:
Nevermind, got it now
[Xperia Z1 Original Android Development] Juzman:
Okay, using Pimped-Kernel-honami-ext4-20140405.zip I cannot enter CWM. However with Pimped-Kernel-honami-ext4-20140403_2254.zip I can.
[Xperia Z1 Original Android Development] MacSeoin:
Same for me, on f2fs 0404 and 0405 I cannot enter recovery, 0403 is fine though!
[Xperia Z1 Original Android Development] Androguide.fr:
Thanks a lot for reporting.

It's really nice to see people actually attaching logs to their bug reports (let alone ALL the logs like you did :good:), kudos.

I ordered a 64gb sdcard this morning, so I'll definitely try to fix the exFAT support asap.

The recovery is indeed broken on the latest build, please use the previous one instead (04/03).
[Xperia Z1 Original Android Development] Androguide.fr:
Yes it does, DoomKernel v11 is using the v1.1 of MohammadAG's DT2Wake, the 04/03 and later builds of Pimped Kernel include the v1.2 (latest).
[Xperia Z1 Original Android Development] juicio90:
Sorry fot of topic.. But, can I try this with terminal? Or ADB?
[Xperia Z1 Original Android Development] Androguide.fr:
Yes, either.

Just drop a recovery image named recovery.img in /sdcard (or wherever you want, just modify the path in the command).

And of course if you're using adb then prepend adb shell to the dd command.
[Xperia Z1 Original Android Development] ekanix20:
Well it works, but your phone will never go in to deep sleep.

Skickat från min C6903 via Tapatalk
[Xperia Z1 Original Android Development] Destroyedbeauty:
Or can't we just use [NUT] DualRecovery as an temporary solution until built-in recovery is patched & fixed?

EDIT: Hoped this would work, but no..
[Xperia Z1 Original Android Development] Kingcool88:
[MENTION=4752917]Androguide.fr[/MENTION]

Bootloop on latest weekly of Slimrom!

Dont know if this log helps..
[Xperia Z1 Original Android Development] prbassplayer:
I believe he hasn't released can kernel yet, slim is running Sony 4.4 drop so it's a new kernel.
[Xperia Z1 Original Android Development] ilia1985:
Prbassplayer... Any updates on nasty memory leak?
[Xperia Z1 Original Android Development] prbassplayer:
Should be fixed in the weekly. I haven't had it in 54 hours of up time.
[Xperia Z1 Original Android Development] Poesini:
Since Omnis latest doesnt work, I migrated to Slim until Omni gets fixed and I havent had a bootloop (Using 0405 build) with 04/03 kernel (havent tested 04/04 since people reported bootloops)

Eagerly waiting CAF kernel (and ROM too?) !!! :)
[Xperia Z1 Original Android Development] Kingcool88:
Tnx for the info!

Skickat från min Xperia Z1 via Tapatalk
[Xperia Z1 Original Android Development] ->---:
You seem to collect governors. Ever heard of this one?

https://github.com/lowtraxx/boostedASSv2

It was developed for good old Milestone 2 and was an advancement from SmartassV2.

http://rootzwiki.com/topic/21493-cpu-gov-boostedassv2-public-release-and-source-f-u-moto-release-41112-2259/
[Xperia Z1 Original Android Development] Androguide.fr:
Well, the more choice the better IMO.

Thanks for the suggestion, never heard of this one, I'll take a look.

Although you usually can't just drop the governor from another device and have it compile properly, it needs to be customized to use the SOC-specific parts that talk to the CPU (to simplify).
[Xperia Z1 Original Android Development] Androguide.fr:
To keep you guys waiting here's a (ext4) caf kernel for Slim or the newer CM nightlies, with Sound Control and the camera commit I pointed-out earlier:

http://d-h.st/ziu
[Xperia Z1 Original Android Development] Poesini:
I kind of disagree with having lots of governors which people hardly ever use...

We can get the best governors (Top of them) and get a clean kernel

Also, what is the possibility to get cpuquiet? I liked it a lot

Another thing would be Smartmax governor which is a big boy in terms of battery life while keeping the device snappy enough

Anyway, just my 2 cents and I'm still waiting for f2fs CAF kernel :p
[Xperia Z1 Original Android Development] prbassplayer:
I've never understood the fascination with outdated governors?
[Xperia Z1 Original Android Development] Destroyedbeauty:
The more, the better. As long they're optimized and adjusted for the quad core-SoC that is powering our Z1 phones so..
[Xperia Z1 Original Android Development] lowrider_05:
for example, i love the nightmare governor its responsive and quite battery friendly. I never heard of this one before but i am glad it´s in the list.
[Xperia Z1 Original Android Development] MacSeoin:
Hey guys I'm on Slim build 4 and this kernel didn't boot, just hangs on the Sony splash! Anyone else get this?
[Xperia Z1 Original Android Development] madalone:
yup, same here.. :/
[Xperia Z1 Original Android Development] soulzero:
Same.
[Xperia Z1 Original Android Development] Destroyedbeauty:
Intellidemand and Deadline combo = battery will nearly never die!
[Xperia Z1 Original Android Development] lowrider_05:
thanks for the advice but intellidemand has always a little stutter for me but i will try if deadline saves me some juice over fiops, wich i use now.
[Xperia Z1 Original Android Development] _Garry_:
Is this with source of sonys 4.4???

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] MacSeoin:
It doesn't work m8 just hangs on Sony splash
[Xperia Z1 Original Android Development] Androguide.fr:
Not sure if [MENTION=3877985]prbassplayer[/MENTION] released the CAF/4.4 builds yet or if he's just using those as personal builds right now.

If he hasn't, then previous Pimped Kernel builds will work just fine.

This modded ext4 cm kernel I released yesterday works on the latest CM nightlies, and is based on the new caf-based CM kernel.
[Xperia Z1 Original Android Development] ilia1985:
It works fine here... Were you previously using f2fs version?
[Xperia Z1 Original Android Development] soulzero:
Fresh install formatted internal card so should be working. Ext4
[Xperia Z1 Original Android Development] MacSeoin:
Yh but I then changed to carbon stock and then slim stock both are ext4!?

Only problems with them are the WiFi hotspot bug, at least for me!
[Xperia Z1 Original Android Development] _Garry_:
I just installed your kernel.

Works fine here.

[MENTION=4752917]Androguide.fr[/MENTION]

Latest SlimKat weekly release use CAF so your "test"-kernel runs smooth.

[MENTION=4136455]slimka[/MENTION]t users:

Just tested on official and couldnt get it running.

So:

If you want to test the kernel posted a few pages back, then you have to run latest weekly.

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] soulzero:
God just installed Pimped-Kernel-honami-ext4-20140405 on pacman and now can't access recovery.. The phone won't boot up neither

What file should I fastboot? Where can I get it?
[Xperia Z1 Original Android Development] MacSeoin:
I'm on the latest weekly! Build 4 right?
[Xperia Z1 Original Android Development] ilia1985:
Latest weekly is 4.2... 4 is the official one
[Xperia Z1 Original Android Development] madalone:
doh! i was! hehe going to install the ext4 version see what happens (:
[Xperia Z1 Original Android Development] MacSeoin:
Up and running now :D
[Xperia Z1 Original Android Development] Androguide.fr:
Fastboot the 04/03 build, you can grab it here: http://d-h.st/rdu

You probably won't have wifi afterwards, just flash the zip in recovery or manually move the included /system/lib/modules/wlan.ko
[Xperia Z1 Original Android Development] Destroyedbeauty:
If you're using Fauxclock - tweak the Intellidemand by lowering up_threshold to 88-95 spectrum, and see if it's improving performance and smoothness.
[Xperia Z1 Original Android Development] juicio90:
Man sorry but dont work.

u0_a53@honami:/ $ su

img of=/dev/block/platform/msm_sdcc1/by-name/FOTAKernel <

/dev/block/platform/msm_sdcc1/by-name/FOTAKernel: cannot open for write: No such file or directory

1|root@honami:/ #

Edit: work, but i have problem with unmount sdcard for recovery
[Xperia Z1 Original Android Development] prbassplayer:
But that's just it most are very old versions of interactive, ondemand

and conservative that have been tweaked then hacked to death to be somewhat compatible with our newer devices. Interactive can probably outperform the lot of them, and it's tweak able. Intellideman is another story, based on on-demand is still constantly being worked on. Obviously this is just my 2 cents but more isn't always better.

Weekly 4.2 runs on caf
[Xperia Z1 Original Android Development] Poesini:
I concur in the useless use of outdates and co-existence of the same purpose governors and/or schedulers.
[Xperia Z1 Original Android Development] Destroyedbeauty:
Maybe you are right, I am no kernel developer or advanced Android hacker & modder, just a newbie that is still learning new things everyday on how Android is working..
[Xperia Z1 Original Android Development] Androguide.fr:
Yeah, you're right, of course most governors are based off of interactive, ondemand or conservative, or based off of other governors that were themselves based on those "base" governors.

But I don't think iterative improvement is a bad thing, and having more SOC-specific tweaks and screen-aware/GPU-aware governors (like intelliactive) can really be a benefit over the more generic governor they're improving upon.

I'm not sure we can say that any governor outperforms the others, I think it simply depends on what you're expecting from it in terms of power savings vs performance.

As governors are pretty much self-contained and have no side-effects, the more choice the better IMHO.

I might do a run of benchmarks to try and compare some of the governors included in the kernel sometime soon.
[Xperia Z1 Original Android Development] prbassplayer:
I get that "it won't hurt" but do you really think we can modify them and better than qcom's engineers over at code Aurora? The 3 basic governors used from caf are hardly generic. And if you don't like something specific open an app like trickster mod and tweak it. I want to be clear I'm not trying to come off as an ars I'm legitimately interested in this topic. If you don't want it had here I'll move it elsewhere :)
[Xperia Z1 Original Android Development] ->---:
Thx for explaining. :good: I am not firm in all the details of Linux based operating systems. I just try all I know from DOS/Windows environment and what I can find in a quick way with Google. :D

Do you mean the stock kernel or the pimped one? Is it possible that there was one version of pimped, where the certain file was buggy in a case that it couldn't be overwritten by following releases?
[Xperia Z1 Original Android Development] Androguide.fr:
I'm all for debate, no problem ;)

I'm pretty sure the "main players" of the custom android kernel scene could very well get an engineer position at Qualcomm and don't feel out of place.

Especially faux, just take a look at his resume, he wrote the Operating System used on Boeing planes for advanced flight control, wrote a real-time multi-threaded OS for PowerPC, and these are just a tiny examples, he's genuinely an expert in the field of OS & low-level development and led many multi-million dollar projects - prototype planes for DARPA, wtf?! - (not trying to be a french chauvinist, btw^^).

While I'm well-aware that an independent developer working alone can't achieve the amount of work of an entire team, I'm pretty sure that an independent developer can think outside the box and improve upon the work of that team.

And I think it's like that in pretty much any area of open-source, and it's the beauty of it, to me.

No, something seems to limit the amount of frequencies the GPU can use, and some GPUs pick-up the low-range (27 - 450) while others pick-up the "normal" one as intended (200 - 600).

Maybe there is some kind of GPU binning on the S800, I need to research that.
[Xperia Z1 Original Android Development] ->---:
Interesting. In the table you posted to the benchmark-thread, there were 2 frequencies used twice - 320000000 and 200000000. In my case, if I would remove this doublets, the amount of different freqs in the gpu_available_frequencies would exactly fit to all different frequs you posted.

Edit:

Found that http://www.androidbeat.com/2013/09/difference-snapdragon-800-2-2ghz-2-3ghz/
[Xperia Z1 Original Android Development] prbassplayer:
Faux is the exception. Like I said his governors like intellidemand is one of the few exceptions for 2 reasons. 1 he does a lot of upstream from code Aurora for it 2 he is actively working on it. It's governors like smart-ass or however other dozen governors that is based on very old code was slightly modified back then and besides some basic stuff to get it to work is mainly unchanged for months/years
[Xperia Z1 Original Android Development] Androguide.fr:
Yeah, I have to agree that the majority of governors with "cool names" are most likely not that great.

But I'm sure there's a number of custom governors aside from faux's which are still maintained, although I'd have a hard time telling which ones.
[Xperia Z1 Original Android Development] Androguide.fr:
Interesting, I didn't know higher-binned S800 came with higher GPU frequencies as well, don't know how I missed that.

But still, I had reports from people with a PVS bin of 5 having this issue and people with PVS 2 not having it.

You're right, I'll try removing the useless 27MHz freq (although I'm pretty sure if it's there it's for a reason) and remove some duplicates.

We'll see if it fixes the issue, but that's still very strange that it differs from a device to another on the current builds, there has to be something causing that, just need to figure out what.

[MENTION=3877985]prbassplayer[/MENTION] this discussion got me intrigued, I'll definitely do some benchmarks once I re-add the governors onto the caf sources.

But it's hard to benchmark power saving and balance between performance/battery, and as raw performance doesn't mean much in terms of governors, not sure how I'm gonna do it.
[Xperia Z1 Original Android Development] _Garry_:
I wonder if the higher bins in our Z1 are using MSM8974 or MSM8974AB

Well back to benchmarks.

The main problem is that battery optimized govs are different to speedy ones, and to top it all a z1 aint a z1.

Govs needed to be tested by using or not using your phone.

So i prefere infos about govs - pro/ contra- and choose depending on my phone and usage.

I dont know if its possible for the Z1, but isnt it possible to choose 2 govs for the kernel? I mean for example use ondemand for deep sleep, and use intellactive for normal usage.

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] Androguide.fr:
I don't think so, I could implement a service in Pimp My Z1 to change the governor when the screen is off, but it might use the little battery you'd save by doing that I guess.

For the benchmark, I was thinking maybe trying to play GTA San Andreas for say 30min, and record the CPU activity during that, as well as writing down the battery level before/after.

Then leaving the device unused for a night, and writing down the battery level before/after. That for each governor to benchmark.

It might be a long process though, gotta love GTA and sleeping^^ Not very accurate too, but if you guys have ideas, let me know.
[Xperia Z1 Original Android Development] prbassplayer:
This. AFAIK it can only be done at a higher level like an app. You could modify a governor to do things differently when screen is off zest think that would require more "listeners" en more water cycles. But my c is meh
[Xperia Z1 Original Android Development] _Garry_:
I just thought about this way:

Sleep gov: ondemand

Normal gov: pegasusq

When screen off gov is running Sleep, when you wake up phone - screen on - it just changes to Normal.

Aint that a simple way? So even when dt2w is active its using Sleep, and the "active" part wont trigger Normal.

Just thinking about "listeners" and that was my idea.

Gesendet von meinem Xperia Z1 mit Tapatalk