Jump to content

[DEV][ROM][20.12.] CyanogenMod 10.2 (Android 4.3.1)


Recommended Posts

Guest Fizziebaunz

--------- beginning of /dev/log/system

10-31 09:25:40.940 E/ConnectivityService(400): startUsingNetworkFeature took too long: 743ms

10-31 09:25:45.630 E/NetdConnector(400): NDC Command {649 bandwidth removeiquota rmnet0} took too long (566ms)

10-31 09:25:56.130 E/NetdConnector(400): NDC Command {664 bandwidth setiquota rmnet0 4781447227} took too long (726ms)

10-31 09:25:57.090 E/NetdConnector(400): NDC Command {666 bandwidth setiquota rmnet0 4781447227} took too long (672ms)

10-31 09:25:57.830 E/NetdConnector(400): NDC Command {667 bandwidth removeiquota rmnet0} took too long (507ms)

10-31 09:25:58.970 E/NetdConnector(400): NDC Command {668 bandwidth setiquota rmnet0 4781447227} took too long (1136ms)

10-31 09:25:59.720 E/NetdConnector(400): NDC Command {669 bandwidth removeiquota rmnet0} took too long (745ms)

10-31 09:26:00.700 E/NetdConnector(400): NDC Command {670 bandwidth setiquota rmnet0 4781447227} took too long (980ms)

10-31 09:26:04.210 E/ActivityThread(24229): Failed to find provider info for com.modoohut.provider.geocoder

10-31 09:26:23.930 E/NetdConnector(400): NDC Command {688 bandwidth setiquota rmnet0 4781442883} took too long (667ms)

10-31 09:26:25.600 E/ConnectivityService(400): Carrier Provisioning Urls file not found

10-31 09:39:31.770 E/PerformBackupTask(400): Transport error in initializeDevice()

--------- beginning of /dev/log/main

10-31 10:19:21.540 E/Finsky (25120): [1086] FileBasedKeyValueStore.delete: Attempt to delete 'paramsbhNOBn26uCJlVIPzgHrJwQ' failed!

10-31 10:19:30.280 E/InputDispatcher(400): channel '41ae8e38 com.advancedprocessmanager/com.advancedprocessmanager.Tabs (server)' ~ Channel is unrecoverably broken and will be disposed!

10-31 10:20:55.510 E/cutils-trace(25701): Error opening trace file: No such file or directory (2)

10-31 10:21:25.760 E/cutils-trace(25845): Error opening trace file: No such file or directory (2)

10-31 10:21:38.280 E/cutils-trace(25875): Error opening trace file: No such file or directory (2)

10-31 10:21:41.960 E/cutils-trace(25909): Error opening trace file: No such file or directory (2)

10-31 10:21:46.070 E/cutils-trace(25955): Error opening trace file: No such file or directory (2)

10-31 10:21:55.240 E/cutils-trace(25988): Error opening trace file: No such file or directory (2)

10-31 10:21:56.550 E/cutils-trace(26008): Error opening trace file: No such file or directory (2)

10-31 10:23:10.280 E/SpannableStringBuilder(563): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length

10-31 10:23:21.790 E/SpannableStringBuilder(563): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length

10-31 10:27:49.940 E/MetadataRetrieverClient(21693): failed to extract an album art

10-31 10:27:50.110 E/MetadataRetrieverClient(21693): failed to extract an album art

10-31 10:31:11.860 F/libc (26125): Fatal signal 4 (SIGILL) at 0x523d500c (code=1), thread 26155 (droid.gallery3d)

10-31 10:31:14.060 E/InputDispatcher(400): channel '41a96d88 com.android.gallery3d/com.android.gallery3d.app.Gallery (server)' ~ Channel is unrecoverably broken and will be disposed!

10-31 10:31:14.080 E/InputDispatcher(400): channel '41b5e738 com.android.gallery3d/com.android.gallery3d.filtershow.FilterShowActivity (server)' ~ Channel is unrecoverably broken and will be disposed!

Someone help me understand the above logcat

Link to post
Share on other sites
  • Replies 682
  • Created
  • Last Reply

Popular Posts

