Guest B3rtm3n Posted June 11, 2014 Report Posted June 11, 2014 (edited) Hi Chil just saw your post that you are using 3.4 kernel. Just was curious why you are using old kernel and not 3.8 or 3.10? Btw did dirty upgrade and all is running ok, this really is a huge improvement over the stockfirmware it was running when I bought it. thanks a lot! Edited June 11, 2014 by B3rtm3n
Guest Aqirul Posted June 11, 2014 Report Posted June 11, 2014 this rom is nice.. but the screen caller take sometimes to respond... :3 .. ringging, but no display, not after a few second later :3 hmm.. fix that? thanks for rom anyway..
Guest spanitzer Posted June 11, 2014 Report Posted June 11, 2014 Chil360 is better than Dazzozo! Chil supports the Thread and create a own Kernel. Gold work chil!
Guest SH3H1 Posted June 11, 2014 Report Posted June 11, 2014 (edited) 80% of the work is done by dazzozo ! So don't just misuse any word against him :angry: Edited June 11, 2014 by SH3H1
Guest spanitzer Posted June 11, 2014 Report Posted June 11, 2014 But Dazzozo have old sources and he not support his thread!
Guest Swedoxi Posted June 11, 2014 Report Posted June 11, 2014 For how long are you going to update this rom?
Guest Untot Posted June 11, 2014 Report Posted June 11, 2014 But Dazzozo have old sources and he not support his thread! ALL kitkat sources are ported by Dazzozzo! chil360 and the other kitkat rom devs are using Daz's github as base for their roms
Guest Swedoxi Posted June 11, 2014 Report Posted June 11, 2014 this rom is nice.. but the screen caller take sometimes to respond... :3 .. ringging, but no display, not after a few second later :3 hmm.. fix that? thanks for rom anyway.. Had this problem before. Made a clean install and now it works! try that :)
Guest gregySK Posted June 11, 2014 Report Posted June 11, 2014 this rom is nice.. but the screen caller take sometimes to respond... :3 .. ringging, but no display, not after a few second later :3 hmm.. fix that? thanks for rom anyway.. Edit line in build.prop "ro.telephony.call_ring.delay" from 3000 to 0 ms.
Guest wbrambley Posted June 11, 2014 Report Posted June 11, 2014 I have a slight problem getting VPN connection to work using VPNCilla with the latest SlimKat 5.8 on my Y300. Here the logcat output. Maybe the module is not updated with the new kernel? I/ip6tables( 134): ip6tables v1.4.11.1: can't initialize ip6tables table `nat': Table does not exist (do you need to insmod?) I/ip6tables( 134): Perhaps ip6tables or your kernel needs to be upgraded. I/ip6tables( 134): ip6tables terminated by exit(3) E/Netd ( 134): exec() res=0, status=768 for /system/bin/ip6tables -t nat -D st_nat_POSTROUTING -o tun0 -m mark --mark 61 -j MASQUERADE I will try the Android VPN, maybe that works. Anybody else having problems with 5.8 and VPN? I just logged into several of our hospitals using VPNCilla. I'm using build 5.8 and did a dirty flash from 5.6 no issues here. [emoji4]
Guest Aqirul Posted June 11, 2014 Report Posted June 11, 2014 hmm not working.. already try that, its ringing, but blank screen, screen blank a few second, than can pickup the call.. :3
Guest anotherjib Posted June 11, 2014 Report Posted June 11, 2014 Hi Guys I am going to try slimkat....IN your opinion which is the stablestbuild so far for a daily usage? Thank YOU ;-)For me the last one is the best up to now - not a single reboot
Guest Swedoxi Posted June 11, 2014 Report Posted June 11, 2014 (edited) I can see this device still has the heartbleed bug. Cant you fix that with some update to this rom? Or i will go back to stock rom cuz they said update is out for that. and im going to check if thats true :p Edited June 11, 2014 by Swedoxi
Guest juanpablocastillo Posted June 11, 2014 Report Posted June 11, 2014 The Heartbleed bug is only in 4.1.1 and 4.1.2 because this versions have Heartbeat activated.
Guest Swedoxi Posted June 11, 2014 Report Posted June 11, 2014 The Heartbleed bug is only in 4.1.1 and 4.1.2 because this versions have Heartbeat activated. The version of OpenSSL on your device is affected by the Heartbleed bug (1.0.1e). Sooo im safe you say??
Guest fonz93 Posted June 11, 2014 Report Posted June 11, 2014 (edited) The version of OpenSSL on your device is affected by the Heartbleed bug (1.0.1e). Sooo im safe you say?? Which app do you use to check it? Post a screenshot of that Edited June 11, 2014 by fonz93
Guest Swedoxi Posted June 11, 2014 Report Posted June 11, 2014 (edited) Which app do you use to check it? Post a screenshot of that Lookout: Heartbleed Detector! Edited June 11, 2014 by Swedoxi
Guest juanpablocastillo Posted June 11, 2014 Report Posted June 11, 2014 Heartbeat is disabled (the cause of the vulnerability). Heartbleed depends of that so i'm 95 percent sure.
Guest Swedoxi Posted June 11, 2014 Report Posted June 11, 2014 Well this is from my other phone. So this is what i should say!
Guest juanpablocastillo Posted June 11, 2014 Report Posted June 11, 2014 The picture says the vulnerability is not enabled (Heartbeat). No matter if the version is vulnerable.
Guest juanpablocastillo Posted June 11, 2014 Report Posted June 11, 2014 (edited) What version of Android has your second snapshot? EDIT: Sorry, Google Translate. Edited June 11, 2014 by juanpablocastillo
Guest Swedoxi Posted June 11, 2014 Report Posted June 11, 2014 What version of Android has your second snapshot? EDIT: Sorry, Google Translate. It has android 4.0.4
Guest Swedoxi Posted June 11, 2014 Report Posted June 11, 2014 The picture says the vulnerability is not enabled (Heartbeat). No matter if the version is vulnerable. Well then. Im just very paranoid when it comes to s*** like this xD
Guest juanpablocastillo Posted June 12, 2014 Report Posted June 12, 2014 (edited) Bad redacted post. Please read above. Edited June 12, 2014 by juanpablocastillo
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now