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

disadjusted

Senior Member
Jul 18, 2012
165
110
0
Eastbourne
test with latest 13/01/05

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
i flashed latest linaro build few hours ago without wiping data, with fix permissions...

it rebooted twice: first after Moto-Logo during red LED (even before cyan-Logo); second after booting up and trying it out for a couple of minutes (perhaps 2-5) while titanium backup was loading...

since then it seems quite stable and feels fast'n'fluid on default interactive gov + sio scheduler without mem-tweaks @ 300/600/900/1100 MHz.

Some initial lag after screenoff is still there, but seems to go away faster than on last quarx' build i flashed from 12/12/31... and homescreens, menus etc are even far more fluid. :victory:

thanks so much for your efforts! :good:
 

ldiomedi

Senior Member
Oct 11, 2011
1,299
645
0
Córdoba
I flash the latest yesterday from zero restoring backup from titanium. No problem at all. And its working great. Have a question. In cm10 threat there's a kernel builded for a user without a commit that could be the cause for the ringtone issue and battery drain. Does anybody try it? Could that work on this build? Thanks wskelly for your work!

Sent from my MB526 using xda app-developers app
 

ldiomedi

Senior Member
Oct 11, 2011
1,299
645
0
Córdoba
I flash the latest yesterday from zero restoring backup from titanium. No problem at all. And its working great. Have a question. In cm10 threat there's a kernel builded for a user without a commit that could be the cause for the ringtone issue and battery drain. Does anybody try it? Could that work on this build? Thanks wskelly for your work!

Sent from my MB526 using xda app-developers app
I answer to myself. I just tried the kernel. Boots OK, but there's no WiFi. Without testing more, I went back to original kernel.

Sent from my MB526 using xda app-developers app
 

wskelly

Senior Member
Oct 26, 2010
229
253
0
Thanks guys for trying it out!

Does anyone have an issue with a black screen after rebooting? So, the first boot after installing on top of a Quarx build, it will start up fine usually. However, the second time you boot (when you manually restart the phone for example), it will get to a black screen w/ red LED, eventually the LED will turn off and that's it. Nothing else.

I am struggling with this issue right now trying to help Blechd0se figure it out. It is related to the JellyX kernel somehow and there is a discussion about it over on the JellyX thread:

http://forum.xda-developers.com/showthread.php?t=2017329&page=51
 

disadjusted

Senior Member
Jul 18, 2012
165
110
0
Eastbourne
bluetooth problems

not a single reboot since i first tried this out more than 24hours ago.

edit / @wskelly: i rebooted manually 3 times for trying things out, no black screen issue encountered. but as i described, first time booting i had black screen with red LED for about a minute, after that it rebooted and booted normally...

===

unfortunately i now have bluetooth issues.

even if i only use a BT-keyboard, after turning off BT, the phone-process is being killed. after going to airplane-mode it works again.

any chance for another patch to adress this issue?

@kayant: do you know where quarx addressed it?
 
Last edited:
  • Like
Reactions: wskelly

slph

Senior Member
Feb 19, 2011
136
76
0
Novosibirsk
thx. i have this file already, but any description of what it fixes could be interesting...
In 18.11.12 build was broken bluetooth, so, this file is the 'fix' for 18.11.12 build which was built with Linaro :)
May be lib compiled without linaro? I don't have any details, sorry.

Is it possible to revert this commit for kernel? (reverting solved batt drain on Defy green lens)
 

ldiomedi

Senior Member
Oct 11, 2011
1,299
645
0
Córdoba
Thanks guys for trying it out!

Does anyone have an issue with a black screen after rebooting? So, the first boot after installing on top of a Quarx build, it will start up fine usually. However, the second time you boot (when you manually restart the phone for example), it will get to a black screen w/ red LED, eventually the LED will turn off and that's it. Nothing else.

I am struggling with this issue right now trying to help Blechd0se figure it out. It is related to the JellyX kernel somehow and there is a discussion about it over on the JellyX thread:

http://forum.xda-developers.com/showthread.php?t=2017329&page=51
I'm using the latest Rom since two days ago coming from miui gb. Not a single reboot and no black screen restarting. The bugs are still the same: no sound after x hours (don't controlled how many) and the bt, but for this last one I installed the fix, and no problem sharing files. Don't have a device to attach, so don't know if will work with them.

Sent from my MB526 using xda app-developers app
 

disadjusted

Senior Member
Jul 18, 2012
165
110
0
Eastbourne
BT + blackscreen / power consumption with linaro

In 18.11.12 build was broken bluetooth, so, this file is the 'fix' for 18.11.12 build which was built with Linaro :)
May be lib compiled without linaro? I don't have any details, sorry.
i tried flashing the fix (wiped cache & dalvik, fixed permissions) but afterwards it doesn't boot up anymore, hangs on red LED with screen on...

perhaps i should try latest quarx 13/01/10 if there BT works...? unfortunately i need this! but i loved the fluidity of linaro builds!

and i appreciate one more thing:

lately the lowest power consuption was 0.7%/h on every of quarx' builds, but with linaro builds (quarx' 11/18 and both of wskelly i tried) lowest was only 0.5%/h (with full sync on wifi over night)... so getting more done in less cycles also seems to save battery :)
 

disadjusted

Senior Member
Jul 18, 2012
165
110
0
Eastbourne
BT works on latest quarx

so BT works flawless in latest quarx... many hickups i recognized when using the BT keyboard with 13/01/05 linaro build are gone (like virtually hanging keys and other input delays) and bluetooth can be turned on & off without problems...

what i further recognized is how long it takes to optimize apps without linaro... felt like it was 3 times as long!

does this really belong to compiling with linaro or are there just some files different?

would be a tremendous advantage if i could use BT on latest Linaro build :)

===

edit: despite first impressions (optimizing apps) the latest quarx build is also quite fluid, even more than latest linaro build... but battery consumption is a bit higher, like 0.8%/h over night... (0.5%/h with linaro)

perhaps it'd work to compile latest quarx with linaro...? :)
 
Last edited:

ldiomedi

Senior Member
Oct 11, 2011
1,299
645
0
Córdoba
I want to give my experience with this latest Rom from 05/01. It been up for more than 100 hours and never had the ringtone issue. Some times the phone became a little laggy, but that is for the lots of open apps. All my ringtones are mp3 stored on the sdcard. After a while, it became just like when I flash the Rom. For my use, middle to hard use, it's very stable. The battery drain fast, but that's for the hard use.

Sent from my MB526 using xda app-developers app
 

Attachments

wskelly

Senior Member
Oct 26, 2010
229
253
0
Hi guys,

I haven't abandoned this, to try to keep it updated with Quarx. I have no idea how Quarx does it acutally and it looks like he is supporting a couple of different platforms. Took me several days to try to figure out the black screen issue. :) For whatever reason it seems there are bugs affecting ONLY MB525 users (like me) and not MB526:

  • black screen issue
  • battery drain issue

I wonder what the hardware differences are and how we can differentiate the two platforms?

I am not sure how Quarx does everything he is doing, it is a lot of work to keep track of everything.

Also, does anyone know if there is some sort of mechanism to record the state of all of the sandboxes, so that this list could be included with the ROM? It would be a *huge* improvement for everyone (on all platforms) if we had a list like:

moto_jordan_common branch: whatever latest commit: 3fe554b !! FILES NOT IN SYNC WITH REMOTE !!
jordan_kernel branch: jellybean latest commit: bb45776
frameworks_base branch: jellybean latest commit: 7765abc !! MODIFIED FILES NOT CHECKED IN !!

etc.

The system in place right now is really not adequate for quality control -- i.e. I have no idea what was in my Jan 04 build and there is really no way for me to find out.
 

mmbytes

Member
Sep 19, 2012
31
2
0
Hi wskelly,

thanks for all the work you put in!! Sounds you get a bit overwhelmed with it... :p
I can only confirm that it working fine on my 525, except from the known issue that it sometimes hangs in the black screen at startup.
But here is something that might help you:
I did not have any boot problems for days, while regular shutting down the phone over night and sometimes rebooting it manually during the day.
The black screen started only when I changed the processor settings in 2nd Init from your rom's default setting "interactive" to "power save".
I had a hard time to get the phone booting at all after I changed that. Only after several battery removements the phone started fully again.
And now I have the black screen every now and then.
I'm thinking of doing the full wipe ext4 again to see if it goes away again. Full wipe really works wonders with stability. But have my phone nicely set up at the moment so looks unlikely to start from scratch again.
 
Last edited:

wskelly

Senior Member
Oct 26, 2010
229
253
0
Bluetooth finally fixed

I've found the problem with Bluetooth + Linaro. I haven't uploaded the code to github yet but if you want to try it out to see if it works for you grab the 21-Jan version posted at the link on the OP. I still see a 'process has stopped' when I turn BT off while connected. This however doesn't seem to be a big deal.

Here is the offending code in frameworks/core/base/jni/android_bluetooth_BluetoothSocket.cpp

Code:
case TYPE_SCO:
  struct sockaddr_sco addr_sco;
  addr = (struct sockaddr *)&addr_sco;
  addr_sz = sizeof(addr_sco);
  memset(addr, 0, addr_sz);
  addr_sco.sco_family = AF_BLUETOOTH;
  memcpy(&addr_sco.sco_bdaddr, &bdaddress, sizeof(bdaddr_t));
The address from bdaddress is not copied into sco_bdaddr in the memcpy() operation. The fix was to change the last line to this:

Code:
memcpy(&addr_sco.sco_bdaddr.b[0], &bdaddress.b[0], sizeof(bdaddr_t));
This explicitly copies the address where it is supposed to go without fail. Now, I've also got a lot of log statements all over this file, so if something still is wrong please take a logcat.

The weird thing is when I remove the logcat statements from the file BT doesn't work anymore. (??) It makes no sense so it has to be something with optimization and/or alignment. Not sure what.