• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

[DEV][ROM][17.9.] CyanogenMod 10.1 (Android 4.2.2)

972 posts in this topic

Posted

Err, CyanogenMod is a custom ROM based on AOSP source code and it's built for wide range on devices. This is a device (or a family of devices) specific issue, not a CyanogenMod issue. RC5 or whatever is just a 'tag' they give to their official builds (this is unofficial) when they've reached some internal goals. It's still built from the same source tree it was built yesterday or will be tomorrow. There's a link to merged changes in the second post.

Problem with bluetooth is that Google introduced a completely new bluedroid bluetooth stack in Android 4.2 (vs. bluez stack used in 4.1 and prior). There are no devices with similar bluetooth hardware (WCN2243) with Android 4.2 and Qualcomm doesn't provide valid sample code for this bluetooth chip because they don't officially support our msm7x27a platform on Android 4.2 either.

So, will there be any solution ever for that? Something custom code?

0

Share this post


Link to post
Share on other sites

Posted

The same for me.

Actually I found that the blue screen during typing is from the keyboard(I tried other keyboards and the blue screens/reboots from typing were much less).

But yes there's just too many random reboots so I flashed back Aurora :)

I know this problem. Sometimes my phone reboots with the same blue screen, but I found a solution for that. If you set the processor governor to performance, it will never reboot. It worked for me.

0

Share this post


Link to post
Share on other sites

Posted

Help,

rooted my Blade III and flashed to cyanogenMod and i am experiencing several random reboots,it reboots during use,when typing messages (i changed sms application several times but didnt help) it show blue screen and then reboot.

i have clockworkmod 6.0.3.2 and used cyanogenMod 10 and CyanogenMod 10.1 but same thing.

Did flashing firmware,or kernel would solve this bug?

The same for me.

Actually I found that the blue screen during typing is from the keyboard(I tried other keyboards and the blue screens/reboots from typing were much less).

But yes there's just too many random reboots so I flashed back Aurora :)

I think random reboots have nothing to do with overclocking, it keeps on rebooting on normal frequency as well. Mainly when I'm watching something in MXplayer with software decoding.

First make sure that you've done a clean install of the ROM (including formatting /system partition) and that you're not overclocking your CPU.

I can't reproduce any random reboots so it's up to you to post logs (logcat, dmesg) of this issue. Why haven't I seen any?

So, will there be any solution ever for that? Something custom code?

Sure it can be fixed if someone is willing to invest time and energy in debugging and fixing it. I've already wasted more than one weekend in trying to make it work and I haven't succeeded. Now it's someone else's turn to have a crack at it (TeamHackLG?).

The new bluedroid stack works on Blade on even older Qualcomm chip (BTS4025) than what we have on our device. That needed a specific vendor lib to be written for it. Another solution that would definitely work would be to forward port the old bluez stack to 4.2. Imo that isn't the best possible solution and it isn't future proof either. I'd rather have it done in a way that has a chance of working in the next Android version as well.

0

Share this post


Link to post
Share on other sites

Posted

First make sure that you've done a clean install of the ROM (including formatting /system partition) and that you're not overclocking your CPU.

I can't reproduce any random reboots so it's up to you to post logs (logcat, dmesg) of this issue. Why haven't I seen any?

Sure it can be fixed if someone is willing to invest time and energy in debugging and fixing it. I've already wasted more than one weekend in trying to make it work and I haven't succeeded. Now it's someone else's turn to have a crack at it (TeamHackLG?).

The new bluedroid stack works on Blade on even older Qualcomm chip (BTS4025) than what we have on our device. That needed a specific vendor lib to be written for it. Another solution that would definitely work would be to forward port the old bluez stack to 4.2. Imo that isn't the best possible solution and it isn't future proof either. I'd rather have it done in a way that has a chance of working in the next Android version as well.

So, there isn't too much chance to be fixed.. :/

0

Share this post


Link to post
Share on other sites

Posted

About Bluetooth... CAF has implemented Bluez stack into 4.2, not sure if you already knew that but perhaps you can try that. Guys at androidarmv6 have adapted it to CM10.1 sources.

0

Share this post


Link to post
Share on other sites

Posted

About Bluetooth... CAF has implemented Bluez stack into 4.2, not sure if you already knew that but perhaps you can try that. Guys at androidarmv6 have adapted it to CM10.1 sources.

