Guest Posted June 11, 2014 Report Share Posted June 11, 2014 I reverted all updates related to Android's LowMemoryKiller and Linux's OutOfMemory Management for now... Link to comment Share on other sites More sharing options...
Guest AssaSsiNMiLeS Posted June 11, 2014 Report Share Posted June 11, 2014 Now with the 4.8.3 version everything is perfectly fine though I also changed my app configuration a little. But the freezing problems today started after like 7 hours away from the charger so I can't tell yet if these problems will occur with 4.8.3 version. Link to comment Share on other sites More sharing options...
Guest juanpablocastillo Posted June 12, 2014 Report Share Posted June 12, 2014 That's hard to answer. A so called "stable version" requires being tested for a while without any mentionable errors/bugs. Since I'm continuously changing code it can have negative effects on things I weren't able to trigger during testing. That's why I use to mark builds as "nightly", before declaring them as stable. Due of my recent attempt to improve frequency scaling and hot-plugging I discovered a lot of issues which needs to get fixed step by step. Back at Gingerbread times the 1st linux kernels for android differed a lot from the linux mainline. Although they always merged patches which were commit into mainline, it seems that some mandatory patches are missing in the early 3.4.y CodeAurora kernel sources (those huawei used for our device). Unless finding and adding those patches I'm unable to continue on things I'd prefer to do. There are some important ARMv7 changes missing which I'd like to be included in this kernel. If I may give you some hint: if possible try to buy a device which is running on a more recent Linux kernel than 3.4.y I don't understand. So, you can't merge the CAF 3.4 kernel or don't can merge or you can not do as you wanted? Sorry if annoying. Link to comment Share on other sites More sharing options...
Guest Posted June 12, 2014 Report Share Posted June 12, 2014 (edited) Sry if it seems like I'd ignore your question. It's just late/early in the morning. I'll answer it later. Just wanted to provide the current state of work: - wifi broken - It's compiled with GCC 4.9.1. A kind of "changelog" is here: https://github.com/moddingg33k/android_kernel_experimental/commits/master I'd appreciate to get some feedback. Those locking issues should be gone. I removed all LowMemoryKiller related commits for now. Edited June 12, 2014 by Guest Link to comment Share on other sites More sharing options...
Guest Romagnolo1973 Posted June 12, 2014 Report Share Posted June 12, 2014 (edited) I have tryed last experimental but when I activate Wifi I have get a restart and it still have bootloop, I think because wifi module is active, revert to last 31\05 kernel everything ok and I can boot with my wifi icon active moddingg 2 questions: - have you seen HTC 300 kernel I have post in the other thread (your kernel for CM made by fonz93) if can be helpfull? - why 2 backup when flashing your kernel, one in Synopsys backup and other in TWRP? Thanks Edited June 12, 2014 by Romagnolo1973 Link to comment Share on other sites More sharing options...
Guest Domino2115 Posted June 12, 2014 Report Share Posted June 12, 2014 I've installed lastest experimental but phone dont even boot it says'optimalizing apps" and when its done phone reboot Link to comment Share on other sites More sharing options...
Guest thetonyxx Posted June 12, 2014 Report Share Posted June 12, 2014 but phone dont even boot it says'optimalizing apps" wipe dalvik and chace? Link to comment Share on other sites More sharing options...
Guest Posted June 12, 2014 Report Share Posted June 12, 2014 Oh damn! That f***** pre-built WiFi module again :( One of the latest commits broke it again -.- Link to comment Share on other sites More sharing options...
Guest fonz93 Posted June 12, 2014 Report Share Posted June 12, 2014 Oh damn! That f***** pre-built WiFi module again :( One of the latest commits broke it again -.- Dazzozo what wi-fi module is using? I am not sure but i saw on his github a source to compile a wi-fi module, am i wrong? Link to comment Share on other sites More sharing options...
Guest Domino2115 Posted June 12, 2014 Report Share Posted June 12, 2014 wipe dalvik and chace? I did. Link to comment Share on other sites More sharing options...
Guest Posted June 12, 2014 Report Share Posted June 12, 2014 (edited) Yea, he got some source code on his repo which I forked, too. But he doesn't use it. Instead he's using the prebuild modules of some other kernel, which are Huawei's prebuild ones. The problem with those sources is: hotspot doesn't work on them. That's because 2 functions are missing the HostAP binary is trying to call. Well. That's a pit. The last kernel build was promising to save some energy due of optimized frequency scaling behavior Edited June 12, 2014 by Guest Link to comment Share on other sites More sharing options...
Guest fonz93 Posted June 12, 2014 Report Share Posted June 12, 2014 Another question, while porting your kernel i had to modify cm ramdisk and add your wi fi modules to make it work, where did you take them, why are different? Link to comment Share on other sites More sharing options...
Guest Posted June 12, 2014 Report Share Posted June 12, 2014 You had to use "my wifi modules"? They are taken from the stock B199 kernel. Modules from other kernels should work as well in theory. Link to comment Share on other sites More sharing options...
Guest fonz93 Posted June 12, 2014 Report Share Posted June 12, 2014 I couldn't use cm's wi fi modules because the phone reboots when i use wi fi, so i took your wi fi modules from your ram disk and added them on cm ramdisk to make wi fi work Link to comment Share on other sites More sharing options...
Guest Posted June 12, 2014 Report Share Posted June 12, 2014 That's kinda interesting :D because I didn't compile those modules neither modify them (with an hexeditor for ex.) Link to comment Share on other sites More sharing options...
Guest fonz93 Posted June 12, 2014 Report Share Posted June 12, 2014 That's kinda interesting :D because I didn't compile those modules neither modify them (with an hexeditor for ex.) That's why i asked you if they are using differents modules, because i can't use them in your kernel Link to comment Share on other sites More sharing options...
Guest Posted June 12, 2014 Report Share Posted June 12, 2014 (edited) I found the patch-set which caused those reboot issues (with enabled): [KERNEL LOCKS] *big update* ... removed it and uploaded fixed builds: GCC 4.6: http://www58.zippyshare.com/v/49859364/file.html GCC 4.8: http://www3.zippyshare.com/v/33709362/file.html GCC 4.9: http://www42.zippyshare.com/v/41874288/file.html Edited June 12, 2014 by Guest Link to comment Share on other sites More sharing options...
Guest fonz93 Posted June 12, 2014 Report Share Posted June 12, 2014 (edited) I found the patch-set which caused those reboot issues (with enabled): [KERNEL LOCKS] *big update* ... removed it and uploaded fixed builds Do you mean reboots due to the differents wi-fi modules? Edit: Sorry, didn't see changelog Now i can port your kernel to cm11 etc using their modules? Edited June 12, 2014 by fonz93 Link to comment Share on other sites More sharing options...
Guest Posted June 12, 2014 Report Share Posted June 12, 2014 Hmmm?? Those reboots are caused by those mentioned updates, because the pre-build huawei modules don't work with them. Link to comment Share on other sites More sharing options...
Guest fonz93 Posted June 12, 2014 Report Share Posted June 12, 2014 (edited) Hmmm?? Those reboots are caused by those mentioned updates, because the pre-build huawei modules don't work with them. And which modules is dazzozo using?? Edit: Maybe i didn't understand, if dazzozo is using pre-build huawei modules, why didn't they work as yours? (btw, they are different in size), if this update broke wi-fi on cyanogenmod, why on stock ROM those updates doesn't give reboots? Edited June 12, 2014 by fonz93 Link to comment Share on other sites More sharing options...
Guest Posted June 12, 2014 Report Share Posted June 12, 2014 Ask him :P Link to comment Share on other sites More sharing options...
Guest fonz93 Posted June 12, 2014 Report Share Posted June 12, 2014 (edited) Are you sure that on KK ROM's they don't use Dazzozo's wifi sources? look at the SlimKat manifest by chil360 https://github.com/chil360/slimkat_manifest/blob/master/slimkat_huawei.xml Edited June 12, 2014 by fonz93 Link to comment Share on other sites More sharing options...
Guest Posted June 12, 2014 Report Share Posted June 12, 2014 - have you seen HTC 300 kernel I have post in the other thread (your kernel for CM made by fonz93) if can be helpfull?- why 2 backup when flashing your kernel, one in Synopsys backup and other in TWRP?I didn't see any link to the kernel's source code. Did I miss it somehow?The installer creates an backup within the TWRP folder, so people can easier find the backup. Since not everyone is using TWRP, but other recovery solutions, another copy of the backed up kernel is store in the "synopsis-backup" folder on the sdcard. Seems like an overkill, I know. But I guess it's easier safer to delete the duplicate backup than not having it at all. Link to comment Share on other sites More sharing options...
Guest luca020400 Posted June 12, 2014 Report Share Posted June 12, 2014 Kernel 3.4.93 is out https://www.kernel.org Link to comment Share on other sites More sharing options...
Guest Posted June 12, 2014 Report Share Posted June 12, 2014 Are you sure that on KK ROM's they don't use Dazzozo's wifi sources? look at the SlimKat manifest by chil360 https://github.com/chil360/slimkat_manifest/blob/master/slimkat_huawei.xml Hm...not sure which of those listed sources he's using at the end, but you are right. Those modules are not the one's from huawei. They will work on SlimKat (did anyone test WiFi tethering on chil's rom?), but definatly don't work on Huawei Stock ROM because of 2 missing functions required by the system's binaries to create an Access-Point. It's either "hostap" or "wpa_supplicant" (or even both) which needed to get replaced in favor of other WiFi modules. Another solution would be trying to integrate those 2 missing functions on my own *lol* Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now