yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Gurriak:
Can't Acces to BlackRose

I'm trying to run BlackRose for resize the partitions, but BlackRose doesn't detect my N1. I already tried in linux, windows (xp&7) and even with htc sync and nothing works.

The curious thing is that originally i was running the evervolv ROM with 260/10 system/cache and there BlackRose works fine. But when i installed the CM11 ROM over size partitions of 260/10 wasn't possible for BlackRose to detect my N1. But i want to save space, so i reinstalled the evervolv ROM and resize the partitions to 230/10 system/cache for install the CM11 ROM but now i'm stuck with a partitions of 230/10 system/cache because CM11 ROM still doesn't detect my N1. I already tried installing the CARBON ROM but there BlackRose start detecting the N1 and after a few seconds crash. I even attempted to install CM7.2 that was my base ROM but for strange reason doesn't install it.

Another thing that presents problems are the scripts (both) of mount2sd, when i flashed it the phone doesn't boot and i have to flash everything again. I even tried download it from Google Play, but when i install the script the same problem rise again. At this point is a minor problem, the thing that really worries me is to get stuck in a size partitions of 230/10 because this disable me to try other ROMS or upgrades of this, if its size changes.

Any ideas how to solve this ? Exist a method to run BlackRose in hboot mode for resize the partitions ? I feel helpless.

I don't want to appear like annoying person the ROM is awesome and when i flashed the keyboard for foreign languages the gesture typing works smooth (i'm a native spanish speaker).

Regards.
[Nexus One Android Development] Gurriak:
I solved my problem. I could flash my base ROM CM 7.2 and resize the partitions with BlackRose. But anyone else had the same problem flashing the ROMS of CM11 and CARBON ? i don't know if is a bug or it's a problem that only presents to me.

See you around.
[Nexus One Android Development] parkedraccoon:
It may be some sort of incompatibility with the old ADB binaries included in BlackRose. Not really sure. It's possible to bypass the adb stuff and run BlackRose from bootloader. If you're still having ext problems, check out the m2sd aroma script in my Carbon thread.

Anyways!

New update posted. Download link is in first post. CM sources have been updated; the theme engine has been updated, and force high-end graphics is available, but you must enable dev settings. It is in performance settings.
[Nexus One Android Development] thunder2k:
Thanks for the update! Can we just flash over the February version, just with a caches wipe? Do we need to reflash the mountToSd as well? Thanks again, and happy Easter ;)

Sent from my Nexus⁴
[Nexus One Android Development] kostka:
Hi, thanks for the update. But I can't toggle Wi-Fi on after switching it off. Have to reboot. Is there any workaround on this? Thanks.
[Nexus One Android Development] BellaMay95:
With this new release, I can't install the Xposed framework. If I enable the framework, when I reboot everything crashes, from the android.media thing to the keyboard, and the phone, and the system.ui....when it boots up it goes through the "optimizing app _ out of _" thing, and then it crashes after that. Even flashing the disabler .zip that is on the SD card won't make it boot up again.
[Nexus One Android Development] fc_themaster:
I followed all the instructions but ART doesn't work for me... always bootloop.
[Nexus One Android Development] Gurriak:
My exact problem with ext was when i tried to install, or flash it, the m2sd (both scripts normal and aroma) the phone didn't boot and freeze. Well, i could to workaround this and i could flash both, but now my problem is that aroma doesn't do anything and the normal script says that the script couldn't install because my phone has the s-on. So i go to recovery mode and disable verification check in the recovery mode on toggle signature verification but this also didn't work, any idea how to solve it ?

The new ROM works much better than older one, the only issue is with Wi-Fi that some times frezees when i try to activate it, and the problem with blackrose remains.

Tschüss
[Nexus One Android Development] kostka:
Exactly the same problem I have.. something wrong with the Wi-Fi. Please fix this.. thank you :)
[Nexus One Android Development] Gurriak:
I could solve the issue with ext and m2sd, after a deep research and many tests, i solve it making the partition with gparted. If i try to do the partitioning using recovery mode or minitool partition wizard both doesn't create the partitioning table in the right way, you must do it with Gparted or the linux partition tool you choose. The format that works for me is ext4 but must works with ext2 too. I can see that all my problems with ext and m2sd are very common for many users, and now i can conclude that this is the way to fix it.