Yeah, I know and I also noticed you started using it on Mini 2. I have no doubt it would work but I'd much rather have it working with bluedroid. You can't keep porting bluez to this and every subsequent Android version.

0

Share this post


Link to post
Share on other sites

Posted

My battery discharges so fast on Android 4.2. I checked the battery options and the screen used 45 percentages. The screen's brightness is already put lower, but still uses a lot of energy. It discharges 4-6 percentages if I use it for about 10minutes. Any idea how I can solve it?

0

Share this post


Link to post
Share on other sites

Posted (edited)

Yeah, I know and I also noticed you started using it on Mini 2. I have no doubt it would work but I'd much rather have it working with bluedroid. You can't keep porting bluez to this and every subsequent Android version.

Well, what other options are there? I.e., what's the likelihood of Qualcomm releasing the specs (hah) or sample code for the MSM7227 chipset's Bluetooth functionality?

To get an Android 4.2.x on the ZTE Blade III, there are three options:

a ) Wait forever until drivers are released (unlikely)

b ) Use it without Bluetooth (sure, cool if you don't care about BT)

c ) Port the 4.1.x stack over to 4.2.x

Essentially, c) is the only option for having Bluetooth. What sort of work does it take to port over the stack? How much has the low-level API (HAL?) that bluez hooks into changed from 4.1 to 4.2?

(Trevlig midsommar! :-))

Edited by Lipofil
0

Share this post


Link to post
Share on other sites

Posted

Well, what other options are there? I.e., what's the likelihood of Qualcomm releasing the specs (hah) or sample code for the MSM7227 chipset's Bluetooth functionality?

To get an Android 4.2.x on the ZTE Blade III, there are three options:

a ) Wait forever until drivers are released (unlikely)

b ) Use it without Bluetooth (sure, cool if you don't care about BT)

c ) Port the 4.1.x stack over to 4.2.x

Essentially, c) is the only option for having Bluetooth. What sort of work does it take to port over the stack? How much has the low-level API (HAL?) that bluez hooks into changed from 4.1 to 4.2?

(Trevlig midsommar! :-))

KonstaT has said that bt stack is completely different in 4.2 than in 4.1. About porting, I dont know, but it may be that he still needs some sources, etc? But it seems not to be impossible, KonstaT just do not want to waste half of the year with fighting to get bt work on 4.2. Its hard job to port it(If its possible at all)
0

Share this post


Link to post
Share on other sites

Posted

Well, what other options are there? I.e., what's the likelihood of Qualcomm releasing the specs (hah) or sample code for the MSM7227 chipset's Bluetooth functionality?

To get an Android 4.2.x on the ZTE Blade III, there are three options:

a ) Wait forever until drivers are released (unlikely)

b ) Use it without Bluetooth (sure, cool if you don't care about BT)

c ) Port the 4.1.x stack over to 4.2.x

Essentially, c) is the only option for having Bluetooth. What sort of work does it take to port over the stack? How much has the low-level API (HAL?) that bluez hooks into changed from 4.1 to 4.2?

(Trevlig midsommar! :-))

Qualcomm is with no doubt the best chipset manufacturer what comes to open sourcing and supporting their platform. They have wide range of in-house bluetooth solutions but unfortunately not all of them are (yet) supported with Android 4.2. I guess we'll have to wait and see what happens with the next Android version. MSM7x27A is not the only platform where this bt chip comes by 'default'. And by default doesn't mean that a vendor (e.g. ZTE in this case) would be forced to use Qualcomm bluetooth/wifi solution, they could have sticked in a Broadcom chip as well.

Porting bluez stack is quite invasive and that's why I wouldn't like to do it. And like said, it's not future proof either. 4.2 and everything onward will use bluedroid.

0

Share this post


Link to post
Share on other sites

Posted

hello,

please need help.

i tried to instal this rom on my zte blade 3

it gave an error and now i dont have any rom on my phone. please help

this is error i got. i took picture with my other phone ...

https://www.dropbox.com/s/yllt3aujgxtc0wm/2013-03-01%2016.24.44.jpg

help please

i have now the same problem, i can't help you... sorry ... but if you fix them please tell me how did you fix it :(
0

