[ROM][JB]CM10 with Linaro toolchain based on Quarx repo

[Maarren]

Guys, so far this is very unstable.

Just had a reboot during an alarm, high battery drain, not good. Had to clear cache and dalvik to reboot.

Use with caution!

Curious about your experience.

Sent from my MB526 using Tapatalk 2

Red lens defy. (with normal voltages)

Installed fine, performance was fine. ROM got stuck after a few hours and could not boot anymore. Reinstalled quarx rom, but then noticed something happened to data partition. (all my setting were reset, but apps were still there). a recovery of previous data partition fixed it.

 

[wskelly]

I'm going to pull the build from the site; I just had a data partition issue also, not worth messing with it.

If you have it installed and everything is fine, I recommend you revert to something else asap...

 

[slph]

Installed, everything was fine (JellyX kernel really feels better at interface response).
Phone self rebooted and never boot after receiving sms
Clean caches and switching cpu settings didn't help, so I replaced zImage to 18.11 again.

For a temporary solution: wskelly build + kernel from 18.11 Quarx build - working correct for me, except led icon on charge, it blinking red, nothing serious.

 

[wskelly]

Removed kernel optimizations from Kayant and went back to plain gcc for the kernel build. I am not sure if optimizations are to blame or if the Linaro gcc is to blame for the instability but the latest version (4-Jan-2013) has so far been stable at least overnight and didn't experience anything unusual yet. I did wipe data to get it to boot, I am not sure of the reason for this but Blechd0se mentioned in the JellyX thread that this might be necessary. There is a 'kernel installation prep' script that can be flashed, I didn't try this but it seems there should be a *reason* to have to wipe data -- like a specific file or group of files that causes the issue. Maybe this kernel prep script helps with that. It comes from this thread here on XDA.

Now I will try to bring back Linaro for the kernel but won't post until I think it is stable. For now I'm using the one posted and no issues since last night.

Summary: Jan-4-2013 --> JellyX (compiled with vanilla gcc) + Quarx repo (compiled with Linaro 4.7)

 

[wskelly]

Success with Linaro 4.6 + JellyX

Holy crap.

@Kayant if you read this, the solution to Linaro 4.6+ with the kernel is here. I've just made the commit for this here. My android manifest includes the Linaro 4.6 toolchain as of last night, but you need to check out linaro_4_6_2 of my jordan-common repo, as well as make a symlink for the toolchain like so:

[email protected] ~/Projects/cm/prebuilt/linux-x86/toolchain $ ls -la
total 24
drwxr-xr-x  4 wskellenger wskellenger 4096 Jan  5 00:15 .
drwxr-xr-x  5 wskellenger wskellenger 4096 Dec  7 00:45 ..
drwxr-xr-x 11 wskellenger wskellenger 4096 Dec  7 00:45 arm-eabi-4.4.3
drwxr-xr-x  8 wskellenger wskellenger 4096 Dec  7 00:46 arm-eabi-4.5.4-linaro
lrwxrwxrwx  1 wskellenger wskellenger   93 Jan  5 00:15 arm-eabi-4.6.2-linaro -> /home/wskellenger/Projects/cm/prebuilts/gcc/linux-x86/arm/android-toolchain-eabi-linaro-4.6.2
lrwxrwxrwx  1 wskellenger wskellenger   91 Jan  5 00:10 arm-eabi-4.7-linaro -> /home/wskellenger/Projects/cm/prebuilts/gcc/linux-x86/arm/android-toolchain-eabi-linaro-4.7
[email protected] ~/Projects/cm/prebuilt/linux-x86/toolchain $

Prior to this commit I would get bootloops with Linaro 4.6 and 4.7 trying to boot. This time I just flashed it on top of the 4-Jan build, no data wipe, and it booted up successfully. Nothing weird yet. I'm headed out on some errands so we'll see how it goes today as far as stability.

Note this build is *not* posted yet.

 

[slph]