Until now the Wi-Fi problems doesn't present anymore after a clean installation and formatting with Gparted. The other problem with blackrose remains.

I post every problem i face hoping my experience could help others.

Thank you for your great work.
[Nexus One Android Development] kostka:
On mine, I have everything work well again after doing wipe cache+dalvik on 4EXT recovery
[Nexus One Android Development] thunder2k:
For me is working fine, but I can't move data 2 ext, otherwise it doesn't work, but not in the way you described, it just says me that the framework is not active.

Sent from my Nexus⁴
[Nexus One Android Development] phoeagon:
Yes. XPrivacy does work

---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------

Yeah I once ran into exactly the same problem. Then I go to recovery and wipe cache and data again (w/ xposed installed)

---------- Post added at 11:08 PM ---------- Previous post was at 11:07 PM ----------

Confirmed. Also, is a Pdroid integration possible?
[Nexus One Android Development] BellaMay95:
Oh, and another bug I've been experiencing. Most of the time this happens right after I unlock the screen, but it will freeze for several seconds and then re-lock itself and I have to unlock the screen again. If I turn the screen off while it is frozen like that it will take a few minutes to turn back on. It has been confined to when I turn the screen on, but it just happened to me when I've been using it for a while with the screen on, it just randomly froze and locked itself. Any idea why this is happening? I haven't re-formatted my SD card in a while, could that be an issue?
[Nexus One Android Development] parkedraccoon:
Not enough /system space. This lack of /system space may also be why people are having some xposed problems - if it doesn't fully install properly because of not enough /system space there may be problems.

Sounds like a SystemUI crash. Maybe xpsoed modules are causing it? It's perfectly possible that it's not an xposed module problem, though, but I'd need a log to look at things.

As for the wifi bug that people seem to be having, I've had it on previous versions of the rom (when wifi turns on for initial Google sign-in) so I don't think it's new to this version. However, even if it is, I don't really have the know-how to really fix it, unless it's simple.
[Nexus One Android Development] phoeagon:
Unlikely. I have a 270/10 system and it still randomly crashes after reboots. Maybe like one out of 20 reboots results in the "updating apps" then constant crash loop. Always resolved with a recovery wipe /cache.

I have 270/10 blackrose, mounts2sd moved application, cache, dalvik-cache but not system apps or application data.

---------- Post added at 04:36 PM ---------- Previous post was at 04:33 PM ----------

Also the ROM seems to randomly mute your sound after waking up from lockscreen. Usually when I plug a headphone in and wake it up, no audio would go to the headphone or speaker. A workaround would be ejecting the headphone, playing music via speaker, then quickly inserting the headphone back-in. After this combo and a couple of awkward seconds with music from your speaker, the audio correctly routes to my headphone.
[Nexus One Android Development] BellaMay95:
Mmm...I don't have Xposed installed at all, not even the installer, because the phone won't ever boot up if I try that. My system partition is 250, so I should be good there. I think I'm going to re-format my SD card and re-do the whole thing to see if that has anything to do with it, because everything worked perfectly until the last release in April, and I doubt just that minor update broke everything. As for a log, I'm going to have to read up on how to do that because I haven't taken one before. :)
[Nexus One Android Development] rabies876:
Pleasant day to all the happy people.

Mile stone 6 has been released to day so the next update for us will be great as well.

Good day.
[Nexus One Android Development] BellaMay95:
Any chance that links to old versions are available? With the latest version (4/18), if I try to activate the Xposed framework everything crashes on reboot and I can't get in to my phone. Flashing the Xposed disabler .zip does nothing for me. If someone could post a link to the previous version of the ROM before that update I'd much appreciate it. :) And, of course, if my problem could be figured out that'd be great as well. :)
[Nexus One Android Development] parkedraccoon:
Try a slightly larger hboot. CM fits much more snugly into the 220 mb than Carbon, and Xposed may be not completely fitting in and causing problems.
[Nexus One Android Development] BellaMay95:
I have a 290/16 set-up...I think that's probably enough space? :P
[Nexus One Android Development] parkedraccoon:
Try and get a log. I can't seem to replicate the problem for me; I am unable to run with ext at the moment though, so that may be what's causing problems.

Here are some older versions:

