Database Users

Blackhole 4.x to SuperClean 2.x observations

Awesome ROM - thanks for sharing your work!
I flashed the standalone 4.0 followed by the 4.01 update. Now I'm grabbing extras a bit at a time. Some observations/questions:
1. When I boot/reboot, I let the phone settle in (read SD,etc). I unlock, but then Launcher Pro is completely unresponsive. I must long press home button & use task mgr to kill it. When it comes back, all is good until next reboot.
2. I restored downloaded apps using Titanium. Market is not recognizing any as installed. First time I've gone this route. Expected?
3. I can't back out of Contacts; gotta use Home button.
4. Recently edited Memos don't come to the top of the list. Can that be reverted to the 2.1 behavior?
Small stuff in view of super clean, super cool ROM.
Thanks again!

It's disappointing, but I feel certain this post would have gotten a reply or some comments if posted in the Dev section. Here in the General section, it's either remained below the radar or been ignored. Can a mod or admin tell me if there was a more appropriate place for my post? Obviously, I haven't met the 10 post minimum, or I would have popped it in the Dev section in the Blackhole thread where others are posting their observations and feedback of that ROM. Thanks.

upgrade to Blackhole 4.2
Might as well work my way towards the 10-post minimum so I can post to the dev section where discussion actually happens...
I followed this thread to get CWM shaped up:
http://forum.xda-developers.com/showthread.php?t=957132
Trying a backup initiated through ROM Manager resulted in badness, so I repeated the steps for CWM (using Odin). BTW, I had to boot the phone once without the SD card to move past being stuck at the Samsung logo. I then rebooted into CWM (red) and did a backup.
Then I followed SoS's instructions and installed the standalone 4.2:
http://forum.xda-developers.com/showthread.php?t=940456
As long as I was just working within CWM, I was fine. ROM Manager is totally hosed. It really can only be used now to browse the ala carte options. Trying to install through it results in being stuck at the Samsung logo. 3-fingered booting from powered off doesn't even work. Repeat the CWM fix (using Odin) and boot once without the SD card.
To get around ROM Manager Madness, I use it to pick the options I want, then cancel the final step, reboot into recovery from a long press of the power button and use CWM to install the individual zips. Fine.
The original oddities in Blackhole 4.x are still present on my device. The two that are most bothersome: [1] I can't back out of contacts [2] Launcher Pro is unresponsive after booting.

For the contacts issue, create a new link to contacts from the app drawer and use the new one to replace the existing.
good day.

chopper the dog said:
For the contacts issue, create a new link to contacts from the app drawer and use the new one to replace the existing.
good day.
Click to expand...
Click to collapse
Thanks for the reply, I'll try that.
Worked great, thanks!

clock lag persists
Initially I thought that the clock lag I was experiencing in 4.01 was gone in 4.2. Nope, it remains. As others have said, seems to be related to enabling Wi-fi.
I'll go check the threads for updates but, last I checked, a double reboot was the suggested fix. I'm not clear whether people were suggesting that to be some sort of permanent fix. It didn't seem to be for me.
The time would correct after the first reboot and I would reboot again to comply with the posts, but I <think> the problem would return under 4.01. Now under 4.2, I'm sure. Last night, I double-rebooted and this morning the clock was 20 minutes slow.
Like I said, I'll go looking for updates now. Could be that this has already been resolved for real.

voice recorder, car home
Just adding a couple more oddities to the current list: voice recorder force closes and car home doesn't come up automatically when you plug in to the car cradle.
Reloading the voice recorder zip through CWM was about the only tactic I tried with no luck. Then I wanted to grab something for the ROM over-the-air, but the site was down. Checked in here and saw there was a problem with the host. That interruption of being able to download pieces parts OTA was kind of the proverbial straw, so I'm trying a SuperClean.
Pushed it through Odin and the process was smooth. The ROM looks good. None of the same oddities except the clock lag. I'm changing the sleep state of Wi-fi to see if that makes a difference.
SonofSkywalker does amazing work and I'm sure I'll be trying his ROMs again. For now, though, something different.

