How about without gapps? Works fine here on ace after that commit.
DS is my daily driver so without gapps the phone is like a brick.
I'll test without gapps and without bootanimation. Too bad that booting takes like an hour.
How about without gapps? Works fine here on ace after that commit.
I didn't mean you have to run it like that for eternity. I don't have the device so I can't perform any tests on saga myself thus the request for a simple test I'd otherwise do myself.DS is my daily driver so without gapps the phone is like a brick.
I'll test without gapps and without bootanimation. Too bad that booting takes like an hour.
I'm aware and I don't have a problem testing.I didn't mean you have to run it like that for eternity. I don't have the device so I can't perform any tests on saga myself thus the request for a simple test I'd otherwise do myself.
Looks like the full resolution boot animation is still being copied over instead of the half resolution one. I didn't verify that the build flag actually does what it should do. My ace probably only works because ART cache creation was already successful once and I upgraded on top of that and it didn't recreate the whole cache so the thing that causes the issue is fixed until it does. You can probably put the boot animation back too once it has successfully booted up once but full resolution boot animation will still slow down the boot due to being very resource hungry which causes ART cache creation to fail too thus causing the low memory warning. I know it doesn't make much sense that these things are related but something goes haywire because cache isn't created properly. Anyways, I will look into really including the half resolution version of boot animation.I'm aware and I don't have a problem testing.
edit: Even without gapps.
edit2: I removed bootanimation and the phone flies. (with gapps) It's AWESOME.
btw. There is some bootanimation, it is an "android" word right in the middle with some shades going on.
edit3: HOLY ****!
Looks like the full resolution boot animation is still being copied over instead of the half resolution one. I didn't verify that the build flag actually does what it should do. My ace probably only works because ART cache creation was already successful once and I upgraded on top of that and it didn't recreate the whole cache so the thing that causes the issue is fixed until it does. You can probably put the boot animation back too once it has successfully booted up once but full resolution boot animation will still slow down the boot due to being very resource hungry which causes ART cache creation to fail too thus causing the low memory warning. I know it doesn't make much sense that these things are related but something goes haywire because cache isn't created properly. Anyways, I will look into really including the half resolution version of boot animation.
I'm stuck in a bootloop but cant seem to access recovery or fastboot with vol keys, it just goes to boot anim, anyone know how to help, I'm pretty knowledgeable at this sort of thing but I'm stumped if I cant find a way into recovery or fastboot.
I think its bootlooped due to not fastbooting the boot.img. Anyone I can fastboot that without getting to fastboot?
No fix.Does anyone find a way how to set profile picture? When I'm trying to open settings for Owner user I'm getting message "The contact doesn't exist".
This error also seems to be happen on Nexus 6 http://xdaforums.com/nexus-6/develo...ndroid-5-1-t3066269/post59772529#post59772529
Cm browser is buggy as hell.Hi everybody! I have an issue with some apps in build of 17 apr. For instance, CM browser works about 20-30 seconds, freezes for 1-2 sec and shuts down! It looks like not enought memory. (Other browser works fine) Same thing with other few apps!
I flashed 12.1 + gapps 5.1 once with full wipe ( deleted bootanimation zip before ). And I didn't change any settings. Maybe it can be fixed by updating next nightly? Or I should try to reflash it first
Thanks a lot for a 12.1! :good:
P.S. Same issue after update 20 apr(((
Take a log.
I have logcats of two other apps with same issue:Cm browser is buggy as hell.
It crashes here too.
The boot animation should be fixed on these builds.
Thanks, I will try.No fix.
You can install google+ and sync your profile picture from there
pull of the battery...Stuck at HTC logo after clean flash.
I am boot unlocked and s-off.
Flashing the ROM after cleaning my stock ROM. Now after flashing i got stable HTC LOGO...
Do i have to worry about kernel now? Do i have to change it ? if so please provide me the download link
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
fastboot flash boot boot.img
mkdir cm12.1
cd cm12.1/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-12.1/local_manifest.xml -O .repo/local_manifests/local_manifest.xml
repo sync
. build/envsetup.sh
lunch cm_saga-userdebug
mka bacon
I'm quite busy in my life right now and will likely be so for a while. I can't say anything for the others because we don't really work that tightly together - people just do things they want to do when they want to do them. I'm personally mainly interested in fixing WebView / RenderThread crash for the time being but it's not progressing very fast due to the aforementioned life situation among other things. I'm not making a stress source out of this project though so things progress at their own pace like it has been the past 3 years I've been involved with ace community. I'm sorry for any possible misunderstandings if this hasn't been clear.Hi guys, how's development going? Seems a bit slow now
Was just wondering if my previous logcats are useful? Or applications crashes "don't matter" (in the sense you'll only look into OS features - i.e. wifi, calls, sensors...)?
Keep up the great work :good:
Yeah, I guess it's possible but if we ask whether it's possible that I can make them work, that's a completely different story.Is it theoretically possible to use the open source freedreno drivers? They support OpenGL ES 2.0 on Adreno 205. If so, they might resolve some graphical issues (if there are any left while using the new adreno blobs).