This is my port of CyanogenMod 10.2 for ZTE Blade. It is unofficial and unsupported by the CyanogenMod team. This ROM is mainly for developers/testers/advanced users. I'm really not interested in hear

Merged commits not mentioned in the changelog. 20.12. changelog: CM 10.2.0 final WhisperPush (merged) 11.10. changelog: android 4.3.1 24.9. changelog: fixed dat

New build. Just keeping up with upstream.   cm-10.2-20131011-KonstaKANG-blade.zip https://hotfile.com/dl/250174260/84828b3/cm-10.2-20131011-KonstaKANG-blade.zip.html md5:4e3d5a2b1ae256486b900498c657fd

Posted Images

Guest rohitzz

Hii all I was using blade for 2 year and now I use karbonn titanium s1 with snapdragon 200 quad core processor.

Specs- http://pdadb.net/index.php?m=specs&id=4497&view=1&c=karbonn_s1_titanium

So I've seen easy method porting rom for my phone here - http://forum.xda-developers.com/showthread.php?t=1908008

My Question is

1.Can I use my stock rom as my base rom for this tutorial.

2.And mainly which rom should I take for port rom for this tutorial on my phone

3.In case I want to port cm 10.2 then can I use zte blade rom as port rom.

4.And if not then which phone's rom can I take as port rom.

Link to post
Share on other sites
Guest Fizziebaunz

Fizziebaunz:

My tips would be...

Size of /system and /data, available free space, have you mounted /data with -o ro?

When did it began, by the way?

well it begun after flashing the latest build.... system is 160..... free space is 0.6MB.... data has a lot of free space like 170MB I use link2sd.... I don't know how to mount data. ....

Link to post
Share on other sites

well it begun after flashing the latest build.... system is 160..... free space is 0.6MB.... data has a lot of free space like 170MB I use link2sd.... I don't know how to mount data. ....
 

. . . You'll need at least 180mb system partition for the ROM and gapps to fit. Both gen1->gen2 and G2 TPTs are available at Amphoras' site. Gen3 patch for CM7/9/10/10.1/10.2 available at my CM9 thread . . .
Link to post
Share on other sites

Aguess, while Google announced Android 4.4 KitKat -version, "slimmer" for even 512 mb ram phones, we'll soon see KonstaT's KitKat too : ) 

 

http://developer.android.com/about/versions/kitkat.html

 

http://source.android.com/source/downloading.html

 

 

Not necessarily, it works well on phone with 512MB ram, it doesn't say anything about how much storage space it needs. android 4.3 rom requires use to change the partition size, after installing gapps there is only a few mb left. It may not fit on the partition.

Link to post
Share on other sites

I did trim the rom before flashing.... only problem is gallery force closes during picture edit

 

mine is 160mb too.

if you trimmed your rom can be alot of things, depending of what you have removed, only you know. my advice is, test with a 180mb partition just for ensure the size is big enough. if the problem does not reappear in the partition of 180mb, you'll know. . . .

Link to post
Share on other sites
Guest Fizziebaunz

mine is 160mb too.

if you trimmed your rom can be alot of things, depending of what you have removed, only you know. my advice is, test with a 180mb partition just for ensure the size is big enough. if the problem does not reappear in the partition of 180mb, you'll know. . . .

And do you have that kind of problem with picture editing.... using gallery.

Link to post
Share on other sites

@KonstaT

 

Kit kat 4.4 is optimised to work on lower end devices with 512MB RAM. Would  you please  make a release

for brilliant Blade I.

Thanks in advance for your great work! 

Link to post
Share on other sites

And do you have that kind of problem with picture editing.... using gallery.

 

 

i don't have blade with me right now, i'll test as soon as i can

 

all ok, i've tested editing a photo using gallery with no problem.

Link to post
Share on other sites
Guest Sulthekk

@KonstaT

Kit kat 4.4 is optimised to work on lower end devices with 512MB RAM. Would you please make a release

for brilliant Blade I.

Thanks in advance for your great work!