clock lag fix?
as per a forum suggestion, I changed the Wi-fi sleep setting. So far, it seems to prevent clock lag.
Home Screen | Menu | Settings | Wireless & Network | Wi-Fi settings | Advanced | Wi-Fi sleep policy -> select 'When screen turns off'.
Does anyone know if this has been an issue in the VZW full stock 2.2?

battery life is better
Under Super Clean 2.6, launching Google Maps and exiting has released the wake lock and battery life is much better.
Does a user guide, sticky or FAQ exist for Spare Parts? I could see that "other | running" was 100%, but I wasn't sure how to zero in on what was causing it other than trial and error based on other users' posts.

unread email count
A quick search of the forums didn't turn up much discussion, so I'll throw this out there:
on DL30 leak, the general email icon would increment and not decrement or clear until mail was manipulated on the phone. In other words, if it said 3 unread messages and I used Outlook (or the mail provider's web mail) to deal with them, it would sync and accurately display the message state in the list of emails - but the email icon on the home screen would still show 3. If 3 more came in and again they were dealt with elsewhere, the icon would go to 6. Only if action was taken on the phone itself would the counter "get real".
On Blackhole 4.x and SuperClean 2.x (any custom EB01 ROM?), the email icon on the home screen doesn't show an unread count (fine by me, I don't miss it), but when you pull down the notification bar, the unread count there acts exactly the same way.
Anyone else experiencing this? Devs, can it be fixed?

Did you clear your cache and davlik? I had some issues(when I closed an app none of my apps would show up and overall everything was running really slow). However when I was on superclean 2.6 I cleared my cache and davlik(for the first time) before I upgraded to superclean 2.8 and overall everything is working no problems.

thanks i havent used anything but sc!

Screw everything Handcent related T.T

So I've been preparing myself for the past 4 days (More or less) to make my move to GOSMS since I've found it to run smoother than Handcent. I had a thread on my privacy box with 9,400+ texts so I have started restoring it back with the other threads however I noticed it was taking longer than usual so I would stop it to see how much it had to go.
I thought I was making progress until today when I woke up and came to the realization that this dumb little app has actually been RESTARTING the restoration process from the beginning.
In short, now I have a thread with 43,000+ texts that I can't delete because my phone takes forever or Handcent crashes while Force deleting.. Any suggestions?

I know there is a way to delete the entire db through settings > apps. Of course that means deleting the entire thing. There is also another way where you can delete the db using adb
Sent from my A500 using Tapatalk

Restored from TitaniumBackup, now toggles are missing

My questions is as my title explains.
I just used the shiny new root tool to root my phone, so of course the first thing I did was boot up Titanium Backup and restore all of my apps and some of my settings.
I made sure that I was pretty careful not to override any system apps/settings, or at least so I thought.
Everything is working fine, except that now all of my toggles are completely gone.
Notification drawer: Missing
Quick Settings Panel: Missing
Settings -> Display -> Notification Drawer: Missing
Was just wondering if anyone had any ideas, or if I'm forced to do a reset and restore again :/

Nevermind I fixed it. I used Titanum Backup to wipe my two Settings Storages and that worked.
Just thought I'd post that in case someone else does the same thing.

I generally only do restore of apps, then afterwards certain ones I will restore the data, like games Angry Birds etc. You may have restored some mod app or something that overwrote those items? not sure. But going from one device to another its a bit risky restoring app and data in my expereince.
*ah, glad you got it

highaltitude said:
I generally only do restore of apps, then afterwards certain ones I will restore the data, like games Angry Birds etc. You may have restored some mod app or something that overwrote those items? not sure. But going from one device to another its a bit risky restoring app and data in my expereince.
*ah, glad you got it
Click to expand...
Click to collapse
Agreed. Never a good idea to try to restore Settings (or really ANYTHING other than user apps) when going cross-ROM, and especially cross-Device. Sometimes you can get away with it if the roms are based on the same origin (i.e. a modified stock rom from stock), but if there's ever any changes to the available settings (nearly always the case), there's a huge risk.
Glad to see you fixed it.

