Why don't you collab with @BlueFlame4^ yep
There's no reason to make a thread for something that does not work.
cheers.
It would speed up development.
Why don't you collab with @BlueFlame4^ yep
There's no reason to make a thread for something that does not work.
cheers.
it can be greatWhy don't you collab with @BlueFlame4
It would speed up development.
Are you working on R3S development?? Sounds exciting.it can be great![]()
yep ,Are you working on R3S development?? Sounds exciting.
Do you have a Redmi 3s to work on?yep ,
but stop Offtopic guys![]()
Yes, he haveDo you have a Redmi 3s to work on?
Los is released...Try it onceWell, he definitely deserves credits, you're rightNow the thing is though that I digged through most of the sources and either some use some framework patches or suffer bugs or both. How's your AICP going though?
I don't have time today but will check it out tomorrow. Thanks for the info!Los is released...Try it once
Ya, but kernel source is not, he using 3.18.31 which is latest caf changes on LOS latest update, but he give the wrong link to the kernel source, i just asking to him yesterday he said will give the correct kernel source, but until now is nothingLos is released...Try it once
Finally someone found out :laugh:Ya, but kernel source is not, he using 3.18.31 which is latest caf changes on LOS latest update, but he give the wrong link to the kernel source, i just asking to him yesterday he said will give the correct kernel source, but until now is nothing
I feared for something like that. I won't donate until the real sources are released, if so, i will be happy to do so!Ya, but kernel source is not, he using 3.18.31 which is latest caf changes on LOS latest update, but he give the wrong link to the kernel source, i just asking to him yesterday he said will give the correct kernel source, but until now is nothing
Well, be open is important so everyone with programing ability can work together make the kernel clean and bugless, bugless sounds like impossible but it can be possible if we work togetherI feared for something like that. I won't donate until the real sources are released, if so, i will be happy to do so!
* This post does not concern those that do not face reboots when connecting to 4G *Quick update to keep everyone entertained and informed: Tha LTE band bug looks rather nasty to me. Also another log states that
This totally sounds like a blob issue on the first glance. Oddly enough this doesn't happen on stock kernel so I am afraid Xiaomi built some weird workaround into the kernel, ugh. I hope I can get this fixed.Code:modem subsystem failure reason: rflte_mc_meas.c:861:Invalid LTE NV for device 0 band 3 for IRAT.
I rebasing the kernel with latest I Will try in asapYa, but kernel source is not, he using 3.18.31 which is latest caf changes on LOS latest update, but he give the wrong link to the kernel source, i just asking to him yesterday he said will give the correct kernel source, but until now is nothing
Sir. You rebasing the kernel taken from xiaomi opensource or using from another source sir?I rebasing the kernel with latest I Will try in asap
Caf with redmi patchSir. You rebasing the kernel taken from xiaomi opensource or using from another source sir?
something like this?* This post does not concern those that do not face reboots when connecting to 4G *
Well apparently, the revert on Xiaomi's changes to drivers/soc/qcom/subsystem_restart.c, that so called fixed the compilation error, caused the panic.
Instead, with 'WT_SUBSYSTEM_REASTART_LEVEL' defined not removed, no more freezing and reboots when connecting to network![]()
But still, it cannot connect to 4G. Now it just keeps trying to connect, fails, tries again, fails again.. at least there's a chance to choose 3G connection now!
Nice nice