http://d-h.st/search?search_by=2&search_for=parkedraccoon
[Nexus One Android Development] BellaMay95:
Thanks for the link. I just got the N1 back to normal today after 48 hours of trial-and-error with other stuff, so I'd rather not touch it again at the moment (it's the phone I use on a daily basis), perhaps in a week or so I'll be brave enough to read up on how to take a log and mess with it again. :)
[Nexus One Android Development] mauriciognr:
Is the "slow motion" problem solved in the camera? Las time camera was laggy as hell.
[Nexus One Android Development] parkedraccoon:
Camera's not gonna be fixed until k3 comes out.

Anyways, update time! As usual link is in the first post. There haven't been too many CM source updates - mainly some more updates to their new theme engine and such.
[Nexus One Android Development] BellaMay95:
Any chance wi-fi calling would be available on a JB or KK rom? Last package I see is only available for CM7...
[Nexus One Android Development] thunder2k:
Hi guys, I'm stuck at X logo after flashing this update + mount2sd + banks gapps 6_2 minimal in this order. I noticed that there are 0 Mb left on system partition. What about you? Thanks a lot!

Sent from my Nexus⁴
[Nexus One Android Development] mauriciognr:
ROM already include Play Store. No need for external gapps

---------- Post added at 07:03 AM ---------- Previous post was at 07:01 AM ----------

Ive installed the last update (Jun 14) and is awesome.Im using link2sd plus to move apps and data to ext partition, so far everything is working ok, i mean no new bugs at5 least. Cant wait for the next update 4.4.4 CM 11 M8 maybe?
[Nexus One Android Development] thunder2k:
Thanks for the update!

Yesterday evening I tried to flash without GAPPS and it worked flawlessly!!

Any news from the OP for the 4.4.4 update?
[Nexus One Android Development] 1of16:
an update would be awesome!
[Nexus One Android Development] parkedraccoon:
On a trip this weekend I'll get it to you when I get back.
[Nexus One Android Development] wanxu:
When I flashed ROM + Mount2SD (both with CWM one in that order) I had a bootloop.

Then I flashed ROM (changed to TWRP) and installed Mount2SD from google play and now it works without having to flash it from recovery. I think you should tell it in the first page, in case someone has the same problem as me.
[Nexus One Android Development] mauriciognr:
Status abr and battery issues.

With the high end graphics option enabled in performance menu my status bar still black. Only shows transparent in lock screen. Im using ADW launcher if that matters.

[IMG="Lockscreen, desktop and facebook app status bars."]http://i974.photobucket.com/albums/ae228/mauriciognr/Screenshot_2014-07-11-22-02-03_zps59c69a07.png[/IMG]

Another weird thing i found was a huge battery drain, battery goes down really fast, i mean REALLY fast like 15% per hour with light use (BBM and whatsapp). All this is compared with CM7.2 battery life.

Any ideas? thanks guys

--------------------------------------------------------------------------------------------------------

My statusbar problem got solved with Nova Launcher. Someone else has battery drain or is just me?

[IMG="Nova Launcher desktop"]http://i974.photobucket.com/albums/ae228/mauriciognr/Screenshot_2014-07-12-08-48-441_zps041bf367.png[/IMG]
[Nexus One Android Development] 1of16:
first of all, this is a low power device, so the high end graphics option is unchecked for a reason and kinda useless anyways

second...I see many possible battery drainers: twitter, instagram, fb, bbm. maybe take a look in the battery settings?

I bet one of them is the reason or the google play services, cause there are (again) buggy and waking the device up for no reason. deactivate the wake-up options in the privacy settings for the google play services.
[Nexus One Android Development] mauriciognr:
Battery drain is not high ends graphics related, it was there way before i enabled them. i will check on battery settings. Thanks
[Nexus One Android Development] parkedraccoon:
Well folks, as promised...

New update!

cm source updated - 4.4.4 and other updates

native USB tethering fixed

bionic optimizations - switched to scorpion

CM seems to have changed how they detect Google services in setup, so account login will not work in setup wizard. Just enter play store once you do setup and it will work fine.

Link is in first post, as always. Later on I'll get some updated stuff for ART. I'm expecting a new mobo for my laptop so there may be some delay while I deal with that.
[Nexus One Android Development] Theericgames:
One Question