Annoying "service enabled" toasts

Been getting them, more often (or at least it feels like it).
Generic message, so I can't tell which app or system generating them.
How would you troubleshoot this, without phone reset?
Brand new and Bone stock 4.3, haven't had a chance to root yet.
Thanks.

gidal said:
Been getting them, more often (or at least it feels like it).
Generic message, so I can't tell which app or system generating them.
How would you troubleshoot this, without phone reset?
Click to expand...
Click to collapse
One way to solve it isn't nice, but it works:
1. Root, make nandroid backup (subsequent steps are risky), and install Titanium Backup
2. Filter for user apps
3. Disable everything
4. Reboot and confirm that problem is gone.
5. Enable the first 1/2 of the apps. (In the batch operations menu, long press an app in the middle and choose "Select all below".)
If the problem has returned:
- Of the enabled apps, one is bad. Disable half of those enabled apps.
- Go to step 5.
If the problem is still gone:
- One of the still disabled apps is causing the problem. Enable half of the most recently disabled apps.
- Go to step 5.
This method is a little time consuming, but not as bad as it seems. For 125 user apps, it will take 7 iterations to find the culprit. For fewer user apps, it will take less time. If you disable ALL user apps and the problem persists, the issue is with system data and you need to wipe some system app's data or factory reset.

fenstre said:
One way to solve it isn't nice, but it works:
1. Root, make nandroid backup (subsequent steps are risky), and install Titanium Backup
2. Filter for user apps
3. Disable everything
4. Reboot and confirm that problem is gone.
5. Enable the first 1/2 of the apps. (In the batch operations menu, long press an app in the middle and choose "Select all below".)
If the problem has returned:
- Of the enabled apps, one is bad. Disable half of those enabled apps.
- Go to step 5.
If the problem is still gone:
- One of the still disabled apps is causing the problem. Enable half of the most recently disabled apps.
- Go to step 5.
This method is a little time consuming, but not as bad as it seems. For 125 user apps, it will take 7 iterations to find the culprit. For fewer user apps, it will take less time. If you disable ALL user apps and the problem persists, the issue is with system data and you need to wipe some system app's data or factory reset.
Click to expand...
Click to collapse
Thanks - very good troubleshooting technique.
I'll do that this weekend. I'm afraid it's due to some system apps that I disabled. Thing is, I reenabled all and still getting the toasts. I'll probably do a factory reset and install my apps one at a time.
What's weird is, this is what I usually do when I get new Android device. Only this N4 responds differently to my initial set up process.

Found the culprit, it was flip silent. I didn't suspect it at first since I've been using it with my other Android devices, including on CM10.2 (4.3), and never ran into toasts issue like with N4.

Straaange things happened this morning

