Root [rom] pac-man

[reeseboy]

Yeah.. military duty. It happens.

Sent from my VS920 4G using Tapatalk 2

I'm ******ed... I figured thats what you meant, but my mind saw this - I'm on a boat

Edit: Haha it edited r e t a r d e d

 

[PrinceCorwin]

Yeah.. military duty. It happens.

Sent from my VS920 4G using Tapatalk 2

What branch? Local or overseas? Now I understand why you like tinkering with Android so much! Lol. Smartphones must be a godsend for servicemen. And thanx for your service, to both the country and the geek nation. (I'm assuming you meant USA service. Please forgive me if I'm wrong.

 

[Yoinx]

What branch? Local or overseas? Now I understand why you like tinkering with Android so much! Lol. Smartphones must be a godsend for servicemen. And thanx for your service, to both the country and the geek nation. (I'm assuming you meant USA service. Please forgive me if I'm wrong.

Nah it's here. And coast guard. Though it's getting a bit of topic

Sent from my VS920 4G using Tapatalk 2

 

[Yoinx]

I think it got merged. Look for it in the latest nightly builds

And speaking of nightly builds, we just got a new build server and I'm working to setup a distributed build farm that uses both old and new servers. This will let all devices get nightly builds and they will be available earlier in the day.

It's in at least as of the nightly on the 12th

Sent from my VS920 4G using Tapatalk 2

 

[SilentSmoke11]

It's in at least as of the nightly on the 12th

Sent from my VS920 4G using Tapatalk 2

Its in for sure? Switching from CM then...

 

[Yoinx]

Its in for sure? Switching from CM then...

I'm pretty sure it is...

I'm running it and it's sitting on the side of my screen...

Sent from my VS920 4G using Tapatalk 2

 

[SilentSmoke11]

I'm pretty sure it is...

I'm running it and it's sitting on the side of my screen...

Sent from my VS920 4G using Tapatalk 2

How do you activate it? I switched and I don't find a setting anywhere?

 

[Yoinx]

How do you activate it? I switched and I don't find a setting anywhere?

System Settings > System > Halo Settings | To configure

Drag your notification drawer and tap the new icon that's there | To enable

You'll need to use the halo))) app that you'll notice is now installed to pin apps to it, if you want to use that functionality.

Double tap and hold to drag it around.

 

[SilentSmoke11]

System Settings > System > Halo Settings | To configure

Drag your notification drawer and tap the new icon that's there | To enable

You'll need to use the halo))) app that you'll notice is now installed to pin apps to it, if you want to use that functionality.

Double tap and hold to drag it around.

Its not there... Wtf

http://imgur.com/ZDkAXrv

 

[Yoinx]

Its not there... Wtf

imgur: the simple image sharer

Which nightly are you on? Needs to be one from the last couple days.

 

[SilentSmoke11]

Which nightly are you on? Needs to be one from the last couple days.

The 12ths. Should I move up a day? If so, do I just download it(the newest or whatever) and dirty flash it right?

 

[Yoinx]

The 12ths. Should I move up a day? If so, do I just download it(the newest or whatever) and dirty flash it right?

I'm on build date Wed Jun 12 14:22:12 EDT 2013.... if you're on the same, you should be good (might be timestamped with your local time)

yeah, you can dirty flash.

 

[SilentSmoke11]

I'm on build date Wed Jun 12 14:22:12 EDT 2013.... if you're on the same, you should be good (might be timestamped with your local time)

yeah, you can dirty flash.

Thanks man. Will report back tomorrow with my findings.

 

[SilentSmoke11]

I'm on build date Wed Jun 12 14:22:12 EDT 2013.... if you're on the same, you should be good (might be timestamped with your local time)

yeah, you can dirty flash.

Back already. You prob won't see this till tomorrow but today's nightly(14th) wouldn't boot at all. After lg logo all I got was black screen. Tried clearing dalvik, and regular cache in CWM. Notjing. Just rolled back to the the one nightly I was on and I'm back, but what the hell man... All I want is some Halo action...

 

[SilentSmoke11]

I'm on build date Wed Jun 12 14:22:12 EDT 2013.... if you're on the same, you should be good (might be timestamped with your local time)

yeah, you can dirty flash.

Oh yeah and I figure out why I didn't have HALO. I was actually on the 9ths Nightly. Fail on my part

Since the 14ths nightly didn't work, I'm downloading the 12ths nightly as I type this.

 

[Yoinx]

Yeah, they probably pulled in some of the changes from cm in the past few days. People are reporting issues with it.

 

[SilentSmoke11]

Yeah, they probably pulled in some of the changes from cm in the past few days. People are reporting issues with it.

OK so I'm on it right now. Everything went fine with the 12ths nightly. I can see halo settings now in the settings menu and I have the the halo))) app now. Thanks for the help.

 

[SilentSmoke11]

OK I don't see any halo action going on here though...

http://imgur.com/a/FuAkt

 

[SilentSmoke11]

Sorry it did duplicates...

http://imgur.com/mDK5PvP

 

[Yoinx]

OK I don't see any halo action going on here though...

I dont see any halo going on though... - Imgur

It should be in your notifications pulldown. A little blue circle. You have to tap that to enable halo.

 

[SilentSmoke11]

It should be in your notifications pulldown. A little blue circle. You have to tap that to enable halo.

Thanks. I got it now but you can't have it in Tablet mode D:

That's why it wasn't showing up.

 

[Yoinx]

@TDM,

I'm just running around doing some cleaning up. One of the things that's annoyed me with logcats is the Directvolume spam at the begining of each one.

Logcat Spam:

Spoiler

[HIGH]
I/Vold ( 213): Vold 2.1 (the revenge) firing up
D/Vold ( 213): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 213): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 1, PARTN 1
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 2, PARTN 2
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 3, PARTN 3
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 4, PARTN 4
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 5, PARTN 5
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 6, PARTN 6
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 7, PARTN 7
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 8, PARTN 8
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 9, PARTN 9
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 10, PARTN 10
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 11, PARTN 11
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 12, PARTN 12
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 13, PARTN 13
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 14, PARTN 14
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 15, PARTN 15
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 16, PARTN 16
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 17, PARTN 17
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 18, PARTN 18
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 19, PARTN 19
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 20, PARTN 20
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 21, PARTN 21
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 22, PARTN 22
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 23, PARTN 23
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 24, PARTN 24
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 25, PARTN 25
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 26, PARTN 26
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 27, PARTN 27
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 28, PARTN 28
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 29, PARTN 29
E/DirectVolume( 213): Invalid 'PARTN' value
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 30, PARTN 30
E/DirectVolume( 213): Invalid 'PARTN' value
W/Vold ( 213): Duplicate state (2)
D/DirectVolume( 213): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 33, PARTN 1
D/Vold ( 213): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
[/HIGH]

It seems that vold.fstab was causing this because it had

[HIGH]dev_mount sdcard /storage/sdcard auto /devices/platform/msm_sdcc.3/mmc_host /devices/platform/msm_sdcc.1/mmc_host[/HIGH]

Modifying this to:

[HIGH]dev_mount sdcard /storage/sdcard 1 /devices/platform/msm_sdcc.3/mmc_host/[/HIGH]

fixes the spam and gives me

[HIGH]I/Vold ( 212): Vold 2.1 (the revenge) firing up
V/sysinit ( 276): Executing /system/etc/init.d/S99SuperCharger...
D/Vold ( 212): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 212): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 212): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 33, PARTN 1
D/Vold ( 212): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)[/HIGH]

which is far better to me. Is there a reason for the second sysfs path? I don't want to randomly lose my sdcard mount if it was actually necessary.

also, vold.conf is supposedly not needed anymore. Either way, it looks like the one that we have is just for emulator use as the sysfs path it points to doesn't exist.

 

[tdm]

Post deleted

 

[lakota_wolf]

After flashing I lost root within the ROM. Is there a way to flash or use the terminal to regain. Or will I have to use the adb push scripts. Any help or links to an appropriate post is very much appreciated.

Sent from my VS920 4G using Xparent Green Tapatalk 2

 

[Yoinx]

After flashing I lost root within the ROM. Is there a way to flash or use the terminal to regain. Or will I have to use the adb push scripts. Any help or links to an appropriate post is very much appreciated.

Sent from my VS920 4G using Xparent Green Tapatalk 2

Not sure how you lost root... all custom roms are rooted.

Sent from my VS920 4G using Tapatalk 2