• Content count

  • Joined

  • Last visited

Community Reputation

25 Excellent

About xeros2

  • Rank

Previous Fields

  • Your Current Device(s) Coolpad F1 8297W

Recent Profile Visitors

717 profile views
  1. Nice, thanks! Looking at the screenshots it looks similar to AOSP. What about xposed modules? Did you test any for compatibility? For comparision, on CoolUI around half of xposed modules are not fully compatibile. How would you compare camera quality & speed (& functionality) to other ROMs? (I'm curious about comparision with CoolUI with stock camera). And what do you mean "almost 100% functional"? Does it have any issues?   Too bad that we're loosing dakok, jakethedogg,... and few other members (who bought new phone) that brought much to F1 community. At the other side - great choice! In F1 now I really miss gyroscope & magnetometer/compass that are essential for VR, but I'm still not going to replace my F1 in next 1-2 years yet.
  2. If this happened after flashing single ROM and you didn't have issues before then it might not be flash issue but rather incompatible ROM which might have changed partitioning.   Still, it should be possible to fix it.   I think the easiest way would be flashing complete stock firmware (including use of scatter file) first to fix the issue and later flash your chosen correct ROM.
  3. So try first with: 1. Installing ADB client on PC & ADB drivers (you can find many instructions for that), then:  
  4. Can't tell for sure without seeing any detailed log, but I could guess that there could be some bad block in built-in flash in 'cache' partition area. I suggest to: - connect to phone via ADB when you're in recovery or use terminal (still in recovery if it's touch recovery, like TWRP), - use Linux low level tools to create fs and mark bad blocks (ensuring that it's normal EXT4 filesystem, not some modified one and that you have the tools in your recovery) - "badblocks" & "mkfs.ext4" ("mke2fs") - try to search for some docs on that.   I have done such things few years ago with old Android 4.0.3 AllWinner A10 tablet - despite many bad blocks (which I have marked as bad and ommited to not use for data), including /system & /data areas, it's still working up to now. At that time this tablet got bricked because my daughter connected completely drained tablet to USB charger which didn't have enough power to keep tablet awake and it was constantly starting & resetting all the time for whole day (& maybe night, too), which resulted in built-in flash corruption.
  5. Sure, I use fast Kingston 64GB Class 10 U3 MicroSDXC (90MB/s Read / 85MB/s Write) without any issues since around beginning of this year. One thing is that I had to format it as FAT32 as kernel in F1 doesn't have exFAT support compiled in.
  6. Battery Drain suggestions

    Well, generally MT6592 is power hungry SoC, but... If you're interested mostly in YouTube then I would suggest to limit screen light and maybe use Tasker app (or sth similar) to disable 6 CPU cores & limit CPU+GPU frequency+voltage (to minimum required for fluent YouTube playback) when YouTube is started and return previous state when YouTube is stopped or other apps get started. In my case I have noticed quite big battery drains even when phone was in sleep state (but with 3G or WIFI enabled) so I've set it using Tasker to do such tricks for display off/on events and hibernate most apps in sleep state and it has improved battery drains in sleep mode quite much. I still have huge battery drains in high end gaming (around 3-3.5h SOT only in heavy games that take advantage of all 8 CPU & 4 GPU cores) so I should profile that better also, but at least phone waiting for IM messages, SMS, phone/video calls, e-mails... does not drain that much.   Edit: I see also that you have much Cell standby and WLAN power usage - I could suggest to switch cellular connectivity to GSM (if you don't need 3G) - it should improve range & battery usage (it can be also profiled with Tasker to switch to 3G when you enable data connection) and increase WLAN scan intervals in build.prop.
  7. I think it's the same rumour like with L for F1. MMX gets ROMs from Coolpad so I doubt that it will get official L, too. Sadly speaking, I think that development for F1/MMX has stopped. But I wish I was wrong.
  8. Did anyone got such issue that bluetooth "just stopped working"? When I try to enable it it's getting disabled in few secs. What I've found it's getting enabled in configuration (1 value for "bluetooth_on" in /data/data/com.android.providers.settings/databases/settings.db "system" table) but in menu it's still disabled and doesn't search for devices and it's not reachable. Other things that I've found (compared to backup with BT working) is that MAC address in "secure" table has been reset to 00:00:00:00:00:00 but even after changing it back to proper one it's still not working with the same result. In dmesg I found suspicious text: <5>[ 571.378340] (0)[1:init]init: starting 'bt_mac' <6>[ 571.378787] (0)[1:init]init: PropSet [init.svc.bt_mac:running] Start>> <6>[ 571.378933] (0)[1:init]init: PropSet [init.svc.bt_mac:running] Done <7>[ 571.402719] (0)[9002:write_bt_mac][exec] /system/bin/write_bt_mac(3) <7>[ 571.448608] (1)[9002:write_bt_mac][9002:9002:write_bt_mac] exit <7>[ 571.448893] (1)[9002:write_bt_mac][9002:write_bt_mac] sig 17 to [9000:sh]but googling didn't show anything for such exit signal from this process. Setting "bluetooth_on" to "0" in "system" table and reboot makes logs outputs a bit better for first attempt to enable BT (at first sight they look like it should work), but it still gets disabled afterwards. I have checked /data/nvram files for BT and /data/@btmtk and there it looks similar to backup and nothing useful in /proc & /sys to check from kernel side. I was thinking about some hardware problems as I've been using BT for connection to car engine computer few times for 7-8h/day of car driving and it seams it might have stopped working when I tried it once more or it could have been some unplanned phone reboot due to hang of launcher/app. Other than that, everything else works fine (just this BT isn't working).   Just for info - I didn't try to clean data & ROM reflash - I've got used to repair broken things instead going easy way & start configuration/reinstallation from scratch (I have almost 300 apps & many of them are tightly integrated with system and specially configured that backup restore wouldn't be so easy in my case).   Did anyone have such problem also and what was resolution for it?
  9. Well, I (& all of us here, I think), was really counting on this 5.1 update because I'm looking for its features & fixes (including better compromise between performance & power consumption), because as I still use 4.2, I don't have any objections for performance, but battery life is very weak (even after removing, killing, freezing, hibernating most of apps), especially on when using more heavy tasks just for a couple of minutes each day. I really miss other kernel features that are not available in released JB & KK kernels so far, like I/O accounting, USB 3.0 charging support, USB Host (even non-powered), ExFAT & other FS support, better CPU & IO schedulers and CPU frequency scaling fixes (like CPU goes to static ~1142MHz in sleep state, regardless of cpufreq kernel settings for any scheduler to set min/max/cur frequencies, but from power consumption it looks like ~750-850MHz frequencies with 6 cores disabled (using only 2 cores) seem to be most power effective for sleep states for MT6592). Other things are mentioned GPU drivers - other phones with MT6592 & KK have better GPU kernel drivers for our MALI 450 (for example Lenovo A8/A806,...), which are better in both performance & power consumption. There are even more things waiting for fixes on Coolpad side, but these are the first things that come to my mind for kernel side.
  10. Cases/covers

    You're right, I shouldn't try to glue this metal ring - this part is ugly now. But... anyway, it still looks better than previous ugly silicone case (especially after that it changed it's color).
  11. Cases/covers

    Sorry, but I can't take a picture of phone with cover. I don't have any other device with camera with me (besides laptop with very poor 0,3M camera) to make a photo. All I could do is just cover photo without a phone, using F1 after removing it from cover: http://postimg.org/gallery/lg65x98o/ That metal ring for camera is not from this cover - it's the one that I have glued for use with external lens (and I sill have glue around it, which I'll have to clean). Originally camera hole looked exactly like on photos from case offer.
  12. Cases/covers

    Well, I was concerned about thickness, too, but it's not that thick as I thought. Anyway, for sure it's thicker than your previous cover (which replaced phone's back), but it's not bad and comparing it with my previous silicone cover or phone without a cover, this one I like the most & it seems that it gives at least some sort of phone protection (can't confirm that yet, unless I'll drop the phone).
  13. Cases/covers

    Finally received it (gold one). It's really awesome (exactly like on photos here): http://www.aliexpress.com/item/Metal-Aluminum-Transparent-Clear-Acrylic-Hard-Back-Case-For-Coolpad-Dashen-F1-8297-Luxury-Cover-for/32407787508.html (I have bought it even cheaper from other seller, which had old case in his offer, but I asked does he have this new a'la iPhone 6 and he sent me the one above).   It is really aluminium, back cover is comparable to "tempered glass" (maybe it's not real glass, but at least looks like good quality acrylic), which I bought sometime ago for screen protection. Buttons work even better than without the cover (and much better usable than in silicone cover), phone fits perfectly, not moving inside, metal frame is a bit higher than screen so looks like screen corners are somewhat protected from accident falling down, but phone is not that much thicker than without this cover (seems to be less thicker than with silicone case). Feeling of holding the phone in this case is very good, too (despite the back is slippery, but frame doesn't and phone doesn't seem to slip of the hand). I wear phone in jeans pocket (walking, running, pulling it in & out very often) and having such cover since about a week so far no scratches, but today I have sticked to it metal ring for magnetic additional lens (I have exchangeable telephoto 2x optical zoom, fisheye, wide & macro lens - these are quite nice equipment, too) using super glue (it didn't want to stick using it's own glue) and unfortunately some glue has slopped around so now I'm looking for a way to clean it to make it beauty again (washing liquid, soap, toothpaste, WD-40, hot water... didn't help so far but at least didn't corrupt the back cover, even that I tried to wipe it very hard in many ways).   Anyway, it seems to be best cover that I had so far for any phone. Just one thing - transparent window for Coolpad logo is like on photo (up) so doesn't match logo on our phones (down side), but it doesn't affect anything and you can put inside there anything you want.
  14. Thx for reply. Yeah, that's a pitty. Well, there are very few apps that can use accelerometers as alternative for gyroscope. But anyway, I think that cardboard could be at least good for 3D movies watching (versions with less zooming lens).
  15. Would anyone check any of apps that I posted here and answer with info that it works or not and on which ROM version it was tested? Thank you in advance.

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.