Seeing as though there's no more BajaROM thread, I'll post this is in the general Q&A section. Of course, while I am running BajaROM, I can't be sure that the ROM had anything to do with it.
Something weird definitely happened to my phone last night... at exactly 2:28am, it would seem.
When I woke up this morning, my live background changed to a different static background, my normal keyboard (thumb keyboard) was replaced by the samsung one, my clock widget was frozen at 2:28, the battery level read 87% (after charging all night), and hasn't changed all morning, even after an hour commute of phone calls and media play... tasker had inexplicably turned off... and I'm still finding odd things.
I restarted my phone, and my clock is more current now, but my clock widget and the statusbar clock are a minute apart for a portion of every minute (like they're offset by <60sec) Tasker still didn't turn on like it should have, until I started the app to spark it... as if it was the first time I installed it. (It does the same thing when I restore the app through Titanium Backup on a new ROM install)
I checked to make sure I still have root by starting Titanium Backup... I have root, but titanium backup says it's the free version now... when I normally have the Donate (Pro) version. I had to reinstall it from the Google Play store
I have a few nightly backup/refresh items scheduled in Titanium Backup at 2am and 2:30am... so I wonder if something went wrong.
If anyone has experienced similar issues, leave a comment.
Thanks!

DrPhant0m said:
Seeing as though there's no more BajaROM thread, I'll post this is in the general Q&A section. Of course, while I am running BajaROM, I can't be sure that the ROM had anything to do with it.
Something weird definitely happened to my phone last night... at exactly 2:28am, it would seem.
When I woke up this morning, my live background changed to a different static background, my normal keyboard (thumb keyboard) was replaced by the samsung one, my clock widget was frozen at 2:28, the battery level read 87% (after charging all night), and hasn't changed all morning, even after an hour commute of phone calls and media play... tasker had inexplicably turned off... and I'm still finding odd things.
I restarted my phone, and my clock is more current now, but my clock widget and the statusbar clock are a minute apart for a portion of every minute (like they're offset by <60sec) Tasker still didn't turn on like it should have, until I started the app to spark it... as if it was the first time I installed it. (It does the same thing when I restore the app through Titanium Backup on a new ROM install)
I checked to make sure I still have root by starting Titanium Backup... I have root, but titanium backup says it's the free version now... when I normally have the Donate (Pro) version. I had to reinstall it from the Google Play store
I have a few nightly backup/refresh items scheduled in Titanium Backup at 2am and 2:30am... so I wonder if something went wrong.
If anyone has experienced similar issues, leave a comment.
Thanks!
Click to expand...
Click to collapse
This won't help you understand what's going on but for what it's worth I'm running Baja 16.1 and it's just fine. I don't use any exposed or wanam modules. Think that might be the culprit? That is if you run any..

TheAfroSamurai said:
This won't help you understand what's going on but for what it's worth I'm running Baja 16.1 and it's just fine. I don't use any exposed or wanam modules. Think that might be the culprit? That is if you run any..
Click to expand...
Click to collapse
I do run some (several) xposed mods and wanam/gravity box mods, and have been for quite some time on several devices. A string of bizarre events like that hasn't happened though.
It is strange, though, that I did install XToast just last night. This is an xposed mod that gives you more control over the toast messages received under different circumstances. Could be the culprit... not sure. I think I'll disable it and go back to BurntToast, a mod that does similar stuff.
Maybe switching from one to the other borked something?
Thanks for the input.

I also experienced some weird behaviour. I do suspect Titanium tp cause the problems, but I'm not yet 100% sure...
Not all of my issues are completely the same as yours, but still similar.
First of all, my device is a Galaxy S3 mini, CM11 installed, rooted, XPosed installed with several modules (but no Gravity or Wanam). All partitions are in ext4, external SDcard is in exFAT.
(1) root: During startup, Titanium asks an awful lot of times for boot access. Sometimes it does for 50-100 times. In the end, devices will still be rooted but startup takes a long time.
(2) startup: As mentioned: takes really long. With EVERY reboot, I get the "Android is upgrading..." message for about a minute.
This issue is solved by clearing all .odex-files with Lucky Patcher.
(3) Keyboard. I used Google Keyboard as my standard keyboard, but a while after installing/flashing (10 minutes to an hour) Google Keyboard uninstalls spontaneously (without interaction). This happened with all Keyboard versions I tried, in system and in data. And with or without it checked as primary keyboard in language & input settings. (because of those issues I switch to SwiftKey)
(4) Background: Background (custom wallpaper) disappears after a crash, and instead I get a static generic Android wallpaper. Also, every time I try to set my wallpaper back, device instantly reboots. (soft reboot which crashes and goes into a full reboot)
(5) Clock freeze: I've had those clock freezes a few times, but months ago. I think in my case it was due to some bad code in the ROM, not Titanium.
(6) Root: Even though in SuperSU settings I asked to remember autorisation, and automatically grant access, but after every boot, I had to grant permission to all apps using root access over and over again.
In order to try to solve my problems, I changed a few things.
- Google Now Launcher + XGelSettings instead of Nova Launcher. This didn't solve any of these problems, but I do like GNL more now
- I'm using Titanium Backup 6.1.5.4 stead of latest version, installed as a data app.
- I'm using SuperSU 1.98 instead of latest version, flashed as a system app.
- I'm using an older ROM version (CM M5 instead of CM M9/latest)
Most of my issues are gone now. I didn't check for (3) anymore.

armadiljo said:
I also experienced some weird behaviour. I do suspect Titanium tp cause the problems, but I'm not yet 100% sure...
Not all of my issues are completely the same as yours, but still similar.
First of all, my device is a Galaxy S3 mini, CM11 installed, rooted, XPosed installed with several modules (but no Gravity or Wanam). All partitions are in ext4, external SDcard is in exFAT.
(1) root: During startup, Titanium asks an awful lot of times for boot access. Sometimes it does for 50-100 times. In the end, devices will still be rooted but startup takes a long time.
(2) startup: As mentioned: takes really long. With EVERY reboot, I get the "Android is upgrading..." message for about a minute.
This issue is solved by clearing all .odex-files with Lucky Patcher.
(3) Keyboard. I used Google Keyboard as my standard keyboard, but a while after installing/flashing (10 minutes to an hour) Google Keyboard uninstalls spontaneously (without interaction). This happened with all Keyboard versions I tried, in system and in data. And with or without it checked as primary keyboard in language & input settings. (because of those issues I switch to SwiftKey)
(4) Background: Background (custom wallpaper) disappears after a crash, and instead I get a static generic Android wallpaper. Also, every time I try to set my wallpaper back, device instantly reboots. (soft reboot which crashes and goes into a full reboot)
(5) Clock freeze: I've had those clock freezes a few times, but months ago. I think in my case it was due to some bad code in the ROM, not Titanium.
(6) Root: Even though in SuperSU settings I asked to remember autorisation, and automatically grant access, but after every boot, I had to grant permission to all apps using root access over and over again.
In order to try to solve my problems, I changed a few things.
- Google Now Launcher + XGelSettings instead of Nova Launcher. This didn't solve any of these problems, but I do like GNL more now
- I'm using Titanium Backup 6.1.5.4 stead of latest version, installed as a data app.
- I'm using SuperSU 1.98 instead of latest version, flashed as a system app.
- I'm using an older ROM version (CM M5 instead of CM M9/latest)
Most of my issues are gone now. I didn't check for (3) anymore.
Click to expand...
Click to collapse
Thank you for the information. I kind of suspect that Titanium Backup had something to do with my problems, as well, since it happened right around the time that a scheduled action was to take place. I think that TB was still in the middle of the previous operation at 2am when it tried to start the next one at 2:30. This has never caused a problem before, but maybe it was at the wrong place at the wrong time, as odd as that may sound.
Your problems seem to be a more constant hassle. Especially the parts about granting SU access several times. I'm leaning toward the fact that your external SD card might interfere a little. External memory is handled a lot differently in kitkat builds, which CM11 is. In newer custom ROMs, there are attempts made to "fix" it... but in your case, maybe it was counter-intuitive.
The issue is that, to paraphrase... Kit-Kat imposes a lot of data access restrictions on external media. So... if you create a file in one app... you can't modify that file in another. That's a bastardization of the whole thing, I'm sure... so look up the particulars from someone more qualified than I. haha
If I were you (and I had a few hours to burn)... I'd back up everything on your external card and your internal memory (a good idea in any case),
clear EVERYTHING and reinstall the latest versions of everything without the external card in your phone. See if you still have issues. If you don't, then the card might be a problem. Then, wipe the card and put it back in your phone, and let your phone reformat it. At that point, copy your backed-up card data to your external card in whatever way is best to keep KitKat from messing it all up again.
Luckily, I don't have issues with my external card, except for the fact that, say, if I want to put a picture of my son as my wallpaper or notification shade background... if I pick a file from the card, it won't load after I restart my phone. For stuff like this... make sure that you put the pic ON YOUR PHONE STORAGE. Consider it like this... you wouldn't have a lot of luck if your PC's desktop background or screensaver ran from the CD drive, as opposed to your hard drive.

@DrPhant0m
I already went to that process of backing up, wiping and so on. Actually, I already did it twice.
The first time, I cleaned my device, installed latest versions of everything, went through the restoring process. But most of my mentioned issues still existed.
The second time, I cleaned my device again, did about exactly what you mentioned, but I restored some older versions of the ROM, SuperSU and Titanium Backup Pro. And right now, my issues are gone!
Actually, I didn't realise there are so many KitKat-related issues with SD. Maybe my pictures indeed are/where stored on a faulty SD. But it's reformatted now, and it works. And I actually don't know if that picture is stored internally or externally, I selected the picture with/by Google Photo. No idea how it handles is
I'm not saying Titanium certainly will be the bad guy, but I'm quite sure it plays it's part in it. Other issues are caused by the custom ROM. In the last few months, developers of that ROM don't give a **** about solving issues, and introduce one new feature after the other, most of them still highly experimental. Maybe that's another problem I can't control at all

I have found that Titanium always deletes my custom wallpaper and replaces it with the Samsung default every time I do a backup. It also changes my keyboard (normally Hacker's Keyboard) back to Samsung keyboard. It started doing this several updates ago.
Verizon Note 3, 4.4.2, NC4, stock rooted
Titanium Free 6.1.5.6

Michele31415 said:
I have found that Titanium always deletes my custom wallpaper and replaces it with the Samsung default every time I do a backup. It also changes my keyboard (normally Hacker's Keyboard) back to Samsung keyboard. It started doing this several updates ago.
Verizon Note 3, 4.4.2, NC4, stock rooted
Titanium Free 6.1.5.6
Click to expand...
Click to collapse
Every time you do a backup it does this? That's bizarre. Or, do you mean when you restore a backup? I want to say to update to the paid version and see if it fixes it, and if not... request a refund.
What info do you back up when this happens? I could see restoring a backup working against you. For instance, if you restore your keyboard and maybe even some language/input system files... it might default back to the standard keyboard because your confirmation to use a 3rd party keyboard (which could theoretically log all of your keystrokes) is no longer valid.
The background thing is a different story. When Titanium Backup works well... when I restore all of my "MUST HAVE" stuff after a new ROM install... it will restore my live wallpaper, too. There are often times that TB will NOT "work well" and the widgets and wallpaper (among other things) aren't restored properly... not to mention the fact that I can not get my bluetooth pairings and known wifi networks to restore, whether I use snapshot or XML.

DrPhant0m said:
Every time you do a backup it does this? That's bizarre.
Click to expand...
Click to collapse
Yes. It is.
DrPhant0m said:
Or, do you mean when you restore a backup? I want to say to update to the paid version and see if it fixes it, and if not... request a refund..
Click to expand...
Click to collapse
No, I don't mean upon restoration. I mean I take a full backup (user apps + system apps), go off for a cup of coffee, come back, see that it completed OK, exit TI, and then I see that my background is back to the Samsung default and it I open something that needs keyboard, the keyboard is also back to Samsung default. I guess it was never enough of a bother for me to go to the trouble of buying it and then complaining. I figure that for free, I can put up with a minor annoyance.
DrPhant0m said:
What info do you back up when this happens? I could see restoring a backup working against you. For instance, if you restore your keyboard and maybe even some language/input system files... it might default back to the standard keyboard because your confirmation to use a 3rd party keyboard (which could theoretically log all of your keystrokes) is no longer valid.
Click to expand...
Click to collapse
I can see where you're thinking, but it happens right after *doing* the backup. I haven't even had the need to do a full restore yet, so I don't know what that would do.
DrPhant0m said:
The background thing is a different story. When Titanium Backup works well... when I restore all of my "MUST HAVE" stuff after a new ROM install... it will restore my live wallpaper, too. There are often times that TB will NOT "work well" and the widgets and wallpaper (among other things) aren't restored properly... not to mention the fact that I can not get my bluetooth pairings and known wifi networks to restore, whether I use snapshot or XML.
Click to expand...
Click to collapse
It's very odd, that's for sure.