Guest danny19901 Posted October 15, 2013 Report Share Posted October 15, 2013 Awesome update no issues so far had 1 reboot but hey no more problems also using cexstel kernel 0.1 and works flawless Link to comment Share on other sites More sharing options...
Guest Simbox97 Posted October 15, 2013 Report Share Posted October 15, 2013 I'm on the last ROM (2013-10-14) and it often reboots :\ The font is more "bold font" than other CM ROMs but it isn't so important. In the end is a good rom but I'd like to have no random reboot Link to comment Share on other sites More sharing options...
Guest fonz93 Posted October 15, 2013 Report Share Posted October 15, 2013 try experimental rom Link to comment Share on other sites More sharing options...
Guest SaurabhRCk Posted October 15, 2013 Report Share Posted October 15, 2013 I'm on the last ROM (2013-10-14) and it often reboots :\ The font is more "bold font" than other CM ROMs but it isn't so important. In the end is a good rom but I'd like to have no random reboot What kind of reboots?? I mean is it occurring when starting any specific app? or just random? Link to comment Share on other sites More sharing options...
Guest Simbox97 Posted October 15, 2013 Report Share Posted October 15, 2013 What kind of reboots?? I mean is it occurring when starting any specific app? or just random? Random reboots... I'll try later to reflash the ROM... Link to comment Share on other sites More sharing options...
Guest danny19901 Posted October 15, 2013 Report Share Posted October 15, 2013 OK I tried test ROM the 1 with cam fixes anyway I have been messing around a lot with tweaks etc... I have cexstel 0.1 cm10.1 kernel and while messing around I have had no reboots but quite some lag so I messed around more and now have zero lag even on heavy usage music doesn't pause or anything while doing stuff also display quality and speed is much better and smoother all tweaks are from pimp my ROM beta app in playstore use at own risk but trust me speed is unbelievable and battery is much better now its worth messing around and giving a try Link to comment Share on other sites More sharing options...
Guest TangerineTractor Posted October 16, 2013 Report Share Posted October 16, 2013 OK I tried test ROM the 1 with cam fixes anyway I have been messing around a lot with tweaks etc... I have cexstel 0.1 cm10.1 kernel and while messing around I have had no reboots but quite some lag so I messed around more and now have zero lag even on heavy usage music doesn't pause or anything while doing stuff also display quality and speed is much better and smoother all tweaks are from pimp my ROM beta app in playstore use at own risk but trust me speed is unbelievable and battery is much better now its worth messing around and giving a try We are all so happy for you. Want to share your tweaks with the rest of us? Link to comment Share on other sites More sharing options...
Guest Simbox97 Posted October 16, 2013 Report Share Posted October 16, 2013 I re-flashed the ROM and there aren't more random reboots Good job Joestone ;) I'm waiting the final release with all problems fixed :) Link to comment Share on other sites More sharing options...
Guest nirmalbalaji Posted October 16, 2013 Report Share Posted October 16, 2013 I re-flashed the ROM and there aren't more random reboots Good job Joestone ;) I'm waiting the final release with all problems fixed :) I think its too soon to push it to the final stage. It was still in beta and there is always some bugs to fix in early stages. This ROM come a long way and I think its pretty much good for a daily usage. Link to comment Share on other sites More sharing options...
Guest xals1997 Posted October 17, 2013 Report Share Posted October 17, 2013 kra1o5 fixed milky screen http://www.modaco.com/topic/364200-cyanogenmod-101-build-r10-171013/ but no the camera (green screen and green lines in video playbak still appearing) Joestone fixed the green screen and the lines in video playback but no the milky screen haha :P i think that they should work together xD Link to comment Share on other sites More sharing options...
Guest SaurabhRCk Posted October 17, 2013 Report Share Posted October 17, 2013 ^ same thought here too! Link to comment Share on other sites More sharing options...
Guest joestone Posted October 17, 2013 Report Share Posted October 17, 2013 I tried Kra1o5' kernel , but it gives memorydealer warnings while loading OMX codecs , with the new display drivers. I have to merge the cnages in my kernel to Kra1o5's kernel to fix the milky screen and the memorydealer warnings in my build. If I can merge the changes will publish a new build as well as the modified sources. Link to comment Share on other sites More sharing options...
Guest ZolaIII Posted October 17, 2013 Report Share Posted October 17, 2013 They are working together! Those are only separate builds! When you find good working solution then it's easy to integrate it (with publicly available code) to every build like with milky screen for Y300 as you call it or RILs under CMs. If you want to help you should test builds for specific futures (fixes) & report back with detailed description & logcats if needed & possible! All do they should again reconsider (more frequently updated) a unified master git with stable implementations to prevent future fragmentation as it whose planned in the first place! Link to comment Share on other sites More sharing options...
Guest ZolaIII Posted October 17, 2013 Report Share Posted October 17, 2013 I tried Kra1o5' kernel , but it gives memorydealer warnings while loading OMX codecs , with the new display drivers. I have to merge the cnages in my kernel to Kra1o5's kernel to fix the milky screen and the memorydealer warnings in my build. If I can merge the changes will publish a new build as well as the modified sources. So the pmem after all plays a important role in our problems or better say ion is a problem!? Link to comment Share on other sites More sharing options...
Guest joestone Posted October 17, 2013 Report Share Posted October 17, 2013 So the pmem after all plays a important role in our problems or better say ion is a problem!?The new display driver is using ion. There are changes which are merged already like extra governors in my builds . But my kernel uses updated kgsl part , display part (msm_fb , mdp). I have no idea where to find the relevant part of the memorydealer warnings. Kra1o5's kernel works with my build (after reverted the dancing cwm fix) and I think these warnings present in Cexstel kernel as well. Link to comment Share on other sites More sharing options...
Guest ZolaIII Posted October 17, 2013 Report Share Posted October 17, 2013 The new display driver is using ion. There are changes which are merged already like extra governors in my builds . But my kernel uses updated kgsl part , display part (msm_fb , mdp). I have no idea where to find the relevant part of the memorydealer warnings. Kra1o5's kernel works with my build (after reverted the dancing cwm fix) and I think these warnings present in Cexstel kernel as well. You are probably right Cextel used Kras repository & original kernel for Y-300 as I know ... Any chance for reverting back to pmem as it is opened? Link to comment Share on other sites More sharing options...
Guest joestone Posted October 19, 2013 Report Share Posted October 19, 2013 New build uploaded , now the milky screen should be fixed. Link to comment Share on other sites More sharing options...
Guest Laximus Posted October 19, 2013 Report Share Posted October 19, 2013 (edited) I tried and it works nice, screen color is ok, and the system is quick. =) One thing, I changed this line :#vold.externalsd.isprimary=trueto this : vold.externalsd.isprimary=true, and after the restart , the Apollo and Es File Exp doesnt see my ext.sd card anymore. Still OpenGL2 laggy. Antutu was under 5000, with swap was around 6200 , and Nenamark2 shows around 25 fps while with stock 33. But the rest seems to me ok. Thank you Köszönjük =) Edited October 19, 2013 by Laximus Link to comment Share on other sites More sharing options...
Guest Sigray Posted October 19, 2013 Report Share Posted October 19, 2013 The camera can't connect. (Y300) Link to comment Share on other sites More sharing options...
Guest danny19901 Posted October 20, 2013 Report Share Posted October 20, 2013 The camera can't connect. (Y300) try focal or camera JB + Link to comment Share on other sites More sharing options...
Guest joestone Posted October 20, 2013 Report Share Posted October 20, 2013 Good news ! I have working videorecording. The build need some fine tuning before I publish it. Link to comment Share on other sites More sharing options...
Guest SH3H1 Posted October 20, 2013 Report Share Posted October 20, 2013 Good news ! I have working videorecording. The build need some fine tuning before I publish it. That's great Link to comment Share on other sites More sharing options...
Guest angellgtz Posted October 20, 2013 Report Share Posted October 20, 2013 Good news ! I have working videorecording. The build need some fine tuning before I publish it. How is going the video hardware acceleration @joestone ? :o Link to comment Share on other sites More sharing options...
Guest SaurabhRCk Posted October 20, 2013 Report Share Posted October 20, 2013 Good news ! I have working videorecording. The build need some fine tuning before I publish it. Owesome! I think its the best week for this device! :) anyway just a request, when uploading the latest version can you please make a know bug list. this way its will easy for us to track the changes. thnx! Link to comment Share on other sites More sharing options...
Guest ZolaIII Posted October 20, 2013 Report Share Posted October 20, 2013 Congratulation! 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