Share this post


Link to post
Share on other sites

Posted

i have now the same problem, i can't help you... sorry ... but if you fix them please tell me how did you fix it :(

So you managed to find that but you didn't find the solution. Person you quoted tried to install a Blade ROM on to a Blade III.

After reading your posts I'd seriously suggest that you'd stick with your stock ROM. :P

0

Share this post


Link to post
Share on other sites

Posted

So you managed to find that but you didn't find the solution. Person you quoted tried to install a Blade ROM on to a Blade III.

After reading your posts I'd seriously suggest that you'd stick with your stock ROM. :P

I am thinking same. Seems to be imbossible to guide him. He always try to install stock rom with cwm and vice versa. Arrrgh!
0

Share this post


Link to post
Share on other sites

Posted

Screenshot_2013_06_27_13_03_51.png

Hello, what's the problem here?

0

Share this post


Link to post
Share on other sites

Posted

Screenshot_2013_06_27_13_03_51.png

Hello, what's the problem here?

IIN english please. Usually reboot helps to clock problems(I have had them very rarely)
0

Share this post


Link to post
Share on other sites

Posted

Also not using automatic network time fixes it too..

0

Share this post


Link to post
Share on other sites

Posted

can someone help me? i have zte blade phone,i installed this rom works perfectly,but i have an error.... my phone always restart..when i write on browser,facebook,my phone reboot.. i think it's cpu problem? please Help!!!! (sorry for my bad english.. )

0

Share this post


Link to post
Share on other sites

Posted

Wrong section. Dont overclock(if you) and make a full wipe before installation.

0

Share this post


Link to post
Share on other sites

Posted (edited)

for the first time, my status bar's time is stuck. It has shown 19:58 since, I guess, 19:58 (three hours now).

I am not using automatic network time, I use NTP :) Every other app shows the time correctly. I am using yesterday's CM build.

EDIT: clock app's night mode does not update the time after initial startup :)

Edited by Otila
0

Share this post


Link to post
Share on other sites

Posted

I'm having a serious wtf moment. I don't understand Russian and Google translate doesn't help much either.

But Aurora Borealis only works with one SIM, right? It doesn't have dual-SIM dialer, messaging, settings, etc. Same goes to CyanogenMod, there is no dual-SIM support. At best it would work with single SIM.

Greetings Konstat

i'm from Russia

My English is bad, so I use a translator

I use Zte v880e Dual Sim and Aurora Borealis

after adding a line to build. prop

"persist.dsds.enable = true" smartphone uses two sim!

post-1018137-0-95628000-1372591084_thumb

post-1018137-0-93224300-1372591089_thumb

Is it possible to implement in your CM 10?

CM 10 runs on my smartphone but it does not work RILD

here are the lines from the log

"D / ConnectivityService (371): ConnectivityService starting up

E / MobileDataStateTracker (371): default: Ignoring feature request because could not acquire PhoneService

E / MobileDataStateTracker (371): default: Could not enable APN type "default" "

could you give me solution for repair radio on CM 10, please?

1

Share this post


Link to post
Share on other sites

Posted

Greetings Konstat

i'm from Russia

My English is bad, so I use a translator

I use Zte v880e Dual Sim and Aurora Borealis

after adding a line to build. prop

"persist.dsds.enable = true" smartphone uses two sim!

Is it possible to implement in your CM 10?

CM 10 runs on my smartphone but it does not work RILD

could you give me solution for repair radio on CM 10, please?

I've added a second rild service for dual-sim devices in the latest CyanogenMod10 build (this thread is for CM10.1). You can enable it by adding 'ro.multi.rild=true' to your build.prop. Could you test that and report back in the CM10 thread? You might get one SIM working but I doubt it.

Qualcomm has open sourced their dual-SIM implementation and there are working CyanogenMod ports for dual-SIM devices thanks to this (e.g. some Huawei devices, Sony Xperia E Dual). It is quite extensive and it needs quite a bit of modification to TelephonyProvider, Phone, Mms, Settings, etc. I doubt it would be much of a problem to make everything work only if I had a dual-SIM device myself. Currently I can't do any more help you.

0

Share this post


Link to post
Share on other sites

Posted