I've been using this ROM for a few days, in fact, a few days ago BEFORE the new update.

Actually, only use this ROM because you can apply the theme ANDROID L.

Anyway, my question is: Can I update my ROM without deleting my current applications?

[SIZE="3"]Ah! By the way, here are some screenshots of the theme ANDROID L.[/SIZE]
[Nexus One Android Development] parkedraccoon:
It may work as long as you reflash your ext script, but backup your important data first. I cannot guarantee that it will work.

In other news, I've been working on ART. I'm trying to make the zip also enable art initially, so that you won't need to go through the time-consuming process of switching to ART and rebuilding the ART-cache.
[Nexus One Android Development] Theericgames:
Hmm....

Could you explain in detail how I do it? It seems that what I need details ...
[Nexus One Android Development] parkedraccoon:
If you wish to retain data, do not wipe data, flash the new rom, then flash ext script, and reboot, and it should be fine.

ART instructions are now in the 2nd post. They have been updated.
[Nexus One Android Development] mauriciognr:
Silly question, does ART worth the shot in this device? I've read that the Android L ART is way different and faster than the KitKat one, dont get me wrong ill flash that **** jajaja but maybe you can educate me a little. thanks for your work man, youre awesome
[Nexus One Android Development] parkedraccoon:
I've tried it a bit, the difference wasn't too big. Takes up more space, too. People were asking for it previously so I made it available. This was simply an update.
[Nexus One Android Development] Hyflex:
I'm unable to install this for some reason, every time I get to the stage of changing the hboot to 220 it fails...

If I just try to install using twrp it fails to install the rom... :/

Anyone able to help? :S
[Nexus One Android Development] Obsy:
Blackrose doesn´t like TWRP... try 4Ext
[Nexus One Android Development] 1of16:
awesome work as always...but i got a problem:

it seems not to be possible to install cm11_071514_LatinIME.zip?

I got a 250mb partition, but TWRP 2.6 says "E:Error excuting updater binary in zip '....'"

any idea?
[Nexus One Android Development] Theericgames:
ART...

In truth, I have tried everything to use ART, but every time I flash the zip my recovery says ... FAILED

What am I doing wrong?
[Nexus One Android Development] Hyflex:
It still failed, I've tried on TWRP, CWM and 4EXT and they all show the following error message when I try and set it to 220mb

I have Blackrose installed already from like a year ago but I have no idea if it's the correct version and partition size I have no idea about, I am able to install CM7 but I want to install CM11 :(

Any help would be appreciated
[Nexus One Android Development] parkedraccoon:
It says to put "resize" into the input, but you put "220". ;) Also, on your bootloader screen it will show your current size on the second line.

(This reply is for both of you.) TWRP seems to hate a lot of stuff. I had the same problem with Mounts2SD. It works fine for me in CWM.
[Nexus One Android Development] Obsy:
Like [MENTION=4861589]parkedraccoon[/MENTION] said you must type

resize

and then you'll be asked for size of partition... So, good luck!
[Nexus One Android Development] Theericgames:
...really?

LOL

If necessary, I will have to install CWM ... xD
[Nexus One Android Development] rabies876:
I don't have any issue at all with Carbon

Nexus One using Carbon ROM.
[Nexus One Android Development] maumaumau:
could you update the gapps-link in the second post?

thx
[Nexus One Android Development] Kotaless:
I recommend Bank's minimal Gapps. You can find here: http://xdaforums.com/google-nexus-5/themes-apps/standard-minimal-gapps-t2012857
[Nexus One Android Development] joeyhewitt:
Build instructions

parkedraccoon, great work on this, and thank you! I'm wondering if you can share some more information on building this for ourselves. I've pieced together a build from CM11 stable repos (branch stable/cm-11.0 on Github) + your Torch, Settings, frameworks-base, and fork of Evervolv's device directory + Evervolv kernel and its dependencies.

My build boots to the homescreen, but crashes within a minute or two due to graphics issues. So, before I spend too much time on that, I wanted to check if you have any build instructions, unpublished patches, build manifests, etc., that might help me get closer to your build. I understand some things, like slimming, might be too tedious to describe, so you can leave that out. Any help is appreciated. Thanks!

P.S. If it makes a difference to anyone, here's some more details on my crash:

