Edited by x6itru, 30 January 2013 - 07:11 PM.
[DEV][ROM][14.5.] CyanogenMod 10 (Android 4.1.2)
#41
Posted 30 January 2013 - 07:08 PM
#42
Posted 30 January 2013 - 08:02 PM
dorren, on 30 January 2013 - 04:46 PM, said:
And sometimes my ear turns on the airplane mode and the call ends, but i guess that is the proximity sensor that needs calibration. I will look in the menyes for that
I had another case of not beeing able to answer now, but when pressing the powerbutton two times and then answering it works.
/Erik
x6itru, on 30 January 2013 - 07:08 PM, said:
Yeah, I've had problems with proximity too. Still not sure if everyone have this issue though. It's stange since all other sensors work and I think it worked out-of-the-box in my CM9 builds.
You can calibrate proximity under Settings -> Advanced -> Calibrate proximity sensor and it will work until the next reboot. We're using a prebuilt sensors lib from the stock ROM and it doesn't know how to read that calibration data. I've been trying to build sensors lib from source and proximity/light sensors works great but acceleration/magnetic/orientation doesn't. :/
I boot my phone so often that I made a simple script that calibrates proximity sensor automatically on every reboot. Save this as 09proximity to /system/etc/init.d (or /data/local/userinit.d if you want it to survive ROM updates) and make it executable (775 permissions).
#!/system/bin/sh # Calibrate ZTE atlas40 proximity sensor at boot /system/bin/prox_cal -c
ZTE Blade:
CyanogenMod 10.1 - KonstaKANG (Android 4.2.2) - ClockWorkMod 6.0.2.7
CyanogenMod 10 - KonstaKANG (Android 4.1.2)
CyanogenMod 9 - KonstaKANG (Android 4.0.4)
Swedish Snow RLS7 (Android 2.3.5)
ZTE Blade III:
CyanogenMod 10.1 - KonstaKANG (Android 4.2.2) - ClockWorkMod 6.0.3.2
CyanogenMod 10 - KonstaKANG (Android 4.1.2)
Aurora Borealis RLS1 (Android 4.0.4)
Firefox OS - Ubuntu Touch
#43
Posted 31 January 2013 - 08:35 AM
I can also confirm "Sometimes the status bar freezes, and i cant go to my notifications" and phone ringing only 1 time when someone calling me.
#44
Posted 31 January 2013 - 09:36 AM
How does it compare to the Blade "1" running your same release (i.e. your latest CM10) ?
I've read nice reviews of the Blade 3, but most of them talk about lags and slowdowns in the interface. I'm pretty sure that using a custom ROM totally solves these issues though (can you confirm ?), but I wonder how CM10 impacts the good battery life that all the reviewers agree on.
#45
Posted 31 January 2013 - 10:41 AM
klipi, on 31 January 2013 - 08:35 AM, said:
I can also confirm "Sometimes the status bar freezes, and i cant go to my notifications" and phone ringing only 1 time when someone calling me.
Changing composition type to gpu probably fixes the notification freeze (see this post). You can enable repeating ringtone by adding these lines to your /system/build.prop. Or just use a longer ringtone.
ro.telephony.call_ring.multiple=false ro.telephony.call_ring.delay=3000
thewild, on 31 January 2013 - 09:36 AM, said:
How does it compare to the Blade "1" running your same release (i.e. your latest CM10) ?
I've read nice reviews of the Blade 3, but most of them talk about lags and slowdowns in the interface. I'm pretty sure that using a custom ROM totally solves these issues though (can you confirm ?), but I wonder how CM10 impacts the good battery life that all the reviewers agree on.
Lol, I have no idea. I don't have much experience on regular use with this device. I think my battery has never gone below 75% with CyanogenMod. It spends too much time connected to USB when I'm debugging it.
I spent few days with the stock based ROM and I was impressed with the battery performance. Even the custom kernel didn't seem to trash it. I'd say battery life in my use was at least twice as good as with my old Blade (which has a two years old battery).
I haven't experienced any UI slowdowns with the ROMs I've used. It still has the normal 'Android lag' in few places (multi-tasking view, notification area in jellybean) and few skipped frames every now and then, but that's just something that you should expect from a cheap low performing hardware. In general msm7x27a performance should pretty much match the performance of high-end devices from over two years ago (Nexus S, Galaxy S).
ZTE Blade:
CyanogenMod 10.1 - KonstaKANG (Android 4.2.2) - ClockWorkMod 6.0.2.7
CyanogenMod 10 - KonstaKANG (Android 4.1.2)
CyanogenMod 9 - KonstaKANG (Android 4.0.4)
Swedish Snow RLS7 (Android 2.3.5)
ZTE Blade III:
CyanogenMod 10.1 - KonstaKANG (Android 4.2.2) - ClockWorkMod 6.0.3.2
CyanogenMod 10 - KonstaKANG (Android 4.1.2)
Aurora Borealis RLS1 (Android 4.0.4)
Firefox OS - Ubuntu Touch
#46
Posted 31 January 2013 - 10:53 AM
KonstaT, on 31 January 2013 - 10:41 AM, said:
I spent few days with the stock based ROM and I was impressed with the battery performance. Even the custom kernel didn't seem to trash it. I'd say battery life in my use was at least twice as good as with my old Blade (which has a two years old battery).
I haven't experienced any UI slowdowns with the ROMs I've used. It still has the normal 'Android lag' in few places (multi-tasking view, notification area in jellybean) and few skipped frames every now and then but that's just something that you should expect from a cheap low performing hardware. In general msm7x27a performance should pretty much match the performance of high-end devices from over two years ago (Nexus S, Galaxy S).
OK thanks for sharing your views on the device.
I think there are better (hardware-wise) devices in this same price range, but most of them are not widely distributed and will never have CM support (because the manufacturers won't release source codes).
Once you've tasted custom ROMs (and JB), it's hard the be stuck on original ROMs (most of which will never be upgraded to JB).
BTW, is project butter fully working on this device ? Does it make a noticeable difference ? (I believe it is since you don't mention it in the "not working" list)
#47
Posted 31 January 2013 - 01:43 PM
it is possible to install it?
Edited by merc1800k, 31 January 2013 - 01:44 PM.
#48
Posted 31 January 2013 - 02:08 PM
What's good working wifi-hotspot application? I tried severals, but nothing worked.
Edited by Qstom, 31 January 2013 - 02:20 PM.
#49
Posted 31 January 2013 - 02:24 PM
Qstom, on 31 January 2013 - 02:08 PM, said:
What's good working wifi tethering application? I tried severals, but nothing worked.
adb pull /system/build.propand push after edit
adb push /system/build.prop
Edited by x6itru, 31 January 2013 - 02:24 PM.
#50
Posted 31 January 2013 - 02:37 PM
thewild, on 31 January 2013 - 10:53 AM, said:
merc1800k, on 31 January 2013 - 01:43 PM, said:
it is possible to install it?
In CockWorkMod thread:
KonstaT, on 20 January 2013 - 11:05 AM, said:
Qstom, on 31 January 2013 - 02:08 PM, said:
What's good working wifi-hotspot application? I tried severals, but nothing worked.
Wifi tether for root users works for me.
ZTE Blade:
CyanogenMod 10.1 - KonstaKANG (Android 4.2.2) - ClockWorkMod 6.0.2.7
CyanogenMod 10 - KonstaKANG (Android 4.1.2)
CyanogenMod 9 - KonstaKANG (Android 4.0.4)
Swedish Snow RLS7 (Android 2.3.5)
ZTE Blade III:
CyanogenMod 10.1 - KonstaKANG (Android 4.2.2) - ClockWorkMod 6.0.3.2
CyanogenMod 10 - KonstaKANG (Android 4.1.2)
Aurora Borealis RLS1 (Android 4.0.4)
Firefox OS - Ubuntu Touch
#51
Posted 31 January 2013 - 03:13 PM
thewild, on 31 January 2013 - 09:36 AM, said:
How does it compare to the Blade "1" running your same release (i.e. your latest CM10) ?
I've read nice reviews of the Blade 3, but most of them talk about lags and slowdowns in the interface. I'm pretty sure that using a custom ROM totally solves these issues though (can you confirm ?), but I wonder how CM10 impacts the good battery life that all the reviewers agree on.
I get minimum 24h of use with wifi on and connected all the time, tho just for mails and twitter here and there.
#52
Posted 31 January 2013 - 03:56 PM
KonstaT, on 31 January 2013 - 02:37 PM, said:
Sounds a lot like CyanogenMod related issue...
In CockWorkMod thread:
Root Explorer is great but it costs few euros. ES file explorer is free.
Wifi tether for root users works for me.
KonstaT, on 31 January 2013 - 02:37 PM, said:
Sounds a lot like CyanogenMod related issue...
In CockWorkMod thread:
Root Explorer is great but it costs few euros. ES file explorer is free.
Wifi tether for root users works for me.
where i can found stock rom for blade 3???
#53
Posted 31 January 2013 - 04:57 PM
merc1800k, on 31 January 2013 - 03:56 PM, said:
http://www.modaco.co...3/#entry2062909
#54
Posted 31 January 2013 - 05:17 PM
#55
Posted 31 January 2013 - 05:39 PM
#56
Posted 31 January 2013 - 05:58 PM
Edited by x6itru, 31 January 2013 - 06:01 PM.
#57
Posted 31 January 2013 - 05:59 PM
merc1800k, on 31 January 2013 - 05:39 PM, said:
i dont know another way to install original rom
Here is a custom rom based on original maybe that one has the upgrade that is originally included in stock rom?
http://www.swedroid....ead.php?t=89517
I have not tested so I do not know.
And after that use one of the roms here:
http://wwwen.zte.com.../mobile/Sweden/
Instructions on how to upgrade is in the .zip you download.
Well that is the best I can do.
On TopIc: When using the headset with your rom KonstaT, the mic is muted by "itself".
#58
Posted 31 January 2013 - 06:17 PM
merc1800k, on 31 January 2013 - 05:39 PM, said:
i dont know another way to install original rom
Here you will find all stock recovery. Install appropriate zip from CWM!
http://zteblade3.blo...ry-6012_17.html
(After installation, choose advanced - reboot recovery in CWM)
Edited by apeelme, 31 January 2013 - 06:24 PM.
#59
Posted 31 January 2013 - 07:01 PM
apeelme, on 31 January 2013 - 06:17 PM, said:
http://zteblade3.blo...ry-6012_17.html
(After installation, choose advanced - reboot recovery in CWM)
thanks a lot !
i will try later
#60
Posted 31 January 2013 - 08:26 PM
4 user(s) are reading this topic
1 members, 3 guests, 0 anonymous users
-
szymekdo







Sign In
Create Account


Back to top