New build. Mostly the same stuff that was in the previous CM10 build. FM radio, new libaudio and new kernel. FM radio works so much better than with CM10. Mute works, no annoying volume skipping and it also has an updated (not so ugly :P) FM app. Of course all the latest merged CyanogenMod features are included as well.

cm-10.1-20130704-KonstaKANG-atlas40.zip

https://hotfile.com/dl/232424234/7518508/cm-10.1-20130704-KonstaKANG-atlas40.zip.html

md5:b920256bb405e20af1893520cae2dfca

-fixed FM radio

-updated libaudio

-switched to caf kernel (source)

-CM10.1.1

3

Share this post


Link to post
Share on other sites

Posted (edited)

own build hangs in "Starting apps."

EDIT: works with KonstaKANG zip


W/AudioSystem( 469): AudioFlinger not published, waiting...

W/IMediaDeathNotifier( 469): Media player service not published, waiting...

I/ServiceManager( 469): Waiting for service media.audio_flinger...

I/ServiceManager( 469): Waiting for service media.player...

I/ServiceManager( 469): Waiting for service media.audio_flinger...

I/ServiceManager( 469): Waiting for service media.player...

I/ServiceManager( 469): Waiting for service media.audio_flinger...

I/ServiceManager( 469): Waiting for service media.player...

I/mediaserver( 1101): ServiceManager: 0x40d73ed8

F/libc	( 1101): Fatal signal 7 (SIGBUS) at 0x00000000 (code=128), thread 1101 (mediaserver)

I/DEBUG ( 108): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG ( 108): Build fingerprint: 'ZTE/N880E_JB4_2/atlas40:4.2/JOP40C/20121121.110335:user/release-keys'

I/DEBUG ( 108): Revision: '0'

I/DEBUG ( 108): pid: 1101, tid: 1101, name: mediaserver >>> /system/bin/mediaserver <<<

I/DEBUG ( 108): signal 7 (SIGBUS), code 128 (?), fault addr 00000000

I/ServiceManager( 469): Waiting for service media.audio_flinger...

I/DEBUG ( 108):	 r0 40d740bd r1 beca0b08 r2 00000160 r3 40d740bd

I/DEBUG ( 108):	 r4 40d740b9 r5 beca0b08 r6 beca0aac r7 00000000

I/DEBUG ( 108):	 r8 00000000 r9 00000000 sl 00000000 fp beca0bec

I/DEBUG ( 108):	 ip 40193e88 sp beca0a88 lr 40188f41 pc 400490d8 cpsr 000f0010

I/DEBUG ( 108):	 d0 00650067006e0069 d1 006c0066005f006f

I/DEBUG ( 108):	 d2 0076007200650065 d3 004d006500630000

I/DEBUG ( 108):	 d4 0000000000000000 d5 0000000000000000

I/DEBUG ( 108):	 d6 0000000000000000 d7 3479371600000000

I/DEBUG ( 108):	 d8 0000000000000000 d9 0000000000000000

I/DEBUG ( 108):	 d10 0000000000000000 d11 0000000000000000

I/DEBUG ( 108):	 d12 0000000000000000 d13 0000000000000000

I/DEBUG ( 108):	 d14 0000000000000000 d15 0000000000000000

I/DEBUG ( 108):	 d16 41ca3c9b8b3d4fdf d17 3f50624dd2f1a9fc

I/DEBUG ( 108):	 d18 41b568cfcf000000 d19 0000000000000000

I/DEBUG ( 108):	 d20 0000000000000000 d21 0000000000000000

I/DEBUG ( 108):	 d22 0000000000000000 d23 0000000000000000

I/DEBUG ( 108):	 d24 0000000000000000 d25 0000000000000000

I/DEBUG ( 108):	 d26 0000000000000000 d27 0000000000000000

I/DEBUG ( 108):	 d28 0000000000000000 d29 0000000000000000

I/DEBUG ( 108):	 d30 0000000000000000 d31 0000000000000000

I/DEBUG ( 108):	 scr 00000010

I/DEBUG ( 108):

I/DEBUG ( 108): backtrace:

I/DEBUG ( 108):	 #00 pc 000050d8 /system/lib/libcutils.so (android_atomic_inc+4)

I/DEBUG ( 108):	 #01 pc 0000ef3d /system/lib/libutils.so (android::RefBase::incStrong(void const*) const+6)