Latest build is good for me (but installed with full wipe, cleaining script, wiping caches didn't help me)
If you included this commit to 5.01.13 kernel, then, I can say it can't solve battery drain for green lense - min 2% per hour when phone untouched (18.11 twice lower, 0.5-1% more).

Here should be something, what included in kernel after 18.11... not sure what can be different with camera color, but drain reports only from people who have Defy with green lense.

Update: After manual reboot, phone got black screen and boot after wipe caches

 

[wskelly]

After literally HOURS of messing around yesterday, going to bed at 3a and getting up with my kids early this morning, here are the results:

Build JellyX kernel with:

Linaro gcc 4.5: boots, unstable
Linaro gcc 4.6: boots, no network available
Linaro gcc 4.7: bootloop
Gnu gcc 4.4: boots, everything works, stable

Quarx was (and maybe still is?) using Linaro 4.5 for the kernel, but his kernel doesn't have all of the tweaks that JellyX from user Blechd0se has.

So I've gone back to gcc for the JellyX kernel, they send to play nicely together. Still using Linaro 4.7 for everything else. New build just uploaded:

*Gcc for JellyX kernel
*Linaro 4.7 for everything else
*Put optimizations from Kayant back in
*Added a feature in recovery that will wipe cache and Dalvik automatically after updating from zip (I hate doing this manually). Default this feature is off but you will see "toggle cache + dalvik wipe" (something like that) next to "toggle signature verification" right before you choose zip from SD. (Of course you won't see this until after you flash and reboot.)

Carlos: just bought my wife a larger sd card so I will format her old one to NTFS and try it.

Quadrant with this build:

Sent from my MB526 using Tapatalk 2

 

[casouzaj]

Thanks a ton, wskelly, for keeping attempting to solve the NTFS card issue! Eagerly waiting for a future release of yours addressing it! As Quarx's 11/17 handles my NTFS card just flawlessly, meaning that JB had the necessary patches/corrections identified last March under ICS, I suppose his newer builds (from 11/18 onwards) might have picked a different branch whilst synchronizing CM updates. I'd like to know your oppinion on this idea, if any and possible.

Thanks again, anyway!

 

[Fight4Music]

@wskelly, looks nice , i will try your latest Build, but which Version of jellyx should i use?

Gesendet von meinem MB526 mit Tapatalk 2

 

[wskelly]

@fight, JellyX is already bundled with the ROM. If you are already using JellyX, hopefully you don't need to wipe data. Make sure you have a backup.

Sent from my MB526 using Tapatalk 2

 

[Fight4Music]

@fight, JellyX is already bundled with the ROM. If you are already using JellyX, hopefully you don't need to wipe data. Make sure you have a backup.

Sent from my MB526 using Tapatalk 2

I used several jellyx version's, at last 30.12, but with it, i stucked in a bootloop (with quarx latest build).

So, TB is my best friend .

I will try and report back

Gesendet von meinem MB526 mit Tapatalk 2

 

[niksy+]

It's because Quarx re-enabled trace in the 30.12 and 31.12 builds, while the JellyX kernel has it removed. I think Kelly mentioned somewhere that he disabled trace...hence the two (CM10+JellyX) work fine together, again!

WSKelly, could you please run AnTuTu, as well? I got ~3570 max so far (on 23/12 Quarx's build) (clocked at 1.1ghz, deadline as i/o scheduler)

 

[wskelly]

Here is my Antutu score @ 1000 MHz. I didn't change anything else, just watching TV with the kids, downloaded and ran the app (cool app btw, I'm going to get rid of quadrant now)

Sent from my MB526 using Tapatalk 2

 

[wskelly]

Thanks a ton, wskelly, for keeping attempting to solve the NTFS card issue! Eagerly waiting for a future release of yours addressing it! As Quarx's 11/17 handles my NTFS card just flawlessly, meaning that JB had the necessary patches/corrections identified last March under ICS, I suppose his newer builds (from 11/18 onwards) might have picked a different branch whilst synchronizing CM updates. I'd like to know your oppinion on this idea, if any and possible.

Thanks again, anyway!

Carlos, I got the issue about five minutes after putting the card in the phone. But it is not really clear except in the logcat. Here is what is happening to me:

1. Took picture. System behaves as if the photo was taken, no error.
2. Tried to change ringtone. I am able to select the ringtone from the SD card with ES File Explorer, but then the ringtone immediately changes to "Silent"
3. Open gallery. Gallery shows nothing (but I did not copy all of my photos from my old (working fine) card so right now I've got no photos at all.
4. I checked logcat and I see the MediaProvider error you've mentioned many times.

I have a hard time thinking this is a kernel issue because ES File Explorer can access the files fine. I think this must be a base Android issue like with MediaProvider or one of the lower level parts of Android that provide the card information to applications. I don't have a good understanding of how it all fits together but now I can easily reproduce and debug the issue here.

From what I see Quarx just mostly merges the upstream commits from CM, so I don't really know how this happened. I'll try to debug.

 

[casouzaj]

I'm glad that you have easily reproduced the NTFS card issue. Not sure, but pehaps I had forgotten to tell you in my previous posts, when I described the issue, that, just like you with ES File Explorer, Total Commander, in my case, was able to access the card contents just fine, while Android failed miserably: no system sounds whatsoever (alarms, notifications, ringtones), either playing or setting them, no music playing by either Google Music Player or Motorola Connected Music Player (I don't like Apollo, and uninstall it whenever it is embedded in the ROM), Google Play Store, Camera, Gallery, etc.

 

[Fight4Music]

Just installed over latest quarx, no need to wipe data for me. Till now all is working fine without specific issus.

Gesendet von meinem MB526 mit Tapatalk 2

 

[ccav2000]

Does Bluetooth works without issues? I remember Quarx's Linaro builds had that problem.

---------- Post added at 12:23 PM ---------- Previous post was at 11:24 AM ----------

Answering my own question: the bluetooth bug is still there, deactivating Bluetooth kills the Phone process, therefore requiring reboot. I cannot deem this ROM as stable for my needs at this time unfortunately.

 

[Kayant]

Does Bluetooth works without issues? I remember Quarx's Linaro builds had that problem.

---------- Post added at 12:23 PM ---------- Previous post was at 11:24 AM ----------

Answering my own question: the bluetooth bug is still there, deactivating Bluetooth kills the Phone process, therefore requiring reboot. I cannot deem this ROM as stable for my needs at this time unfortunately.

You need the BT fix Quarx uploaded it seems he hasn't uploaded his repo with the fix yet - http://forum.xda-developers.com/showpost.php?p=36244749&postcount=979

 

[Fight4Music]

You need the BT fix Quarx uploaded it seems he hasn't uploaded his repo with the fix yet - http://forum.xda-developers.com/showpost.php?p=36244749&postcount=979

With bluetooth fix on build of 05.01.13, i have no network connection..

 

[cyrusct82]

Installed latest build without data wipe over Quarx 07.01 every thing is ok for now:thumbup:

Sent from my MB526 using xda app-developers app