Dazzozo changed the topic of #huawei-g300 to: #huawei-g300 | G300 & Y300 innovation station | home of the G300's CyanogenMod port and mnupea | http://irclog.whitequark.org/huawei-g300 | https://dazzozo.com/L.png
luca020400 has quit [Ping timeout: 264 seconds]
luca020400 has joined #huawei-g300
luca020400 has quit [Remote host closed the connection]
luca020400 has joined #huawei-g300
luca020400 has quit [Ping timeout: 256 seconds]
luca020400 has joined #huawei-g300
Ghost|afk is now known as Shadowghoster
Flea997 has joined #huawei-g300
Flea997 has quit [Remote host closed the connection]
Solitary has joined #huawei-g300
Shadowghoster is now known as Ghost|afk
luca020400 has quit [Ping timeout: 250 seconds]
gregor160300 has joined #huawei-g300
Solitary has quit [Remote host closed the connection]
gregor160300 has quit [Quit: Leaving]
Solitary has joined #huawei-g300
Included has joined #huawei-g300
<Included> hello, can I ask a few things?
luca020400 has joined #huawei-g300
luca020400 has quit [Excess Flood]
luca020400 has joined #huawei-g300
luca020400 has quit [Read error: Connection reset by peer]
luca020400 has joined #huawei-g300
xhxhd has joined #huawei-g300
luca020400 has quit [Ping timeout: 252 seconds]
xhxhd has quit [Client Quit]
luca020400 has joined #huawei-g300
<Included> somebody?
<luca020400> Hi
<Included> hi
<luca020400> What's your problem ?
<Included> got CM11 and and suddenly I lose reception
<luca020400> Impossible xd
<Included> restart solves it
<Included> but I wonder what it causes
<Included> I didn't unlock the bootloader officialy, but I don't use 3G
<Included> so it shouldn't be related
<Included> Dazzozo, could you spare a bit of your time?
<luca020400> Without logcat / kmsg we cannot fix anything
<luca020400> We aren't magician
<Included> I know
<Included> it happens when I'm not looking
<Included> probably when the phone is idle
<Included> which logs will you need?
<luca020400> Without logcat / kmsg we cannot fix anything
<Included> so /dev/kmsg is the one?
<luca020400> It should in y300
<Included> have g300
<Included> cat /dev/kmsg says no invalid argument
<Included> so should I 'logcat -f file' ?
<Included> as root
luca020400 has quit [Ping timeout: 246 seconds]
luca020400 has joined #huawei-g300
<Included> luca020400, I will fully charge it, and start logging /proc/kmsg and logcat then
luca020400 has quit [Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )]
luca020400 has joined #huawei-g300
luca020400 has quit [Client Quit]
luca020400 has joined #huawei-g300
juan210600 has joined #huawei-g300
<juan210600> Hi.
luca020400 has quit [Quit: Leaving]
<juan210600> See you.
juan210600 has quit [Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )]
luca020400 has joined #huawei-g300
<codename13> damn, i got the 3.4 kernel to build finally, but it wont boot :(
<codename13> The only hackish thing I did with the kernel porting was disabling the bluetooth stuff in my defconfig for the time being
<codename13> Anyways I'm gonna renable bluetooth in the defconfig and try to the fix the errors before I upload to Github
gregor160300 has joined #huawei-g300
luca020400 has quit [Remote host closed the connection]
gregor160300 has quit [Quit: Leaving]
<codename13> Has anyone here attempted enabling framebuffer console on boot? Enabling it should allow the kernel log to be displayed on the screen during boot,
<codename13> which would be really useful for debugging my 3.4 kernel
luca020400 has joined #huawei-g300
luca020400 has quit [Ping timeout: 248 seconds]
luca020400 has joined #huawei-g300
<codename13> Wait I think I just realized what's preventing my kernel from booting
<codename13> I built it with a 4.8 toolchain
<codename13> A lot of older kernels need a patch to boot with the 4.8 toolchain
<codename13> I'm gonna try and built it with a 4.7 one then
Solitary has quit [Ping timeout: 265 seconds]
<codename13> no luck booting with gcc 4.7 :( Could the cause of the not-booting be because I don't have ION configured or enabled (PMEM is used)?