I get these lines in logcat:

E/Surface ( 1675): dequeueBuffer: error duping fence: 24
W/Adreno200-GSL( 1675): <gsl_ldd_control:226>: ioctl code 0xc0140933 (IOCTL_KGSL_TIMESTAMP_EVENT) failed: errno 22 Invalid argument
W/Adreno200-EGLSUB( 1675): <ResolveFence:2912>: gsl_add_fence_event failed
W/Adreno200-EGL( 1675): <eglDupNativeFenceFDANDROID:5642>: EGL_BAD_PARAMETER
E/GLConsumer( 1675): [com.android.settings/com.android.settings.Settings] syncForReleaseLocked: error dup'ing native fence fd: 0x3000
W/SurfaceFlinger( 1675): failed to dup layer fence, skipping sync: 24

Then repeating these while the screen is frozen:

E/BufferQueue( 1675): [com.android.settings/com.android.settings.Settings] queueBuffer: fence is NULL
E/Surface ( 2095): queueBuffer: error queuing buffer to SurfaceTexture, -22
W/Adreno200-EGLSUB( 2095): <SwapBuffers:1119>: failed to queueBuffer
W/Adreno200-EGL( 2095): <eglSwapBuffers:3529>: EGL_BAD_SURFACE

Eventually it sort of soft-reboots (I think system_server gets restarted), but it will crash again. There is also a red rectangle around the screen that appears sometimes. I see references on Google; apparently it is a warning that an app is taking too long to draw a frame. I won't worry about it too much until/unless I fix the crash.
[Nexus One Android Development] parkedraccoon:
I do have a couple commits I cherry pick before each build.

https://github.com/csytracy/android...mmit/f3e32aa9b524e1f515e64ddf4314ef63ef8c16dd

https://github.com/csytracy/android...mmit/afe8dc5f0e766076e825cc660c86e8fca3680749

revert: https://github.com/CyanogenMod/andr...mmit/4c48963517f1569ce909ad2f8a4b7a675de5a1f6

I have also attached my local manifest. The graphical error is due some commits in frameworks_native that spezi77 has done a good job of keeping track of.

For slimming, my process is based off of this thread. I don't delete all the files that are described there, but I go through the large system APKs one by one, deleting all drawables larger than hdpi, and also deleting languages except for English in LatinIME. I also delete all 3 art files. (2 in lib, one in framework)

To fix gesture typing, make sure to use the same libjni_latinime as in my roms.

I don't update my repos unless I'm building a rom. Make sure you keep track of that. PM me/reply if you have any more questions.

Good luck!
[Nexus One Android Development] joeyhewitt:
Awesome, thanks again! spezi77's reverted commits seem to have fixed the graphics crash. The csytracy telephony patch also fixed the GSM issue, which I didn't notice before. I think I brought in a few changes from your local manifest, but I had most of it already.

For the iproute2 error, I cherry-picked this Qualcomm kernel commit instead of reverting the one in iproute2. It's probably riskier than reverting in iproute2 though, since I don't really know what this stuff is and it's in the kernel. I stumbled on the commit by Googling the compile error we get without the iproute2 revert. It's possible that more of their commits should be merged to get the full effect of whatever this flow stuff is. I may go with the iproute2 revert instead. I haven't seen any kernel crashes, but I am wondering if my battery life when using wifi is worse than it should be.

Since you said you go through system APK's one by one, you may want to use instead "PRODUCT_AAPT_CONFIG := normal hdpi" at the end of cm.mk. I believe this has the same end result. (Its initial value comes from some inherited makefile that includes xhdpi and xxhdpi.) IIRC it dropped about 10MB from my build, without having to do anything outside the build process.

I also set PRODUCT_LOCALES := en_US, which slims a lot, but probably can't be so restrictive for a general release. Surprisingly LatinIME is still huge at 13MB, but I'm avoiding any changes that can't be fit into the normal build process, and don't need the space for now.
[Nexus One Android Development] parkedraccoon:
Interesting. I may have to look into that more.

Before I tried this simply by deleting the xhdpi and xxhdpi from other makefiles. Maybe I did it wrong, I'll have to try it again next round of builds.

I'm guessing that removes some system fonts? I'd be interested to see how it does its slimming.