[KERNEL][A510/A700][07/30] Z-Kernel Beta

dadecamp · Apr 13, 2014

No luck for me.I've had several random reboots. Going back to Pac Man. Thanks for your efforts. I will follow your progress.

Sent from my HTC6525LVW using Tapatalk

Sterist · Apr 14, 2014

sounds like you're using ART and/or crossbreeder

dadecamp · Apr 14, 2014

Sterist said:
sounds like you're using ART and/or crossbreeder

No art or crossbreed

Sent from my A700 using Tapatalk

chacal1906 · Apr 16, 2014

Thanks for your kernel !
I love it !

thanks for your work.

Elibl · Apr 17, 2014

really great stuff here amazing to read. @Ziyan keep on the track your work is highly appreciated

I'll may build an a510 version and try...

Gesendet von meinem Galaxy Nexus mit Tapatalk

Ziyan · Apr 18, 2014

Could someone please post the A510/A700's boot partition size? Just in case I decide to add something, lol...
Anyways, I'm still working on fixing max frequencies over the 10th step (1150 mhz)... something got messed up there

Elibl · Apr 18, 2014

Ziyan said:
Could someone please post the A510/A700's boot partition size? Just in case I decide to add something, lol...
Anyways, I'm still working on fixing max frequencies over the 10th step (1150 mhz)... something got messed up there

Code:

Target boot image: /home/eli/android/system/out/target/product/a510/boot.img
/home/eli/android/system/out/target/product/a510/boot.img maxsize=8562048 blocksize=4224 total=4241408 reserve=88704

@Ziyan: fyi you deleted picasso_m_defconfig (A510) in your last commit it's totally the same configuration as the same hardware only resolution differs

i tried it on a510 and it worked the first time but then after doing an update of ParanoidAndroid and flashing the kernel again it always froze directly after boot process will get a dmesg the next time

so what are your plans are you even considering to go up to 3.4

if it's even possible^^

so here is an a510 version with ParanoidAndroid ramdisk

Ziyan · Apr 18, 2014

Elibl said:
Code:

Target boot image: /home/eli/android/system/out/target/product/a510/boot.img /home/eli/android/system/out/target/product/a510/boot.img maxsize=8562048 blocksize=4224 total=4241408 reserve=88704

@Ziyan: fyi you deleted picasso_m_defconfig (A510) in your last commit it's totally the same configuration as the same hardware only resolution differs

i tried it on a510 and it worked the first time but then after doing an update of ParanoidAndroid and flashing the kernel again it always froze directly after boot process will get a dmesg the next time

so what are your plans are you even considering to go up to 3.4 if it's even possible^^

so here is an a510 version with ParanoidAndroid ramdisk

Thanks, looks like we've got plenty of space left (at least for a kernel).
Yeah, I deleted picasso_m_defconfig, because I didn't update it with the changes, so it was way behind, and difference is originally only one line between them, so I'll just recreate it when I fix the issue with the freq's :highfive:
As for the versions, 3.2 seems okay (nvidia updated their tegra kernel to 3.2), 3.4 would be a lot harder. I think I may try 3.2 in the future, after 3.1 is completed.

Elibl · Apr 18, 2014

Ziyan said:
Thanks, looks like we've got plenty of space left (at least for a kernel).
Yeah, I deleted picasso_m_defconfig, because I didn't update it with the changes, so it was way behind, and difference is originally only one line between them, so I'll just recreate it when I fix the issue with the freq's :highfive:
As for the versions, 3.2 seems okay (nvidia updated their tegra kernel to 3.2), 3.4 would be a lot harder. I think I may try 3.2 in the future, after 3.1 is completed.

Ow yeah that sounds incredible this will push the devices a lot

thanks a lot for your work

Not like recovery^^ needed to use lzma compression for kernel and ramdisk to fit twrp 2.7 size

Yeah I also just copied mf defconfig and changed that line to m one

Gesendet von meinem Galaxy Nexus mit Tapatalk

Elibl · Apr 18, 2014

so here is a kmsg of a freeze it only happens when it optimizes apps after cache dalvik wipe i think due to overheating cpu and after that it always freezes instantly after boot maybe it will start up again after cool down...

Ziyan · Apr 18, 2014

Elibl said:
so here is a kmsg of a freeze it only happens when it optimizes apps after cache dalvik wipe i think due to overheating cpu and after that it always freezes instantly after boot maybe it will start up again after cool down...

I think you should take a look at logcat too, we may see something going on there. The last message came 107s after booting. At 94s, the CPU temp was 67c, that's not that bad. Anyways, I'll modify EDP a bit in the next version, so it will throttle at around 73c.

Elibl · Apr 18, 2014

Ziyan said:
I think you should take a look at logcat too, we may see something going on there. The last message came 107s after booting. At 94s, the CPU temp was 67c, that's not that bad. Anyways, I'll modify EDP a bit in the next version, so it will throttle at around 73c.