There's been a lot of changes under the hood. Even with the lower memory footprint, we have no idea about compatibility, storage requirements, etc. Also, it seems to make use of zram, ksm to achieve that ram usage, which - while really reduces memory footprint - increases CPU usage. While we truly have 512Mb ram, we also have a legacy armv6 processor, which google doesn't even supports, neither within android itself, nor within apps like google now.

PS: On the other hand, I recall KonstaT once said he likes a challenge, and he had already surprised us in the past. I wouldn't be surprised if he at least attempted a port, but don't keep your hopes too high - while 4.3 is a true miracle for our phones, every device has it's limits, and we have been on the borders for quite long now - KitKat may already be on the 'other side'.

Edited by Sulthekk
Link to post
Share on other sites

There's been a lot of changes under the hood. Even with the lower memory footprint, we have no idea about compatibility, storage requirements, etc. Also, it seems to make use of zram, ksm to achieve that ram usage, which - while really reduces memory footprint - increases CPU usage. While we truly have 512Mb ram, we also have a legacy armv6 processor, which google doesn't even supports, neither within android itself, nor within apps like google now.

PS: On the other hand, I recall KonstaT once said he likes a challenge, and he had already surprised us in the past. I wouldn't be surprised if he at least attempted a port, but don't keep your hopes too high - while 4.3 is a true miracle for our phones, every device has it's limits, and we have been on the borders for quite long now - KitKat may already be on the 'other side'.

Pont azt írják,hogy kevesebb ramot eszik,kevesebb cpu-t te meg ennek az ellentkezőjét mondod... Pont hogy ez a 4.3 lassú :S

Edited by mforce
Link to post
Share on other sites
Guest Sulthekk

android 4.4 uses lower ram and lower cpu than this, on 4.4 i think we don't need to use zram and ksm... but we'll see

Elnézést, kik "mondják"? Persze, a Google-alkalmazottaknak ez a dolguk. Time-memory tradeoff ismerôs fogalom?

Biztos optimalizálgattak itt-ott, de ezeknek a technológiáknak az egyidejû használata számításigényes:

KSM:

Idôrôl idôre végig kell nézni a memórialapokat. Csak a CPU képes rá.

zRam:

A tömörítést sem a GPU végzi, hacsak valahonnan nem kerítesz OpenCL-es drivereket adreno200-hoz, armv6-ra fordítva.

Dalvik "optimalizáció":

Az armv6 hivatalosan már egy ideje NEM kap támogatást a google részérôl, úgy kell visszahegeszteni a 4.X-es androidokra. Még ha kicsit csökken(het) is a memóriahasználat, az új JIT kódot armv7-re írták meg, nekünk marad a régi 2.3-ból átvett JIT kód foltozgatása.

Szép a reklám, csak nem a Bladenek szól. :(

Others: Sorry for not using english, I am too sleepy to translate that right now. Sum: see my previous post.

Link to post
Share on other sites
Guest Fizziebaunz

It turns out... the problem was not partition.... cause gallery force closes.... after selecting the last option in picture editing.... will find another app to replace that....

Link to post
Share on other sites

It turns out... the problem was not partition.... cause gallery force closes.... after selecting the last option in picture editing.... will find another app to replace that....

 

if you looking for a lightweight replacement, quickpic is the best.

Link to post
Share on other sites
Guest silverchair

Let's not forget that Konstat always builds against Cyanogenmod, and there is no 4.4 release yet. Still if there are indeed performance improvements, I would gladly try it on my blade.

Link to post
Share on other sites
Guest Ceaușescu

Let's not forget that Konstat always builds against Cyanogenmod, and there is no 4.4 release yet. Still if there are indeed performance improvements, I would gladly try it on my blade.

+1

Like to see Kitkat on my Blade.

Link to post
Share on other sites
Guest RusselM

Not sure if this is mentioned before, so first of all sorry if this is a repo.


When I CLEAN install this ROM (and I use Konsta's latest build of Android 4.2.2) my Google account disappears and there's no way of getting it back.
Furthermore Play Store crashes and all of my contacts are gone, even importing them from SD does not help.
Can this be related to my SIM? Or why can't my device run the Android 4.3(.1) build?

Thanks in advance!

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.