I/DEBUG ( 108):	 #02 pc 0001c40f /system/lib/libbinder.so (android::acquire_object(android::sp<android::ProcessState> const&, android::flat_binder_object const&, void const*)+66)

I/DEBUG ( 108):	 #03 pc 0001cb1d /system/lib/libbinder.so (android::Parcel::writeObject(android::flat_binder_object const&, bool)+76)

I/DEBUG ( 108):	 #04 pc 0001cc45 /system/lib/libbinder.so (android::flatten_binder(android::sp<android::ProcessState> const&, android::sp<android::IBinder> const&, android::Parcel*)+104)

I/DEBUG ( 108):	 #05 pc 0001cd5f /system/lib/libbinder.so (android::Parcel::writeStrongBinder(android::sp<android::IBinder> const&)+18)

I/DEBUG ( 108):	 #06 pc 0001a563 /system/lib/libbinder.so

I/DEBUG ( 108):	 #07 pc 000009d3 /system/bin/mediaserver

I/DEBUG ( 108):	 #08 pc 00000ae7 /system/bin/mediaserver

I/DEBUG ( 108):	 #09 pc 0001274b /system/lib/libc.so (__libc_init+38)

I/DEBUG ( 108):	 #10 pc 00000908 /system/bin/mediaserver

I/DEBUG ( 108):

I/DEBUG ( 108): stack:

I/DEBUG ( 108):		 beca0a48 c0000000

I/DEBUG ( 108):		 beca0a4c 00000006

I/DEBUG ( 108):		 beca0a50 c0000000

I/DEBUG ( 108):		 beca0a54 0000000c

I/DEBUG ( 108):		 beca0a58 beca0ac8 [stack]

I/DEBUG ( 108):		 beca0a5c 00000003

I/DEBUG ( 108):		 beca0a60 00000013

I/DEBUG ( 108):		 beca0a64 401103e9 /system/lib/libc.so (dlmalloc+5172)

I/DEBUG ( 108):		 beca0a68 000000a2

I/DEBUG ( 108):		 beca0a6c 40110fc9 /system/lib/libc.so (dlrealloc+116)

I/DEBUG ( 108):		 beca0a70 beca0b08 [stack]

I/DEBUG ( 108):		 beca0a74 000000a2

I/DEBUG ( 108):		 beca0a78 40d74178 [heap]

I/DEBUG ( 108):		 beca0a7c beca0b08 [stack]

I/DEBUG ( 108):		 beca0a80 df0027ad

I/DEBUG ( 108):		 beca0a84 00000000

I/DEBUG ( 108):	 #00 beca0a88 beca0ac8 [stack]

I/DEBUG ( 108):		 ........ ........

I/DEBUG ( 108):	 #01 beca0a88 beca0ac8 [stack]

I/DEBUG ( 108):		 beca0a8c 40252413 /system/lib/libbinder.so (android::acquire_object(android::sp<android::ProcessState> const&, android::flat_binder_object const&, void const*)+70)

I/DEBUG ( 108):	 #02 beca0a90 beca0aac [stack]

I/DEBUG ( 108):		 beca0a94 beca0ac8 [stack]

I/DEBUG ( 108):		 beca0a98 beca0b08 [stack]

I/DEBUG ( 108):		 beca0a9c beca0ac8 [stack]

I/DEBUG ( 108):		 beca0aa0 40d7413c [heap]

I/DEBUG ( 108):		 beca0aa4 40252b21 /system/lib/libbinder.so (android::Parcel::writeObject(android::flat_binder_object const&, bool)+80)

I/DEBUG ( 108):

Edited by Otila
0

Share this post


Link to post
Share on other sites

Posted

own build hangs in "Starting apps."

Make sure that your device manifest is up to date and you have these two patches applied (1,2).

Copy them to frameworks/base and


git am -3 *.patch
[/CODE] Or create a separate branch so you don't have reapply them after every repo sync
[CODE]
cd cm10.1-workdir
repo start branchname ./frameworks/base
cd frameworks/base
git am -3 *.patch

1

Share this post


Link to post
Share on other sites

Posted

Onthis ROM my wifi connection is very poor (cm 10.1) :( On CM 10 everything was fine. Anyone else got this problem?

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

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