Guest Otila Posted April 10, 2013 Report Posted April 10, 2013 I have fetched these with curl as mentioned in the docs .repo/local_manifests/local_manifest.xml .repo/local_manifests/manifest_zte_atlas40.xml I also got the android_device_zte_atlas40 git , but shouldn't repo sync populate these? device/zte/atlas40 kernel/zte/zte-kernel-msm7x27a vendor/zte
Guest robt77 Posted April 10, 2013 Report Posted April 10, 2013 They should do but if you are building for CM10.1 there is a lot of hacking involved apparently. KonstaT advised it was easier to learn compiling with CM10 first as it is easier. I never got close to compiling for CM10.1 got close with CM10 but turns out my old PC is very low on RAM and just gave up half way through the build:(
Guest DigitalEntity Posted April 10, 2013 Report Posted April 10, 2013 Hi guys! I'm new to Blade III community and smartphones for that matter so I decided to try out CM10.1 on my device and ran in some issues. As I am completely new to ROM modding i'll report them here so U, more tech savvy guys can maybe fix some of it in next version :) 1. Internal memory access - on stock ROM it was possible to access internal memory through internal file manager and over USB connection... maybe permissions issue? --- heh found solution while tipping post :) -- root access in file manager settings :) 2. notifications - there is no way of importing custom notification sounds... I had my Ringtones in same named folder on my SDCard and they all were automatically imported in Ringtone melodies for some reason, can some other folder name be automatic for notifications or something? 3. using google voice chat from gTalk not possible - Tried to use voice chat but looks like mic is muted in app tried unmuting it but no change. Skype and normal calls work fine, sound recording works fine. other side joust does not receive any sound. and bluetooth ofc but as i can see you guys are aware of it. that's all for now :)
Guest Otila Posted April 11, 2013 Report Posted April 11, 2013 positive development: ext4 is supported for SD card; no need for FAT at all. # grep sdcard /proc/mounts /dev/block/vold/179:33 /mnt/fuse/sdcard ext4 rw,dirsync,nosuid,nodev,noexec,noatime,user_xattr,barrier=1,data=ordered 0 0 tmpfs /mnt/fuse/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0 /dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Guest Otila Posted April 11, 2013 Report Posted April 11, 2013 (edited) dirs on the ext4 partition have to be mode 777, 755 does not work: 04-11 17:37:18.859 I/ActivityManager( 444): Displayed com.google.android.apps.translate/.offline.OfflinePackageActivity: +427ms 04-11 17:37:19.029 E/OfflineFileDownloader( 4949): Error writing to file /storage/sdcard0/Android/data/com.google.android.apps.translate/files/ol/v3r1/profiles.txt 04-11 17:37:19.029 E/OfflineFileDownloader( 4949): java.io.FileNotFoundException: /storage/sdcard0/Android/data/com.google.android.apps.translate/files/ol/v3r1/profiles.txt: open failed: EACCES (Permission denied) EDIT: Also, all files have to be 777 (did not try 775, though). EDIT2: this hack seems to be untested, Gallery crashes. 04-11 18:55:56.456 I/DownloadManager( 7413): in removeSpuriousFiles 04-11 18:55:56.516 E/MediaProvider( 7413): Can't obtain external volume ID even though it's mounted. 04-11 18:55:56.536 D/AndroidRuntime( 7413): Shutting down VM 04-11 18:55:56.536 W/dalvikvm( 7413): threadid=1: thread exiting with uncaught exception (group=0x414dd930) 04-11 18:55:56.556 E/AndroidRuntime( 7413): FATAL EXCEPTION: main 04-11 18:55:56.556 E/AndroidRuntime( 7413): java.lang.RuntimeException: Unable to get provider com.android.providers.media.MediaProvider: java.lang.IllegalArgumentException: Can't obtain external volume ID for external volume. 04-11 18:55:56.556 E/AndroidRuntime( 7413): at android.app.ActivityThread.installProvider(ActivityThread.java:5007) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at android.app.ActivityThread.installContentProviders(ActivityThread.java:4617) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4557) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at android.app.ActivityThread.access$1300(ActivityThread.java:153) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1307) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at android.os.Handler.dispatchMessage(Handler.java:99) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at android.os.Looper.loop(Looper.java:137) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at android.app.ActivityThread.main(ActivityThread.java:5226) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at java.lang.reflect.Method.invokeNative(Native Method) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at java.lang.reflect.Method.invoke(Method.java:511) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:562) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at dalvik.system.NativeStart.main(Native Method) 04-11 18:55:56.556 E/AndroidRuntime( 7413): Caused by: java.lang.IllegalArgumentException: Can't obtain external volume ID for external volume. 04-11 18:55:56.556 E/AndroidRuntime( 7413): at com.android.providers.media.MediaProvider.attachVolume(MediaProvider.java:4986) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at com.android.providers.media.MediaProvider.onCreate(MediaProvider.java:598) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at android.content.ContentProvider.attachInfo(ContentProvider.java:1058) 04-11 18:55:56.556 E/AndroidRuntime( 7413): at android.app.ActivityThread.installProvider(ActivityThread.java:5004) 04-11 18:55:56.556 E/AndroidRuntime( 7413): ... 12 more 04-11 18:55:56.566 I/am_crash( 441): [7413,0,android.process.media,13155909,java.lang.IllegalArgumentException,Can't obtain external volume ID for external volume.,MediaProvider.java,4986] 04-11 18:55:56.596 I/am_process_crashed_too_much( 441): [0,android.process.media,10014] 04-11 18:55:56.596 I/am_proc_bad( 441): [0,10014,android.process.media] 04-11 18:55:56.596 W/ActivityManager( 441): Process android.process.media has crashed too many times: killing! 04-11 18:55:56.596 I/ActivityManager( 441): Killing proc 7413:android.process.media/u0a10014: crash 04-11 18:55:56.596 W/ActivityManager( 441): Unable to launch app com.android.providers.media/10014 for provider media: launching app became null 04-11 18:55:56.596 W/ActivityManager( 441): Unable to launch app com.android.providers.media/10014 for provider media: launching app became null 04-11 18:55:56.606 I/am_provider_lost_process( 441): [0,com.android.providers.downloads,10014,downloads] 04-11 18:55:56.606 W/ActivityManager( 441): Unable to launch app com.android.providers.downloads/10014 for provider downloads: launching app became null 04-11 18:55:56.626 E/ActivityThread( 7236): Failed to find provider info for media 04-11 18:55:56.646 E/ActivityThread( 7236): Failed to find provider info for media 04-11 18:55:56.666 E/ActivityThread( 7192): Failed to find provider info for downloads Edited April 11, 2013 by Otila
Guest KonstaT Posted April 11, 2013 Report Posted April 11, 2013 My Brother Xperia J, have stable 1.3GHz OC and better run 3d games >.> Xperia J have better optimalization ? None of the 'official' CyanogenMod kernels on Sony MSM7x27A devices even have overclock support. I haven't found any 'unofficial' OC kernels for CM either. There's one kernel for stock ROMs that advertises to have stable 1.3GHz OC. That overclocking code is even worse than what the Huawei G300 guys had some eight months ago (that's where I've copied mine). Simply adding some frequencies to the table doesn't do it. Hi I have stock ROM in my Blade III. I am interested in developing radio support in unofficial ROMs. So, I started adb shell, next I plugged headphones and started radio. After that I wrote dmesg in adb shell. I saw that radio identifies itself as Tavarua. Does anybody tried to add support for tavarua in kernel? You think someone removed the support? ;) Kernel is fine... CyanogenMod doesn't have proper support for Qualcomm FM. There's support for ST-Ericsson implementation but you'd need to write a new driver for that. Another approach would be to port radio app and changes in audio framework/device audio from CodeAurora. I am following docs from https://github.com/K...ice_zte_atlas40 now after repo sync there's 13 GiB of stuff but something is missing. lunch cm_atlas40-userdebug fails: ls: cannot access device/*/atlas40/cm.mk: No such file or directory build/core/product_config.mk:234: *** Cannot locate config makefile for product "cm_atlas40". Stop. Device atlas40 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod). Repository for atlas40 not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml. What repo version do you have? You need to have a recent repo that supports manifests in local_manifest folder. They should do but if you are building for CM10.1 there is a lot of hacking involved apparently. KonstaT advised it was easier to learn compiling with CM10 first as it is easier. I never got close to compiling for CM10.1 got close with CM10 but turns out my old PC is very low on RAM and just gave up half way through the build:( CM10.1 is fine if you use my manifests as above. They also replace few CM projects so it won't be so simple with paranoid android/aokp/rootbox/etc.
Guest Otila Posted April 11, 2013 Report Posted April 11, 2013 CM10.1 is fine if you use my manifests as above. They also replace few CM projects so it won't be so simple with paranoid android/aokp/rootbox/etc. I had repo v1.18 from google chrome, I didn't think about the version because it was not discussed on that guide page and I did not get warnings about old version,.. I tried also with 1.19 now: ls: cannot access device/*/atlas40/cm.mk: No such file or directory (the same as before) "repo list" output http://pastebin.com/TvbQsefj
Guest KonstaT Posted April 11, 2013 Report Posted April 11, 2013 I had repo v1.18 from google chrome, I didn't think about the version because it was not discussed on that guide page and I did not get warnings about old version,.. I tried also with 1.19 now: ls: cannot access device/*/atlas40/cm.mk: No such file or directory (the same as before) "repo list" output http://pastebin.com/TvbQsefj Local manifests are not picked up. Are you sure that you have copies in your cm10.1/.repo/local_manifests/*? Repo v1.19 is also required. Get sources: repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1 curl --create-dirs -L -o .repo/local_manifests/local_manifest.xml -O -L https://raw.github.com/legaCyMod/android_local_manifest/cm-10.1/local_manifest.xml curl --create-dirs -L -o .repo/local_manifests/manifest_zte_atlas40.xml -O -L https://raw.github.com/legaCyMod/android_local_manifest/cm-10.1/manifest_zte_atlas40.xml repo sync [/CODE] Build: [CODE]. build/envsetup.sh brunch atlas40
Guest Otila Posted April 11, 2013 Report Posted April 11, 2013 Maybe dir structure is messed up, I don't know anymore. but repo sync does not whine. $ ls -la . .repo .repo/local_manifests .: total 248 drwxr-xr-x 29 safari xuser 4096 Apr 11 23:05 . drwx--x--x 529 safari safari 28672 Apr 11 23:17 .. drwxr-xr-x 3 safari xuser 16 Apr 7 23:03 abi drwxr-xr-x 3 safari xuser 116 Apr 11 20:59 android drwxr-xr-x 10 safari xuser 4096 Apr 7 23:03 bionic drwxr-xr-x 4 safari xuser 41 Apr 7 23:03 bootable drwxr-xr-x 7 safari xuser 145 Apr 11 10:14 build -rw-r--r-- 1 safari xuser 33362 Apr 11 22:41 cm-10.1-M1.xml -rw-r--r-- 1 safari xuser 33804 Apr 11 22:41 cm-10.1-M2.xml -rw-r--r-- 1 safari xuser 33786 Apr 11 22:41 cm-10.1-M3.xml drwxr-xr-x 11 safari xuser 4096 Apr 7 23:03 cts drwxr-xr-x 18 safari xuser 4096 Apr 7 23:03 dalvik -rw-r--r-- 1 safari xuser 33868 Apr 11 22:41 default.xml drwxr-xr-x 18 safari xuser 4096 Apr 7 23:03 development drwxr-xr-x 7 safari xuser 68 Apr 10 17:51 device drwxr-xr-x 3 safari xuser 31 Apr 7 23:03 docs drwxr-xr-x 174 safari xuser 4096 Apr 11 20:59 external drwxr-xr-x 14 safari xuser 142 Apr 7 23:10 frameworks drwxr-xr-x 10 safari xuser 4096 Apr 7 23:10 gdk drwxr-xr-x 2 safari xuser 152 Apr 11 23:17 .git drwxr-xr-x 12 safari xuser 151 Apr 7 23:10 hardware drwxr-xr-x 11 safari xuser 4096 Apr 7 23:10 libcore drwxr-xr-x 4 safari xuser 121 Apr 7 23:10 libnativehelper -r--r--r-- 1 safari xuser 87 Apr 7 23:03 Makefile drwxr-xr-x 8 safari xuser 4096 Apr 7 23:10 ndk drwxr-xr-x 8 safari xuser 107 Apr 7 23:11 packages drwxr-xr-x 5 safari xuser 70 Apr 7 23:11 pdk drwxr-xr-x 6 safari xuser 105 Apr 7 23:11 prebuilt drwxr-xr-x 10 safari xuser 103 Apr 7 23:14 prebuilts -rw-r--r-- 1 safari xuser 1779 Apr 11 22:41 README.mkdn drwxr-xr-x 7 safari xuser 4096 Apr 11 23:02 .repo drwxr-xr-x 51 safari xuser 4096 Apr 7 23:14 sdk drwxr-xr-x 9 safari xuser 95 Apr 7 23:14 system drwxr-xr-x 4 safari xuser 32 Apr 7 23:14 tools drwxr-xr-x 5 safari xuser 40 Apr 7 23:14 vendor .repo: total 52 drwxr-xr-x 7 safari xuser 4096 Apr 11 23:02 . drwxr-xr-x 29 safari xuser 4096 Apr 11 23:05 .. drwxr-xr-x 2 safari xuser 62 Apr 11 22:56 local_manifests drwxr-xr-x 3 safari xuser 116 Apr 11 21:25 manifests drwxr-xr-x 9 safari xuser 4096 Apr 7 17:24 manifests.git lrwxrwxrwx 1 safari xuser 21 Apr 7 17:02 manifest.xml -> manifests/default.xml -rw-r--r-- 1 safari xuser 7477 Apr 11 23:14 project.list drwxr-xr-x 27 safari xuser 4096 Apr 7 21:19 projects drwxr-xr-x 7 safari xuser 4096 Apr 7 19:21 repo -rw-r--r-- 1 safari xuser 23696 Apr 11 23:14 .repopickle_fetchtimes .repo/local_manifests: total 12 drwxr-xr-x 2 safari xuser 62 Apr 11 22:56 . drwxr-xr-x 7 safari xuser 4096 Apr 11 23:02 .. -rw-r--r-- 1 safari xuser 1783 Apr 11 21:21 local_manifest.xml -rw-r--r-- 1 safari xuser 393 Apr 11 21:22 manifest_zte_atlas40.xml $ ls -l .git/ total 8 lrwxrwxrwx 1 safari xuser 36 Apr 11 23:12 config -> ../.repo/projects/android.git/config lrwxrwxrwx 1 safari xuser 41 Apr 11 23:12 description -> ../.repo/projects/android.git/description -rw-r--r-- 1 safari xuser 41 Apr 11 22:41 HEAD lrwxrwxrwx 1 safari xuser 35 Apr 11 23:12 hooks -> ../.repo/projects/android.git/hooks -rw-r--r-- 1 safari xuser 465 Apr 11 23:17 index lrwxrwxrwx 1 safari xuser 34 Apr 11 23:13 info -> ../.repo/projects/android.git/info lrwxrwxrwx 1 safari xuser 34 Apr 11 23:13 logs -> ../.repo/projects/android.git/logs lrwxrwxrwx 1 safari xuser 37 Apr 11 23:13 objects -> ../.repo/projects/android.git/objects lrwxrwxrwx 1 safari xuser 41 Apr 11 23:13 packed-refs -> ../.repo/projects/android.git/packed-refs lrwxrwxrwx 1 safari xuser 34 Apr 11 23:13 refs -> ../.repo/projects/android.git/refs lrwxrwxrwx 1 safari xuser 38 Apr 11 23:13 rr-cache -> ../.repo/projects/android.git/rr-cache $ cat .git/HEAD .repo/projects/android.git/HEAD 59ddb2924ebc7cb8208973ec86647d8b6ab2a3df ref: refs/heads/master
Guest Otila Posted April 11, 2013 Report Posted April 11, 2013 (edited) I manually shoved some git repos mentioned at http://www.modaco.co...yanogenmod-10.1 to device/zte/atlas40 vendor/zte/atlas40 kernel/zte/zte-kernel-msm7x27a make started making, I go now sleeping and hopefully I have some breakfast when I wake up.. EDIT: make: *** No rule to make target `vendor/cm/proprietary/Term.apk', needed by `/wrk/safari/cvs/android/out/target/product/atlas40/system/app/Term.apk'. Stop. "repo sync" syncs, but not everything to annoy users, have to manually run ./get-prebuilts EDIT2: make: *** No rule to make target `/wrk/safari/cvs/android/out/target/product/atlas40/obj/STATIC_LIBRARIES/lib_driver_cmd_ath6kl_intermediates/export_includes', needed by `/wrk/safari/cvs/android/out/target/product/atlas40/obj/EXECUTABLES/hostapd_intermediates/import_includes'. Stop. $ . build/envsetup.sh && lunch cm_atlas40-userdebug including device/generic/armv7-a-neon/vendorsetup.sh including device/generic/armv7-a/vendorsetup.sh including device/generic/mips/vendorsetup.sh including device/generic/x86/vendorsetup.sh including device/ti/panda/vendorsetup.sh including device/zte/atlas40/vendorsetup.sh including vendor/cm/vendorsetup.sh including sdk/bash_completion/adb.bash including vendor/cm/bash_completion/git.bash including vendor/cm/bash_completion/repo.bash Trying dependencies-only mode on a non-existing device tree? ============================================ PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=4.2.2 CM_VERSION=10.1-20130411-UNOFFICIAL-atlas40 TARGET_PRODUCT=cm_atlas40 TARGET_BUILD_VARIANT=userdebug TARGET_BUILD_TYPE=release TARGET_BUILD_APPS= TARGET_ARCH=arm TARGET_ARCH_VARIANT=armv7-a-neon HOST_ARCH=x86 HOST_OS=linux HOST_OS_EXTRA=Linux-3.9.0-rc5-ge24b0bfa+-x86_64-with-fedora-17-Beefy_Miracle HOST_BUILD_TYPE=release BUILD_ID=JDQ39 OUT_DIR=/wrk/safari/cvs/android/out ============================================ Edited April 11, 2013 by Otila
Guest vostinic Posted April 12, 2013 Report Posted April 12, 2013 Rom works well but i have one problem: the screen brightness which too weak and do not function settings.What is it ?
Guest KonstaT Posted April 12, 2013 Report Posted April 12, 2013 Maybe dir structure is messed up, I don't know anymore. but repo sync does not whine. Hmm, not sure why you have contents of .repo/manifests (default.xml, manifests for monthly builds, .git directory) on your workdir because you shouldn't. Maybe you've done repo init twice on different subdirs or something. I manually shoved some git repos mentioned at http://www.modaco.co...yanogenmod-10.1 to device/zte/atlas40 vendor/zte/atlas40 kernel/zte/zte-kernel-msm7x27a make started making, I go now sleeping and hopefully I have some breakfast when I wake up.. EDIT2: make: *** No rule to make target `/wrk/safari/cvs/android/out/target/product/atlas40/obj/STATIC_LIBRARIES/lib_driver_cmd_ath6kl_intermediates/export_includes', needed by `/wrk/safari/cvs/android/out/target/product/atlas40/obj/EXECUTABLES/hostapd_intermediates/import_includes'. Stop. Are you sure that you have synced all the repos in my custom manifest. Check that the respective directories are populated. You'll need to have this to build wifi. Just manually 'shoving' the device dirs won't work for CM10.1 (would work for CM10 though). It can also be something to do with your build environment. In that case you can just manually create out/target/product/atlas40/obj/STATIC_LIBRARIES/lib_driver_cmd_ath6kl_intermediates/export_includes directory. Rom works well but i have one problem: the screen brightness which too weak and do not function settings.What is it ? Hardware failure. Apparently you had this same issue with Aurora Borealis as well.
Guest Otila Posted April 12, 2013 Report Posted April 12, 2013 Hmm, not sure why you have contents of .repo/manifests (default.xml, manifests for monthly builds, .git directory) on your workdir because you shouldn't. Maybe you've done repo init twice on different subdirs or something. Are you sure that you have synced all the repos in my custom manifest. Check that the respective directories are populated. You'll need to have this to build wifi. Just manually 'shoving' the device dirs won't work for CM10.1 (would work for CM10 though). I nuked those default.xml&friends. Dirs in Local projects were missing. And I got some breakfast -rw-r--r-- 2 safari xuser 155556001 2013-04-12 12:10:30.577314375 +0300 out/target/product/atlas40/cm-10.1-20130412-UNOFFICIAL-atlas40.zip
Guest plantroon Posted April 12, 2013 Report Posted April 12, 2013 (edited) I admire your work KonstaT but haven't tried CM yet. I wanna play games, access wifi, accept calls, etc. It seems pretty unstable from what I read here. I know operating systems very well (personally using Archlinux) but I can't do any coding :( That's why I rely on you xD I've seen some good ROMs for huawei ascend g300 which has the same chipset as Blade 3. Why can't we suck more performance out of Blade 3? Antutu benchmark shows rly low scores on stock ROM even if I compare it to Xperia Tipo :( Another things I'd like to know are: How to root Blade 3 on Linux? Something about cyanogenmod: When there's an update with some fixes, do I have to download a new image or can I update it from the Android OS itself ? Does factory reset work? Edited April 12, 2013 by plantroon
Guest KonstaT Posted April 12, 2013 Report Posted April 12, 2013 I admire your work KonstaT but haven't tried CM yet. I wanna play games, access wifi, accept calls, etc. It seems pretty unstable from what I read here. I know operating systems very well (personally using Archlinux) but I can't do any coding :( That's why I rely on you xD I've seen some good ROMs for huawei ascend g300 which has the same chipset as Blade 3. Why can't we suck more performance out of Blade 3? Antutu benchmark shows rly low scores on stock ROM even if I compare it to Xperia Tipo :( Another things I'd like to know are: How to root Blade 3 on Linux? Something about cyanogenmod: When there's an update with some fixes, do I have to download a new image or can I update it from the Android OS itself ? Does factory reset work? CM10/CM10.1 is perfectly stable for everyday use. Message boards is just where all the sh*t piles up. You rarely get anything positive - it's all about the problems. You probably have the wrong device for gaming in the first place. I haven't had any performance issues and I've never been disapponted with the performance. Blade III performs just as I've expected. CM10/CM10.1 easily outperforms stock (by little in benchmarks and by far in regular use). You really can't compare benchmark results to other devices with similar (but not the same) hardware. E.g. we have 2,5 times amount pixels than what Tipo has. It's certainly going to stress GPU to a different level. And I really don't trust any benchmarks that someone else has made. Some people take it as a competition to get the highest score possible, when it just should be to measure performance as reliably as possible. Of course you're going to get a higher score if you overclock to the max and put in a class 10 sdcard. It's this sort of variables that should be ruled out in the first place. You root/install ClockWorkMod exactly the same way you would in Windows. Instead of playing around with drivers, you set udev rules for your device (/etc/udev/rules.d/51-android.rules). First line is for ZTE/Blade III and the second is for Google/fastboot. SUBSYSTEMS=="usb", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0306", MODE="0666", OWNER="username" #Blade III SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="d00d", MODE="0666", OWNER="username" #Fastboot[/CODE] Also place adb and fastboot in your $PATH. CyanogenMod OTA updates are only for official CM devices.
Guest Otila Posted April 12, 2013 Report Posted April 12, 2013 (edited) It seems pretty unstable from what I read here. Stock 4.0.4 was far from stable.. even the launcher crashed every now and then, and e.g. spelltower game rebooted the phone two times, now in CM10.1 it's smooth playing and no lags. Also, ZTE does not seem to care much about bug reports. Gallery now works in CM when I got back to fat on SD, it fixed itself automatically somehow(!). JIRA accepts bug reports for "Stable" and "M" releases only, so this thread is where bug reports go, or did I misunderstand something? Edited April 12, 2013 by Otila
Guest KonstaT Posted April 12, 2013 Report Posted April 12, 2013 JIRA accepts bug reports for "Stable" and "M" releases only, so this thread is where bug reports go, or did I misunderstand something? Yeah, and CM bug tracker is only for official CM builds/devices anyway. Bug reports, preferably with logs, are always welcome. This thread is also about open source development so that people can join in, contribute and fix any issues they come across themselves. ;)
Guest Otila Posted April 12, 2013 Report Posted April 12, 2013 Testing, testing.. Building perf was painless, I typed "make perf" ;-p "perf top" output https://docs.google....dit?usp=sharing versus top -m 5 PID PR CPU% S #THR VSS RSS PCY UID Name 18614 0 23% S 33 421096K 61444K fg u0_a219 com.natenai.glowhockey2 109 0 20% S 11 58744K 3892K fg system /system/bin/surfaceflinger 441 0 10% S 89 445452K 76432K fg system system_server 19014 0 2% R 1 1204K 528K root top 19011 0 1% D 1 0K 0K root kworker/u:2 binary https://docs.google....dit?usp=sharing sha3 = 6edceb385a4488777a4bc473b2ba791c42f5a46eafb1dd3f60a9413aaee1fc70fca6418d18df0e586b977ac903862d0e91a32fec0e6e833d1e282196f3700f5e
Guest Otila Posted April 12, 2013 Report Posted April 12, 2013 (edited) Where do I specify which files to exclude from cm-10.1-*-atlas40.zip generated by "make bacon" , like CMUpdater system/etc/terminfo .. my zip has 73 MiB more bloat inside than cm-10.1-20130329-KonstaKANG-atlas40.zip :blush: Edited April 12, 2013 by Otila
Guest thmnss Posted April 12, 2013 Report Posted April 12, 2013 I'm having problems with the proximity sensor on calls, when i make a call to someone the screen goes black and the screen stay black until the other person disconnects the call and I press the button "on/power" infinitely ... Does anybody else have this problem? Any solutions/ sugestions ?!? I'm using Zte Skate Acqua KonstaT If you could help, any way to solve the problem of the proximity sensor at Acqua?
Guest plantroon Posted April 13, 2013 Report Posted April 13, 2013 (edited) First, ubuntu couldn't find the device and then I got this: adb devices List of devices attached ???????????? no permissions Edited April 13, 2013 by plantroon
Guest KonstaT Posted April 13, 2013 Report Posted April 13, 2013 Where do I specify which files to exclude from cm-10.1-*-atlas40.zip generated by "make bacon" , like CMUpdater system/etc/terminfo .. my zip has 73 MiB more bloat inside than cm-10.1-20130329-KonstaKANG-atlas40.zip :blush: Does your build even boot btw? You clearly still haven't setup the manifests properly. CMUpdater, system/etc/terminfo, etc is already taken care of in the makefiles. Your build's system size should still be ~30mb larger than my latest release build. I haven't uploaded patches to remove LatimeIME dictionaries or Trebuchet wallpapers. Since the latest release I've also pushed a change that switched to full_phone and will include live wallpapers and more ringtones. KonstaT If you could help, any way to solve the problem of the proximity sensor at Acqua? Have you tried again with clean install? You can use e.g. AndroSensor to verify if you get a proper reading from the sensor. Here's the old work around that will 'calibrate' proximity sensor on every reboot. proxcal.zip First, ubuntu couldn't find the device and then I got this: adb devices List of devices attached ???????????? no permissions[/CODE] [CODE]sudo adb start-server ?
Guest H3nS Posted April 13, 2013 Report Posted April 13, 2013 Any news about the bluetooth if already anyone fix it??
Guest KonstaT Posted April 13, 2013 Report Posted April 13, 2013 Any news about the bluetooth if already anyone fix it?? There's no devices with Android 4.2 and working WCN2243 bluetooth that I know of.
Guest Otila Posted April 13, 2013 Report Posted April 13, 2013 Does your build even boot btw? You clearly still haven't setup the manifests properly. CMUpdater, system/etc/terminfo, etc is already taken care of in the makefiles. Your build's system size should still be ~30mb larger than my latest release build. I haven't uploaded patches to remove LatimeIME dictionaries or Trebuchet wallpapers. Since the latest release I've also pushed a change that switched to full_phone and will include live wallpapers and more ringtones. I am not yet mentally prepared to run this =) But it should Just Work™ if I install cm-10.1-20130412-UNOFFICIAL-atlas40.zip in cwm6027 and reboot? I really have no idea what else I would do to setup manifests properly besides those things previously mentioned. $ l .repo/manifests .repo .repo/local_manifests/ .repo: total 52 drwxr-xr-x 7 safari xuser 4096 2013-04-13 14:47:07.979715169 +0300 . drwxr-xr-x 30 safari xuser 4096 2013-04-12 22:48:50.490005800 +0300 .. drwxr-xr-x 2 safari xuser 62 2013-04-11 22:56:50.234839319 +0300 local_manifests drwxr-xr-x 3 safari xuser 116 2013-04-13 14:47:24.837765746 +0300 manifests drwxr-xr-x 9 safari xuser 4096 2013-04-07 17:24:53.768429537 +0300 manifests.git lrwxrwxrwx 1 safari xuser 21 2013-04-07 17:02:31.727377884 +0300 manifest.xml -> manifests/default.xml -rw-r--r-- 1 safari xuser 7477 2013-04-13 14:51:10.006501020 +0300 project.list drwxr-xr-x 27 safari xuser 4096 2013-04-07 21:19:35.039765368 +0300 projects drwxr-xr-x 7 safari xuser 4096 2013-04-07 19:21:28.245377524 +0300 repo -rw-r--r-- 1 safari xuser 23676 2013-04-13 14:51:09.052497829 +0300 .repopickle_fetchtimes .repo/local_manifests/: total 12 drwxr-xr-x 2 safari xuser 62 2013-04-11 22:56:50.234839319 +0300 . drwxr-xr-x 7 safari xuser 4096 2013-04-13 14:47:07.979715169 +0300 .. -rw-r--r-- 1 safari xuser 1783 2013-04-11 21:21:56.793484888 +0300 local_manifest.xml -rw-r--r-- 1 safari xuser 393 2013-04-11 21:22:00.083497020 +0300 manifest_zte_atlas40.xml .repo/manifests: total 156 drwxr-xr-x 3 safari xuser 116 2013-04-13 14:47:24.837765746 +0300 . drwxr-xr-x 7 safari xuser 4096 2013-04-13 14:47:07.979715169 +0300 .. -rw-r--r-- 1 safari xuser 33362 2013-04-07 17:02:31.671377673 +0300 cm-10.1-M1.xml -rw-r--r-- 1 safari xuser 33804 2013-04-07 17:02:31.671377673 +0300 cm-10.1-M2.xml -rw-r--r-- 1 safari xuser 33786 2013-04-09 16:54:58.369146931 +0300 cm-10.1-M3.xml -rw-r--r-- 1 safari xuser 33868 2013-04-11 20:59:07.336258483 +0300 default.xml drwxr-xr-x 2 safari xuser 4096 2013-04-11 20:59:07.336258483 +0300 .git -rw-r--r-- 1 safari xuser 1779 2013-04-07 17:02:31.671377673 +0300 README.mkdn also, there's .repo/repo/repo whose path isn't added to $PATH when running build/envsetup.sh , is it expected that people use https://dl-ssl.googl...e/git-repo/repo or .repo/repo/repo ? Yes, I also tried "repo sync" using executable .repo/repo/repo ..
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now