here you go first one is freeze while optimizing the second one successful boot up but unable to unlock (no touch recognition) only able to wake up screen not even able to lock it again

and the tab is really getting hot...

Ziyan · Apr 18, 2014

Elibl said:
here you go first one is freeze while optimizing the second one successful boot up but unable to unlock (no touch recognition) only able to wake up screen not even able to lock it again

and the tab is really getting hot...

Ok, try disabling OC in the defconfig. I think it's the combination of OC + UV, some devices can't handle both.

Elibl · Apr 18, 2014

Ziyan said:
Ok, try disabling OC in the defconfig. I think it's the combination of OC + UV, some devices can't handle both.

ok thx will do so when i've got time maybe this afternoon

Elibl · Apr 18, 2014

Ziyan said:
Ok, try disabling OC in the defconfig. I think it's the combination of OC + UV, some devices can't handle both.

ok i disabled ultimate cpu oc and this way it finally was usable also after optimizing process. got 12384 on antutu. but the first time i booted after dalvik and cache wipe i got a bootloop log showing something like:

Code:

I/auditd  ( 1425): Starting up
E/auditd  ( 1425): Failed on audit_set_pid with error: Protocol not supported
I/auditd  ( 1425): Exiting
V/Sensors (  552): void cb_onMotion(uint16_t)
I/auditd  ( 1429): Starting up
E/auditd  ( 1429): Failed on audit_set_pid with error: Protocol not supported
I/auditd  ( 1429): Exiting
I/auditd  ( 1433): Starting up
E/auditd  ( 1433): Failed on audit_set_pid with error: Protocol not supported
I/auditd  ( 1433): Exiting

in a loop but next boot was ok

hope all this stuff may help you

Ziyan · Apr 18, 2014

Elibl said:
ok i disabled ultimate cpu oc and this way it finally was usable also after optimizing process. got 12384 on antutu. but the first time i booted after dalvik and cache wipe i got a bootloop log showing something like:

Code:

I/auditd ( 1425): Starting up E/auditd ( 1425): Failed on audit_set_pid with error: Protocol not supported I/auditd ( 1425): Exiting V/Sensors ( 552): void cb_onMotion(uint16_t) I/auditd ( 1429): Starting up E/auditd ( 1429): Failed on audit_set_pid with error: Protocol not supported I/auditd ( 1429): Exiting I/auditd ( 1433): Starting up E/auditd ( 1433): Failed on audit_set_pid with error: Protocol not supported I/auditd ( 1433): Exiting

in a loop but next boot was ok

That's a selinux error, it should work as it's enabled in the kernel. What's the output of the last two command?
su
getsebool
getenforce

Elibl · Apr 18, 2014

Ziyan said:
That's a selinux error, it should work as it's enabled in the kernel. What's the output of the last two command?
su
getsebool
getenforce

in_qemu --> off

and

enforcing

Ziyan · Apr 18, 2014

Here's a test build. I don't have the A700 with me till next week, so someone (who's not afraid to flash back the previous version if this doesn't work) please test it. I'd be so happy if it'd fix the problem with max frequencies... I need a dmesg too after setting a max frequency between 1400 and 1700 mhz :good:

Elibl said:
in_qemu --> off

and

enforcing

I think this build fixes that, it turns out that CONFIG_AUDIT_GENERIC was turned off for some reason. I managed to create such a messy commit (sorry, git said me to finish the cherry-pick before I can commit other files, so I did that lol I wasn't excepting this) that I recommend you to just copy the file and edit the lines you need again

Elibl · Apr 27, 2014

Ziyan said:
Here's a test build. I don't have the A700 with me till next week, so someone (who's not afraid to flash back the previous version if this doesn't work) please test it. I'd be so happy if it'd fix the problem with max frequencies... I need a dmesg too after setting a max frequency between 1400 and 1700 mhz :good:

I think this build fixes that, it turns out that CONFIG_AUDIT_GENERIC was turned off for some reason. I managed to create such a messy commit (sorry, git said me to finish the cherry-pick before I can commit other files, so I did that lol I wasn't excepting this) that I recommend you to just copy the file and edit the lines you need again

No one here to test? I'm busy at the moment so sorry no time...

Gesendet von meinem Galaxy Nexus mit Tapatalk

Moscow Desire · Apr 29, 2014

I'll give it a shot in a couple of days. Have work right now pretty busy, but definately interested in pitching in.

Pretty sure it will probably bootloop as I run stock 4.2 JB.

[KERNEL][A510/A700][07/30] Z-Kernel Beta

Senior Member

Senior Member

Senior Member

Member

Senior Member

Recognized Developer

Senior Member

Attachments

Recognized Developer

Senior Member

Senior Member

Attachments

Recognized Developer

Senior Member

Attachments

Recognized Developer

Senior Member

Senior Member

Recognized Developer

Senior Member

Recognized Developer

Senior Member

Retired Senior Moderator

Similar threads

Top Liked Posts