• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Quattrimus JB (CM10, AOKP41)

Considering you're doing all this gratis, I would error on the side of making life easier for yourself. 30mb just isn't that big a deal...
 
  • Like
Reactions: tdm
revdmv said:
Considering you're doing all this gratis, I would error on the side of making life easier for yourself. 30mb just isn't that big a deal...
Click to expand...

Definitely agreed. I think we're all just incredibly grateful for this great ROM and the amount of time and energy you put into it. And 30 megs is nothing, seeing as literally every person using this ROM has 4G. :D
 
  • Like
Reactions: tdm
tdm said:
rc3 is up. Changes from rc2:

* Use correct audio routing lib, fixes voice search etc.
* Use p2p wifi firmware.

Notes:

wifi-p2p is untested. It seems to work for i_atnt (p930). The kernel instantly panics for i_vzw (VS920) when connecting in client mode (eg. accepting an invite). Server mode (eg. sending an invite) seems okay. This is under investigation.

I'm considering ditching the multi-rom setup and creating individual roms for each phone variant. This will reduce the rom size by about 30mb, but will add a significant amount of compile time, disk space usage, and upload time on my end.

The auto-wipe script is not included yet. It needs a bit of polish. Feel free to dirty flash from rc1 or rc2, but switching between cm10/aokp41 may be finicky and require wiping data for certain system apps. This is untested, but it was the case in ICS.

I've been really busy at work and will continue to be busy for the next week or two. Updates will be slow/sporadic.
Click to expand...

Your work is greatly appreciated! We always look forward to what you do...
 
Started noticing a blue flash on my nitro sometimes when I swipe a notification horizontally to dismiss it from the notification shade. Not every time, and only a momentary flash. Hope this isn't a sign of impending doom...
 
Captain DDD said:
So if we were to go onto this rom, but we run into errors, or we don't like the ROM (for whatever reason) we can go back to any stock rom we choose, such as gb and ics through the flashing rom method on rootzwiki? Flashing LG signed Firmware - LG Spectrum - RootzWiki
im not saying I personally hate your rom, heck I love the development. but some of us still need a way out
:) thanks
Click to expand...

Of course. The easier way is to make a backup of your stock system before flashing anything else.
 
Woke to a bsod this morning for the first time in weeks. Only had a couple minutes to look at it, but "ps" hung in an adb shell. There was one particular process which could not be listed. I think it was googlesearchservices. After that, tried reboot but that hung also... presumably trying to kill that process. Definitely strange and definitely a kernel bug. I will poke through the kernel code later.
 
arlancam509 said:
I feel kinda rude for asking, but are you planning to release another AOSP? :o I have been running your test release for a couple weeks now. I like it. I get a reboot when turning the screen off when the camera is active (still picture).

Thank you for everything you have done.
:)
Click to expand...

Yeah I can work on that Monday. I've kept my aosp tree up to date with all the recent fixes.

What issues were there with the last build...?
 
I am on beta 6 and I just lost signal all together. Screen was going through a flickering fit so I pulled the battery. Once I started it back up the only thing I could get to show up was the roaming indicator restore a previous backup with no luck. Wiped everything and re installed from. No luck. I can't get signal to come back.
 
MrB206 said:
Just a heads up to aokp users, dirty flash didn't work for me going from rc2 to rc3.
Click to expand...

FWIW, it always works for me. I never clean flash between my builds. I only clean between major version updates (eg. ics to jb).
 
tdm said:
Yeah I can work on that Monday. I've kept my aosp tree up to date with all the recent fixes.

What issues were there with the last build...?
Click to expand...

Can't downloadsome apps from market, some setting missing in mobile network and phone testing menu. No 4g for me.
 
  • Like
Reactions: tdm
Well, I feel incompetent. I went to pull the battery out again and noticed that the sim card was poking out slightly.. slid it back into its position and voil
 
tdm said:
FWIW, it always works for me. I never clean flash between my builds. I only clean between major version updates (eg. ics to jb).
Click to expand...

Yea, I've had issues with flashing roms dirty on my device. I doubt anyone else will have the issue, I figured I'd mention it.
 
I think I just witnessed a bsod happening real-time this morning.

I unlocked my phone and went to pull up an app, and the screen froze. No response from anything except the power button. But pressing the power button did turn off the screen, and then turn it back on again. I even waited about 10 seconds to check if the lock screen would engage, but it didn't. So I had some other things to do for the next 20 minutes and left it alone.

Then I picked it up again and the screen won't come on when I press the power button. adb connects, and it's got that weird issue where "ps" hangs. But the app is different (it's Google+ this time). Any attempt to access anything under /proc/<pid> that deals with the VM hangs. This includes cmdline and maps. But surprisingly, stat, statm, and status are okay....

# cat /proc/24462/stat
24462 (droid.apps.plus) D 205 205 0 0 -1 4196672 29250 0 24 0 381 87 0 0 20 0 18 0 8775412 497606656 24216 4294967295 32768 37120 3203951632 3203950500 1074693472 0 4612 0 38120 4294967295 0 0 17 1 0 0 0 0 0
# cat /proc/24462/statm
121486 24216 3868 2 0 6739 0
# cat /proc/24462/status
Name:droid.apps.plus
State&#65532; (disk sleep)
Tgid:24462
Pid:24462
PPid:205
TracerPid:0
Uid:10008100081000810008
Gid:10008100081000810008
FDSize:256
Groups:1006 1015 1028 3002 3003
VmPeak: 489976 kB
VmSize: 485944 kB
VmLck: 0 kB
VmHWM: 96864 kB
VmRSS: 96864 kB
VmData: 26820 kB
VmStk: 136 kB
VmExe: 8 kB
VmLib: 28092 kB
VmPTE: 194 kB
VmSwap: 0 kB
Threads:18
SigQ:0/5924
SigPnd:0000000000000000
ShdPnd:0000000000000000
SigBlk:0000000000001204
SigIgn:0000000000000000
SigCgt:00000002000094e8
CapInh:0000000000000000
CapPrm:0000000000000000
CapEff:0000000000000000
CapBnd:ffffffffffffffff
Cpus_allowed:3
Cpus_allowed_list:0-1
voluntary_ctxt_switches:228
nonvoluntary_ctxt_switches:285

So next I killed surfaceflinger and the bootanim comes up, but won't go away. And that pesky 24462 process is still hanging around causing trouble.

Tried to run "sync". It hangs.

Tried to unmount filesystems. Seems like ext4 read/write filesystems hang (/mpt, /tombstones) but readonly fat filesystems don't (/firmware).

It seems like there is a lock that is held but never released. Possibly in the filesystem code. But I'm sure it won't be easy to find.
 
tdm said:
Might be fixed with the new audio routing lib, try it when I release it... probably tomorrow or Friday.
Click to expand...

I think there may be something up with this audio library. Running rc3 and music/videos ignore the volume being set to 0. Basically it will not mute by turning the volume down.

*edit*
Scratch that. I had flashed a universal beasts audio package v3 over rc3. Looks like that's what caused it to ignore the volume controls.

Sent from my VS920 4G using Tapatalk 2
 
You must log in or register to reply here.
Back
Top Bottom