yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Master Cylinder:
Is there a way to install Hover?

---------- Post added at 08:03 PM ---------- Previous post was at 07:52 PM ----------

I'm not sure person you were requesting from but both of these are in the parent thread of this thread. Just go up a level.
[Verizon Samsung Galaxy S III] schmaltzy:
I am really liking this ROM but I'm having an issue of the screen not coming on when I press the unlock button. It only happens every so often. The back and menu button will light up but the screen won't turn on for 10-15 seconds. The biggest pain is when I'm getting a call and it does it. I can still answer the call by blindly swiping to the right. Suggestions?
[Verizon Samsung Galaxy S III] DROIDLOVERX2:
I've actually experienced this same issue and was considering asking about it myself. Any insight would be appreciated! In my case, it seems to only occur after the phone has been sitting idle for some time, such as being plugged in over night. For example, my alarm clock went off this morning (I use Timely), but when I picked up my phone to slide and dismiss the alarm, I could not because the screen would not come on, only the buttons. Any ideas? Also, I'm on v6.5 as I seem to get better battery life and was getting random reboots with v6.6. Still loving the ROM though!
[Verizon Samsung Galaxy S III] Master Cylinder:
Hey Deliberate! I'm not sure of the status of our ROM here. I think v. 7.0 is up and running finally. Can you give us a status report?

Thanks!
[Verizon Samsung Galaxy S III] Rolo42:
I'm on 6.6 (fresh wipe) and I've only noticed two quirks:

- It will occasionally play unlock/relock sound on its own with nothing showing on the screen (no time to as it happens so fast). I haven't investigated this and it could be anything.

- Swiping the notification area (with notifications) opens the Quicksettings tiles on the first swipe.
[Verizon Samsung Galaxy S III] emomike25:
There's a setting under c-rom tools that allows you to turn the Swipe feature off. Just makes it easier to switch between the two instead of hitting the quick settings button in the top right corner
[Verizon Samsung Galaxy S III] Rolo42:
I have Statusbar | Quick Settings | Quick pulldown set to RIGHT (I like that option).

I had Statusbar | Quick Settings | Smart Pulldown set at different options with the same result. However, currently, it isn't bugging. Now I wonder if a particular notification is causing it (or cleared-while-troubleshooting).
[Verizon Samsung Galaxy S III] emomike25:
A notification shouldn't cause that to happen. I don't remember exactly what the setting is because I'm using a different rom for the time being until 7.0 gets ported over. It should be under c-tool then under the toggle settings called "Swipe to switch"
[Verizon Samsung Galaxy S III] emomike25:
Anybody heard anything on 7.0 for the d2lte?
[Verizon Samsung Galaxy S III] Deliberate:
i have it actually automatically hook up to my truck and it stays on fine? have no idea whats happening there. never heard of that before...
[Verizon Samsung Galaxy S III] griz.droidx:
EDIT: Disregard the following, I don't know what's making your phone turn off. It was late and I thought you said turn on.. My bad. Sill hope you get it fixed. I'll leave the rest of the post just can case someone does a search or something on lockscreen notifications..

I wondered about this on another rom a while back. Look for a setting around security or wherever lockscreen settings are. Something having to do with configuring lockscreen notifications. Inside those settings you can make it not wake up when you take it out of your pocket and what not. I forgot what it's called but this is what's causing it. You can keep lockscreen notifications on, and disable the option to automagically turn on your phone. I think it uses the proximity and or light sensors, because I tried a bunch of stuff trying to see what made mine come on and/or stay off, then I found those options.... Not on this rom, but It'll be the same assuming lockscreen notifications are there, and seeing that this rom has a lot of customization included, it could be turned on by default. I'm getting ready to install myself, and was reading posts when I saw this.
[Verizon Samsung Galaxy S III] emomike25:
It's all good griz. I appreciate the response. That was one of the first settings I killed. Messing around with different kernels now to see if that has any bearing. Although since flashing 5.6 yesterday am, it hasn't happened once so far. The good thing is it happens a lot less frequently on Deliberate's roms. We'll see how it goes. It would have happened several times already on any other kitkat rom so maybe 5.6 fixed it. Worst case I'll Odin back to stock then re root
[Verizon Samsung Galaxy S III] herbiehusker2608:
Does HDMI work?
[Verizon Samsung Galaxy S III] Master Cylinder:
Not Themeing Power Menu

Hey!

I have really been enjoying this ROM!

It's not themeing the power menu icons on my phone when I apply a theme through Theme Chooser. What is happening is the theme's pngs for the power menu are going into the Settings>C-Tool>Power Menu configuration tool. Change the theme, the icons change in there but not on the actual power menu. This happens with all of the icons of the options that are added.

My guess is it's because of the themeing option in the Power Menu config tool, because if I set the Power Menu>Style - Change global menu colors>Icon color mode to 'Disabled' then the sound icons on the actual power menu will theme but nothing else changes. (I guess I can color my icons in here - one color and not themed pngs . The other options there seem to have no effect though these options would seem to provide a way to allow the pm pngs to be themed.)

Coincidently, this listing in the power menu config tool does not have any icons in there, so, they pngs for 'Sound' don't get sidetracked.
[Verizon Samsung Galaxy S III] brandoncarlson33:
Anyone else loose there paid apps after a custom kernel install?

N/m KT kernel 4/3 fixes everything ROM is smooth
[Verizon Samsung Galaxy S III] Nnoar:
This ROM has everything I need! Thanks for the hard work. Unfortunately I have some problems.

On v5.6 my phone was kinda warm all the time, and even hot while using (just texting, not heavy tasks), battery life's not good too. Then I switched to leankernel and it's better, but sometimes it got reboot when I left the phone locked itself.

Just flashed v5.7, the temperature seems fine, I can notice that right after first boot. The big thing is it has no mobile signal (I'm using GSM sim card on d2vzw, in another country, not the US) so I'm back to v5.6.

Any suggestion to fix these would be appriciate. Please! I really love this ROM.
[Verizon Samsung Galaxy S III] scott45333:
Love this rom. Has great features and very smooth. I did run into an issue when I updated to 5.7 (wiped everything, clean install). I have no data after update. Changed network to LTE/CDMA/Evo, rebooted, still no data. Hopefully I can find a fix because this really is a great rom. Thank you for all of your work on this.
[Verizon Samsung Galaxy S III] omair2005:
Use my fix in the aicp thread
[Verizon Samsung Galaxy S III] scott45333:
Tried all 3 methods in your fix,unfortunately, none of the options brought data back. Thank you for your response tho.
[Verizon Samsung Galaxy S III] jlokos:
+1; I tried the same but still no data.
[Verizon Samsung Galaxy S III] omair2005:
hmm thats weird. the only thing I can think of is checking your mobile settings, toggle airplane and see if anything happens.. if not could be rom related..

after the d2lte merger, the apn-config is filled with carriers that most of us will never use.. sometimes the rom messes up which to select after a deadzone, wifi handoff, or 3g-4g handoff.. at least thats what I've noticed..
[Verizon Samsung Galaxy S III] jlokos:
I did that as well as toggle LTE. No go. thanks for your asistance.
[Verizon Samsung Galaxy S III] scott45333:
Same here. No luck with anything yet. Never ran into this one before.
[Verizon Samsung Galaxy S III] Master Cylinder:
Same Issue

Dang! No Phone/Data. Back to 5.6 for now ...

PS - Had ART working on 5.5 and 5.6, but wouldn't boot under an avalanche of " xxx Service/App Stopped" notices on 5.7. OP says don't use, so...
[Verizon Samsung Galaxy S III] Master Cylinder:
Being Looked Into

@aways is checkin' on the Verizon phone/data issues on 5.7 ...

PS - ART also working for me on mastamoon's CM11 tweak.
[Verizon Samsung Galaxy S III] scott45333:
I messed around all weekend with no success with data. Hopefully @aways can get it figured out.
[Verizon Samsung Galaxy S III] Master Cylinder:
I'm glad you did that and reported it because I've been tempted to load it up again and go through the same thing. No use banging my head against the same wall.

Here's the thread on the C-RoM forum where I got a response from aways: http://www.c-rom.org/thread-c-rom-v5-7-834.html?pid=1073

Nuthin happening yet.
[Verizon Samsung Galaxy S III] vestaviajag:
Same issue with three of us on the d2spr (sprint) version. No data/cell.

When you look up the About Phone : Baseband, it says Unknown. This leads me to believe that it disables/deletes the radio/modem. I tried flashing a current radio, it didn't stick. All APN tricks and LTE issues don't apply to this problem.

It's not a simple APN problem, or LTE issue, as it affects calls/texts. It has to be something with the ROM.

I'm wondering, hopefully someone can help here, that if you can flash 5.7, then restore the cellular/radio parts of a 5.6 backup. Is that even possible?

I'm using TWRP 2.7.0.0, that may be an issue too.
[Verizon Samsung Galaxy S III] Master Cylinder:
Modem Not Being Flashed

Hey vestaviajag,

Flashing a ROM doesn't overwrite the modem/radios partitions. I'm not an expert but I've seen it stated many times and have flashed ROMs and that should not be an issue. (I also just looked at the update-script on this ROM and it, like all update-scripts for flashing a ROM I presume, only mounts the system partition.)

As far as disabling the modem, that does seem to be what's happening. At least it's not setting it up right. Not everyone I presume of the d2* family is having this problem.

I'm also using the same version of TWRP. Hmm ... I know people have reported problems on some ROMs with 2.7 (they think?) though I have not noticed any - certainly C-RoM 5.5 and 5.6 worked alright. I haven't flashed that many with 2.7, maybe 5 to 7 ROMs.

Below are the partitions on my phone and what is mounted to them:

lrwxrwxrwx root root 1970-03-21 04:26 aboot -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 1970-03-21 04:26 backup -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 1970-03-21 04:26 boot -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 1970-03-21 04:26 cache -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 1970-03-21 04:26 efs -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 1970-03-21 04:26 fota -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 1970-03-21 04:26 fsg -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 1970-03-21 04:26 grow -> /dev/block/mmcblk0p23

lrwxrwxrwx root root 1970-03-21 04:26 modem -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 1970-03-21 04:26 modemst1 -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 1970-03-21 04:26 modemst2 -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 1970-03-21 04:26 pad -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 1970-03-21 04:26 param -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 1970-03-21 04:26 persist -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 1970-03-21 04:26 recovery -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 1970-03-21 04:26 rpm -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 1970-03-21 04:26 sbl1 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 1970-03-21 04:26 sbl2 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 1970-03-21 04:26 sbl3 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 1970-03-21 04:26 ssd -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 1970-03-21 04:26 system -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 1970-03-21 04:26 tz -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 1970-03-21 04:26 userdata -> /dev/block/mmcblk0p15
[Verizon Samsung Galaxy S III] Bramton1:
Looks like Deliberate hasn't posted anywhere in a week. 7.0 came out on the 10th, he posted the update for the LG G2 on the 11st, and then dropped off the Earth.

Starting to have some issues with 6.6. Would like to check out 7.0, but if there's no change by the weekend, I might try a new ROM. :(
[Verizon Samsung Galaxy S III] cadarndjg:
Yeah, 6.6 wasn't stable at all for me, had better luck with 6.4
[Verizon Samsung Galaxy S III] Master Cylinder:
After checkin' out Google+ it seems like aways has not yet been able to solve all of the problems on whatever needs to be converted to d2lte by Deliberate - our device maintaner. v7.0 is not out for i9100(S II) and aways is the maintainer for that device and some of the other Samsung devices. It looks like he is still troubleshooting for some of them - he had failures on initial builds for many Samsung devices.

So, I'm thinking we're not abandoned, just haven't had the bugs worked out yet for the root of our device yet. Might not happen till 7.1.
[Verizon Samsung Galaxy S III] Jacquestrapp:
I have no real further information but that was my reading of their Google+ page as well. 7.0 was a big change from 6.6 and they've been busy working out its problems, we may not see a 7.0 release for our phones but I think we'll probably get 7.1.
[Verizon Samsung Galaxy S III] Master Cylinder:
I forgot to mention that on the 'Download' page at c-rom.org you can see that 11 of 24 devices have not been upgraded to 7.0, including Note 3, i9100, i9300, i9505, etc,.., and d2lte.

------

Update 6/22: All but 3 have been updated. We're left out still.
[Verizon Samsung Galaxy S III] Deliberate:
op updated to v7.1! android 4.4.4!!!!
[Verizon Samsung Galaxy S III] jas88:
Really nice ROM but Bluetooth did not work for me on v7.1.
[Verizon Samsung Galaxy S III] capt730:
Bluetooth not working here either. Jabra phone speaker, Plantronics ear piece. Turns on, searches, doesn't find anything.
[Verizon Samsung Galaxy S III] jadesdan:
I used the C-Rom OTA updater this morning, and now I'm getting nothing but FC's. Tried re-installing, fixing permissions, dalvik and cashe wipes, but no improvement. Any other ideas before I do a full wipe and clean install (which i'd like to avoid)? Thanks.
[Verizon Samsung Galaxy S III] Rolo42:
Similar situation here: acore & dialer force-closes, then bootloops. I manually downloaded 7.1 & MD5 file (the OTA doesn't seem to MD5 check) and it passes with WinMD5 and TWRP. I cleared cache & Dalvik but I don't want to do a full wipe/FDR. Reverting to 6.6 seems to have brought everything back to normal.

I am not running Xposed; I am running avast!, BusyBox, Ti Backup (trying to think of what may interfere...). I have a few unused system apps frozen...may have something to do with it. Do you have anything frozen?
[Verizon Samsung Galaxy S III] capt730:
Since 7.1 is on a new base, a full wipe was recommended. I got it set up and all was running smooth with the exception of Bluetooth not connecting to anything.
[Verizon Samsung Galaxy S III] Jacquestrapp:
It's usually a good idea to check the changelog on the main C-Rom site: http://www.c-rom.org/thread-c-rom-4-4-4-v7-1-846.html. They require a full wipe going from v6.x to 7.x. I wouldn't recommend doing it for v7.1 though, as others have noted and I just discovered for myself, Bluetooth doesn't work, the phone can't find any BT devices.
[Verizon Samsung Galaxy S III] thelangosta:
Bluetooth seems to be broken across several roms right now.
[Verizon Samsung Galaxy S III] johnlgalt:
Any specifics on *which* ROMs?
[Verizon Samsung Galaxy S III] thelangosta:
AICP for sure. Let me try on Beanstalk.

Edit: seems to work fine on the Beanstalk from Ed Chen. I know there have been reports on other threads but I can't remember which ones.
[Verizon Samsung Galaxy S III] capt730:
I've had issues on C-Rom and AICP. Mastamoon's and Gummy are fine for me. I haven't tried Liquid, Carbon or Slim.
[Verizon Samsung Galaxy S III] johnlgalt:
I'm willing to give the new SLIM-based C-ROM 7.1 a spin, but I have to have BT working in order to use my Google Music player in my car (Motorola T505 BT to FM transceiver) b/c my car does not have an AUX jack for me to plug into (which I plan on remedying next month - have to get a part in, it has a hookup waiting to be used, but was never actually installed).

I'm also gonna start looking around for a pure CM11 or another CM11-derived ROM, b/c I really like CM11.

I'll keep a Nandroid backup of the 6.6 I have on it now, flash 7.1, make another Nandroid backup and then go ROM hunting later this evening. I can get by without BT for a couple of days, but I am taking a trip out west starting Friday, and driving, and am gonna need my music :p

I'll look at some of these other ROMs and see which is and which is not BT ready and report back.
[Verizon Samsung Galaxy S III] jlokos:
BT works on Beanstalk, DU, Lego and Omni rom.
[Verizon Samsung Galaxy S III] johnlgalt:
Changelog link (in OP) still links to 6.1, BTW
[Verizon Samsung Galaxy S III] MrBrady:
Lego? What's the Lego ROM?

VZW SGSIII
[Verizon Samsung Galaxy S III] TotallyAnxious:
Has anyone else gotten really weird mobile network options on the 7.1 build? There's tons of them now and they aren't even labeled correctly. The one I have selected shows as CDMA+LTE/EVDO.

Also has anyone else figured out what chamber of secrets does? If you activated developer options and scroll to the bottom there's a blank list option, click on it a few times and a new option pops up. Can't figure out what it actually does.
[Verizon Samsung Galaxy S III] johnlgalt:
Just installed - I'll let you know in a few.
[Verizon Samsung Galaxy S III] capt730:
I noticed that too, but I was still connected to LTE. Since bluetooth didn't work, I didn't check out too much.
[Verizon Samsung Galaxy S III] azumandias:
http://forum.slimroms.net/topic/981-chamber-of-secrets/
[Verizon Samsung Galaxy S III] Nomad1600:
I think LiquidSmooth is also having an issue with Bluetooth on some platforms.
[Verizon Samsung Galaxy S III] Master Cylinder:
I'm gonna paste the recommendation from the dev of this ROM from his website just like it is on there:

IF YOU ARE ON OLD BASE FULL WIPE RECOMMENDED FOR THIS VERSION SINCE WE HAVE REBASED ROM!!!!

I think there is a message here not just in the words but the color and size and boldness of the texts.

EDIT: Oops! I didn't realize that others had answer this - but, might as well leave it.
[Verizon Samsung Galaxy S III] Rolo42:
Maybe said web site (homepage or changelog) could be linked in the original post.
[Verizon Samsung Galaxy S III] Master Cylinder:
Uh.... yeah, good thinking! Doi!:cyclops:

v 7.1: http://www.c-rom.org/thread-c-rom-4-4-4-v7-1-846.html

v 7.0: http://www.c-rom.org/thread-c-rom-v7-0-845.html

PS - Many reporting Bluetooth not working on d2lte threads ...
[Verizon Samsung Galaxy S III] johnlgalt:
Was there an option in the old base for setting a preferred WiFi connection that is not now in this particular base? Or am I misremembering that?

So far, it seems pretty decent, got almost all of my apps reinstalled, now trying to update them all and then make new backups....
[Verizon Samsung Galaxy S III] simpson173:
I spent about 3 hours wiping,flashing,setting everything up.....had my contacts after the flash and now they are gone. Anyone else experience this. I'm a little bummed having to restore 6.6
[Verizon Samsung Galaxy S III] Ghost Protocol:
Hello 'simpson173'.

I believe you're the only one having that issue. My Contacts is still there and syncing fine. Question ~ When you log into your Web mail (CLICK HERE) is your contacts still there? If they are still there, I suggest checking the settings and confirming that it is syncing properly.

Hope this helps. :fingers-crossed:
[Verizon Samsung Galaxy S III] simpson173:
Yea....I probably am the only one with this issue. That's usually the way it goes with me. Had issues before with Kit Kat not syncing contacts but they have been resolved since I have been on C-Rom.... maybe a later version will be good. (fingers crossed) but Thanks for the quick reply.
[Verizon Samsung Galaxy S III] Ghost Protocol:
Buddy... It sounds like you're giving up!! No need to be sad or disappointed. Check your settings and keep playing with the Sync option. Restart your phone too. Believe me no need to wait or switch to another RoM. You have a little or should I say - Minor - issue. I believe it's a syncing issue that happens to all of us - on any RoM. Be positive and be patient. :highfive:
[Verizon Samsung Galaxy S III] johnlgalt:
My contacts are all in Google, so no.
[Verizon Samsung Galaxy S III] jlokos:
I have had this issue with a number of kit kat roms when I dirty flash to a new build. Here is what i do. Go into TIbBu, contacts storage, wipe data, then restore b/u; go into contacts, wipe data and restore b/u. If you don't have TiBu, go into settings>Apps, contacts storage, wipe data and do the same thing in contacts and reboot the phone. The contacts should thereafter re-sync.
[Verizon Samsung Galaxy S III] johnlgalt:
Ahhh, I don't dirty flash when changing ROM bases anymore. Makes sense now that that can be the root of the issue.
[Verizon Samsung Galaxy S III] capt730:
+1.... I wipe everything when switching roms. That way, if I have an issue, it is much easier to narrow down if it is rom related.
[Verizon Samsung Galaxy S III] simpson173:
Thanks...this was not a dirty flash this was clean and like I said they were there after the boot. I like the new boot animation by the way. When I have time I will try these suggestions for now I am back on 4.4.2 (but not for long )
[Verizon Samsung Galaxy S III] DROIDLOVERX2:
Ignore - deleted post! :D
[Verizon Samsung Galaxy S III] simpson173:
Are you sure you are on the right forum?
[Verizon Samsung Galaxy S III] DROIDLOVERX2:
:o HAHA! Oops. Meant to post this on another forum. Sorry! Got my open tabs confused... :silly:
[Verizon Samsung Galaxy S III] pbaden:
The new version 7.1 is very slick. Tons of features, but I was having some problems with the phone shutting off and I had a couple of fc's. Going to check out Bean Stalk but will be watching for updates here as the previous release (4.4.2) was rock solid. Thanks Devs!!!!
[Verizon Samsung Galaxy S III] emomike25:
Hey Deliberate are you aware of any possible fixes/plans for the Bluetooth issue on the d2lte not recognizing any devices? Just curious as this is my dd/go-to rom. Nothing even comes close to c-rom other than your older beanstalk versions.
[Verizon Samsung Galaxy S III] cadarndjg:
4.4.4 running pretty well on my phone.

The only feature I miss on this rom is the ability to reset the battery monitor/stats. Sometimes I like to check the use at a certain location and would like to reset it once I get there. If I'm missing something obvious, forgive me.
[Verizon Samsung Galaxy S III] pbaden:
Anyone else running 444? I'm wondering specifically about stability.

Also, does this version support using ViperFx for audio? It doesn't look like you can change from DSP.
[Verizon Samsung Galaxy S III] haps16:
I am running it and have had zero issues with stability. I am also running Viper. Downloaded the 4.x ask from their site
[Verizon Samsung Galaxy S III] Sean Z:
Can anyone report if the latest build has bluetooth working? I heard that it's not discoverable?
[Verizon Samsung Galaxy S III] Jacquestrapp:
It doesn't work. The latest build is still v7.1 (June 22nd).
[Verizon Samsung Galaxy S III] emomike25:
Bluetooth

Hopefully the next release will have the fix :good::good:. Im sure Deliberate is working on a fix. Not sure when the next release will be as even on the C-Rom website 7.1 is still the most current for all of the devices. All of the other roms that had the same bluetooth issue have been fixed for the most part, probably something that got merged that threw it off.