Database Info

[Q] SlimBean Activating on Every Reboot

I'm running SlimBean 2.5. Every time I reboot or power off/on the phone, I get the message
"Activating...
Activation can take a few minutes"
If I press the Home button, the screen goes away and I get the normal home screen. Everything works fine at this point...so I'm not sure what it's doing "activating".
It's not a big deal, but it's an annoyance.
Any way to fix?

I had the same problem and I gave up SlimBean. If you check your phone status you'll see that you lost your no. and the MIN. No big deal though. Is it not only SlimBean but any AOSP/CM10/AOKP ROMs in certain conditions.
Are you by any chance in roaming?
.
JeffN825 said:
I'm running SlimBean 2.5. Every time I reboot or power off/on the phone, I get the message
"Activating...
Activation can take a few minutes"
If I press the Home button, the screen goes away and I get the normal home screen. Everything works fine at this point...so I'm not sure what it's doing "activating".
It's not a big deal, but it's an annoyance.
Any way to fix?
Click to expand...
Click to collapse

jb_alphamale said:
I had the same problem and I gave up SlimBean. If you check your phone status you'll see that you lost your no. and the MIN. No big deal though. Is it not only SlimBean but any AOSP/CM10/AOKP ROMs in certain conditions.
Are you by any chance in roaming?
.
Click to expand...
Click to collapse
Thanks for the info. Do you know if there are any Jelly Bean ROMS for the Verizon Galaxy S3 that don't have this problem?
I'm not roaming...just normal reception in NYC. Are there any adverse side effects to this that you know of? Or is there any way to fix?
Thanks in advance for your assistance.
P.S. If you gave up SlimBean, what are you using now?

I'm having this issue with SlimBean 2.5 as well as AOKP JB4. I am in a major city with 4G coverage and I rarely see less than 4 bars at work (where I'm currently flashing).
Any ideas anyone?

Issues like this are why I won't be trying any AOPS rom's. The risk is too high and I don't want to spend time fixing IMEI. Never had any problems like this flashing rom's on my Evo.

I'm not sure if this is what fixed my issue or not. I simply formatted /system before flashing and have yet to see the activation screen. Though I haven't been using the phone quite as much as prior flashes, it has gone FAR longer without seeing the activation screen...just over an hour.
FYI: I installed AOKP JB4 this time. I'll be flashing the latest SlimBean ROM shortly and updating the post afterward.

OK, I installed SB and...unfortunately, I got the Activating popup.
So, I was thinking (I like to think). The first time I installed JB I clicked Start right away and it asked me for WiFi info during initial setup. I found out that it was doing that because it didn't have a data connection at the time I clicked "Start". So, I now wait for the radio to connect to the tower (i.e., the meter turns blue and shows 4g) before clicking start. This fixed that snag, so I thought...what if that activation app also needs the same connection to work, but it's not written well enough to handle this situation? I.e., it stores some flag that tells it failed the last time through and doesn't reset.
This is what I normally do:
cwm: factory reset, wipe /system, wipe dalvik cache, install sb & addons.
os: initial setup, change DPI to 320
<reboot 1>
os: use titanium backup to restore ID
<reboot 2>
os: use titanium to restore apps, etc
So this time, after reboot 1, instead of eagerly jumping in and setting up the phone, I did not unlock the phone until the data connection was made.
And...no more activation popup. I rebooted a few times and it's been going for 15+ minutes. I'll update if I see the activation popup again.
I know it sounds crazy...but see if it works for you and let us know!
---------- Post added at 07:05 PM ---------- Previous post was at 06:38 PM ----------
So I was thinking some more. I wondered if the activation popup always shows up if there is no signal. So this time I rebooted and unlocked straight away. I went to the app store, no connection. I hit the home button and...activation!
I rebooted again, but this time I waited for a data connection before unlocking...I did the same things as before. No activation popup!
Any ideas?
I'm going to flash AOKP JB4 and see if I can reproduce this.
---------- Post added at 07:45 PM ---------- Previous post was at 07:05 PM ----------
I could not get the Activation popup in AOKP JB 4. One thing I noticed is that AOKP connects to the network MUCH faster than SB. I know I was getting the Activation popup in AOKP JB 3, so maybe they updated something? Perhaps the order of apps at startup?
Well, I'm sticking with AOKP JB 4 for now. If you ever get SB to work without the popup PM me, please!

You are sort of on to something there. on first boot always wait for data, go through the setup, then you can reboot and what-not. I havent seen a activation screen in a LONG time, and I am SlimBean maintainer for our device, so you can imagine how many times I flash this GS3

cordell12 said:
You are sort of on to something there. on first boot always wait for data, go through the setup, then you can reboot and what-not. I havent seen a activation screen in a LONG time, and I am SlimBean maintainer for our device, so you can imagine how many times I flash this GS3
Click to expand...
Click to collapse
Yeah, I've seen your name all over the place I can absolutely imagine how many flashes you've done.
I can pretty well reproduce the activation screen issue with SB on my device on any boot. All I have to do is unlock the screen the second it's available. It only seems to happen on boot, and I don't do that very often, so I guess that's not a big deal.
I restored to a stock backup last night because AOKP wouldn't connect to my head unit via BT. I'll install SB today and give it a whirl.

Some more info.
I installed SB and waited for signal before setup. It worked fine. I rebooted a few times and, for the most part, waited until after the data connection was made before unlocking. I assumed it had already activated and was done since I didn't see the Activating screen. Unforatuntely, I just rebooted again and I unlocked immediately...and got the activation screen.
That wasn't a big deal, I figured I'd reboot and it would go away. Nope! When I rebooted it immediately went to activating...no unlock was necessary. After this point I tried playing around to see if I could find some rhyme/reason to it. Unfortunately I couldn't. The first 4 reboots produced the Activating screen no matter what I tried. Then for some unknown reason it stopped...4 reboots worked fine, no matter when I unlocked.
I am a little concerned about the length of time it takes to get a data connection. It may be just my device (hardware hiccups happen!) but it seems that it takes SB 2.6 twice as long as AOKP JB 4 to make a data connection. If that was figured out then we might not have to worry about this at all.
FYI - I'm a developer. I got my professional start on SunOS using C back in 1994 and used Unix exclusively until 2003. So I'm VERY comfortable with Unix. That being said, I'd gladly lend my expertise in troubleshooting this, if you so desire.
Hell, if you could hook me up with some links to good DIY ROM compilation instructions I'd probably go as far as putting in my own debugging code to figure out what's triggering that screen. I've been interested in getting into Android development anyway and this would be one hell of a way to start!
---------- Post added at 06:36 PM ---------- Previous post was at 06:23 PM ----------
Well, the Activating screen is back again. This is getting frustrating.

JeffN825 said:
I'm running SlimBean 2.5. Every time I reboot or power off/on the phone, I get the message
"Activating...
Activation can take a few minutes"
If I press the Home button, the screen goes away and I get the normal home screen. Everything works fine at this point...so I'm not sure what it's doing "activating".
It's not a big deal, but it's an annoyance.
Any way to fix?
Click to expand...
Click to collapse
Update 11-18-2012, using Verison S3.I am getting the "activating" message as soon as I install gapps-jb. Actually, as soon as I setup my google account. That tells me there is something wrong with the gapps. It goes away as soon as I hit the home button. I hope it get fixed soon. That's what is stopping me to use it everyday.

After going back and forward thru flashing all CM based Roms, I decide to nail the cause of this annoying message at startup. The problem always happened after installing the latest gapps 20121212-signed file and previous ones. The app that needs to be dissabled is "Setup Wizard.apk". For some reason this app runs at every startup,causing the "activating" message to pop up. The fix is: go to "manage apps" > All > Setup Wizard and click "dissable". End of the story.
TURBO

[Q]Lock Screen Doesn't Show, Home Button Not Working, and Notifications Don't Show!

I've looked elsewhere online and seen others who have had my same problem, but not one ever posted a solution and I am stumped.
I am running CM 10.2 on my GSIII and this just started happening tonight after my phone locked up and I had to pull the battery to restart it. Among other problem I had were, the brightness was set to Auto, my Quick Settings panel, will not drop down, my batter icon was reset to the circle among other minor glitches. The biggest issues I am having are with the home button not responding at all, the lock screen simply doesn't appear and the notifications, including the pull down, are constantly empty. Other apps won't function properly, like Swipe Pad and my keyboard is reverted back to default, without any way of changing it.
If anyone can help me I'd really appreciate it and would like to pay the favor back!

Agg12 said:
I've looked elsewhere online and seen others who have had my same problem, but not one ever posted a solution and I am stumped.
I am running CM 10.2 on my GSIII and this just started happening tonight after my phone locked up and I had to pull the battery to restart it. Among other problem I had were, the brightness was set to Auto, my Quick Settings panel, will not drop down, my batter icon was reset to the circle among other minor glitches. The biggest issues I am having are with the home button not responding at all, the lock screen simply doesn't appear and the notifications, including the pull down, are constantly empty. Other apps won't function properly, like Swipe Pad and my keyboard is reverted back to default, without any way of changing it.
If anyone can help me I'd really appreciate it and would like to pay the favor back!
Click to expand...
Click to collapse
Same exact problem just happened to me last night on my SGS4. Still trying to fix it.

Factory reset and flash rom again. Or flash different rom
Sent from my unknown using Tapatalk
---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------
The battery icon circle animation is a glitch in a lot of KK roms jst disabled it and ur good to go
Sent from my unknown using Tapatalk

twistedillutions said:
Factory reset and flash rom again. Or flash different rom
Sent from my unknown using Tapatalk
---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------
The battery icon circle animation is a glitch in a lot of KK roms jst disabled it and ur good to go
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
Yep, unfortunately this is all that would work. Don't flash the ROM you've already got installed though, that didn't fix anything, I just flashed a different version of the ROM I was on and updated.
Everywhere I read, the suggestions boiled down to reflashing. Pretty much, once you've corrupted the IMEI you're screwed.

[Q] Katkiss 4.2.2 (KK) #17 Display issues

Hi guys,
I wanted to put this in the development section but I guess I don't have permission yet. I am just wondering if anyone running this rom is experiencing strange issues with the display suddenly turning off for no reason. It is not "locking" itself, you can still hear the keyboard tones and such, but nothing is displayed. When you hit the power button you hear the "lock" noise, then you need to tap it again to get the unlock screen.
This happens randomly and sometimes it gets stuck in this terrible loop where the display will only come on for a few milliseconds before turning off again. I've read some display posts about wall papers and such not working and the settings for that does not solve my problem.
Some more info: I have a b60 tablet, using trebuchet as the launcher
Any help or advice would be welcomed, it would also be nice to know if I am the only one who suffers from this annoying glitch.
Cheers!

#19 is the latest version, try updating

Sorry I am an idiot, I do have 19 running currently
Sent from my XT1049 using Tapatalk

rastacalavera said:
Sorry I am an idiot, I do have 19 running currently
Sent from my XT1049 using Tapatalk
Click to expand...
Click to collapse
Hopefully the answering to questions is not as forbidden as to question them! >
Well I got some guesses:
I read about TF owners who suffer from strange behaviour when charigng theire tabs. I was reading in that direction beauce mine does something strange too: When it's charging and I touch it, it feels like light cirbbling in the fingers, when I drive em around the housing. Nothing else, but I was worryied to get an electrical hit. But it's quiet common among a lot of users a nothing to worry as far as I read. Anyway: Others got "ghost inputs". They don't touch the display but there are inputs. Some could fix that by getting a new housing. Others but dropping theire china-AC-adapters anothers by returning the tab.
Other guess: Power button R.I.P. or a cold sobe r point. Should not be that a big thing to fix - when located... Try if you can influence the on/ off behaviour by pressing on the sides around the powerbutton or other critical edges near it.
The other thing could imagin is the most often made and most often denied error: Wrong (or none) wiping / formating. (Actually I think in your paticullary case it's not this but...) I know most ROMs say it would be okay to dirty flash the #19 about eG the #17. But I wouldn't advice to do so!
My way of a clean installation
Just do backups with third party software like Next Launcher, export contacts, etc... Then copy the backup folders and contacts, etc ( if not on external SD) to a save place. After you are done run Titanium Backup and save all your apps and application data. I would NOT recommend to backup system data as well . It actually is (partially) working but cleaner is cooler. Done? Cool. I you need something special you will have to try. :>
meandmytutorials.blogspot.com for exact stepbystep walkthrough.
Reboot into recovery.
Then wipe the hell out of the internal memory. Factory reset + cache formats + dalvik format + whatever. (CARE dont format your external SD or USB if connected. Else you will loose all your data!). When using eG TWRP 2.6.3.0-X or something, also do the advanced format. I eject the external SDs and USB devices before doing so... just to be sure. After the formats / wipes I reboot in recovery. When prompted, I tell the TWRP to reinstall SU. When rebooting I reinsert the SDs etcs. Back in recovery I install the ROM, install GApps, clear dalvik and reboot to into system. There I do all the system configuration and reboot 2x. I do NOT let goole restore anything or activate any localization services or something.
Then I turn display on to 30 mins before idle. Resaon: I do the titanium restore and suffert problems when the screen turned off while backup was restoring. And my backup is aout 10GB.Annoying. Copy back the backup folders and restore the backups with the third party apps. Import contacts if you are not syncing with google or something. Restore launcher settings and stuff. Now I let the tablet boot another 2x and give it some time to settle. About 30 mins. You can see how hard it is working / syncing when opening the gallery or something else. Turn back display to 2-5 mins. Alls done.
Cheers

Delete... Tapatalk doubles my post..,
Gesendet von meinem TF101 mit Tapatalk

I did a fresh wipe/install last night and the problem still persists but not as frequently. Still really limits my use which is why I haven't replied back in so long. Just let the thing sit there cause it was basically unusable. I will check his site later to see if there is a new rom.
Sent from my XT1049 using Tapatalk

Installed another rom, 4.2.2 #23 and the problem persists. Link to video to show example https://www.youtube.com/watch?v=X8BmN-dNSOk&feature=youtube_gdata_player
Sent from my XT1049 using Tapatalk

rastacalavera said:
Installed another rom, 4.2.2 #23 and the problem persists. Link to video to show example https://www.youtube.com/watch?v=X8BmN-dNSOk&feature=youtube_gdata_player
Sent from my XT1049 using Tapatalk
Click to expand...
Click to collapse
Honestly, have not seen that issue at all using Kat Kiss 4.4.2 (I use trebuchet, too). So, it's not doing it on other ROMs (like OmniRom 4.4.x or older Kat Kiss or EOS ROMS?
I used to get some occasional screen-tear glitches with 4.3 and maybe earlier, but I don't recall seeing them anymore.

Yeah just with katkiss. I used trebuchet and Nova. Same issue
Sent from my XT1049 using Tapatalk

Issue with 4.2.2
I had a similar issue with 4.2 but it was cleared up mostly with a full wipe and flash to KK 4.3 (v29 I think). I still had some issues on 4.3 with my b70 tab not turning on. If I unplugged my charger just after the screen went into save mode sometimes I would not get a response from the power button until I plugged in the charger again.
---------- Post added at 08:30 PM ---------- Previous post was at 08:25 PM ----------
Further to my previous post, it seems most of my previous issues have been resolved with a wipe and flash to KKKK 4.4.2 (23c). I am using Nova as a launcher and not the ROM stock launchers.

Really? Weird... Same rom with a b60 tablet. I also used nova but stopped because I thought that might be part of the problem
Sent from my XT1049 using Tapatalk

NamelessROM logs for Dhiru

Hi Dhiru,
As a "new" user I'm not allowed to post on development forums so I'll left my logs to you here.
Since two or three nightlies ago I'm facing random wifi blocks, it simply doesn't activate. The problem resist reboot, cache and dalvik wipe and also one clean install. Another problem facing in the last nightly (20140710) is a few crashes of launcher and camera app simply not opening. Logs are attached. I'll read more about them to do better logs and simplify your good job with the rom. Thank you.
Regardas,
carmeloamg

kn k

Hi again,
this morning after rebooting wi-fi works but camera not. In other hand I was able to use internet but the update failed and also the source forge download using the phone. Now I'm running 20140712 with no camera and no wi-fi. There are attached log from 20140710 (or maybe 20140711 I'm not sure) working wifi and 20140712 with no camera and no wifi.
Regards.

Camera working again in 20140715 but too less ram.

Thanks bro
carmeloamg said:
Hi Dhiru,
As a "new" user I'm not allowed to post on development forums so I'll left my logs to you here.
Since two or three nightlies ago I'm facing random wifi blocks, it simply doesn't activate. The problem resist reboot, cache and dalvik wipe and also one clean install. Another problem facing in the last nightly (20140710) is a few crashes of launcher and camera app simply not opening. Logs are attached. I'll read more about them to do better logs and simplify your good job with the rom. Thank you.
Regardas,
carmeloamg
Click to expand...
Click to collapse
I'm in your same situation, as a noob I can't report issues on the developer's page. hope they will read this
---------- Post added at 10:59 PM ---------- Previous post was at 10:50 PM ----------
carmeloamg said:
Camera working again in 20140715 but too less ram.
Click to expand...
Click to collapse
Hi, i've got 140mb ram free after using the zRam advice in this page:
http://forum.xda-developers.com/showthread.php?t=2762873&page=15

Encryption Issue
one of the major issues in Nameless is the impossibility to encrypt the device, to be more precise, when i tap "encrypt device" appears the droid logo but nothing more happens (it should immediately reboot and show a percentage of progress). if i press the back (return) button it return to settings but status bar disappears, the only way to make it come back is to hold center button and remove encryption from backgroud process.
I'd like to know where is the problem

I experimented a reboot in while opening whatsapp in 20140718. Here is the log.
I swapped off the zRam but it still not going smooth. Thank you Articadrake for the advice. I had the same issue as you trying to encrypt when I was using CM11. Then I didn't try again. I think this is a feature of the rom, the same as screen recording but incompatible in a not powerful device as Galaxy SCL is.
I hope they read it also and being useful.

You may post logs in correct thread, dont think Dhiru is looking for anything in general section.

acuicultor said:
You may post logs in correct thread, dont think Dhiru is looking for anything in general section.
Click to expand...
Click to collapse
We really would like, but we are noobs and cannot post in the developer area. As soon as we will reach the 10 post required, we'll be very happy to write in the dedicated thread.

Last weekly issues
Since last weekly release I've sperimented frequent freezes (10-15sec) and then screen goes black and back to lockscreen with all the previous opened apps close! Am I the only one?

Articadrake said:
Since last weekly release I've sperimented frequent freezes (10-15sec) and then screen goes black and back to lockscreen with all the previous opened apps close! Am I the only one?
Click to expand...
Click to collapse
With today nightly, camera zoom fx freezes the phone and make camera (in any app) unusable and the system became unstable such as, passw lock screen freezes after typing the code and goes back to lock screen.... So you type again and freezes.... Till you reboot phone.

With last nightly every time phone entered deep sleep mode, it become impossibile to wake up, tried every button, tried shakung (sometimes worked in the past) now only thing was to remove battery. I had installed "screen off" app to tap and switch off screen without pressing power button. Uninstalled and went back to nandroid backup of 18/7. Everything works fine now, no more problems, only some random 15sec freezes but acceptable

Best way to reformat while rooted

Hi guys,
I've got my rooted Maxx on 4.4 (not 4.4.4) but it's been kinda unstable lately. Lots of random reboots. I tried examining some cat logs but frankly it's a bit beyond my skills on how to troubleshoot from those. I wanted to try doing a fresh install and see if that solves my stability problems.
So last time I reformatted my phone I used Android's restore factory defaults option from the settings menu. I lost root, it took days to get it back by pure chance since I was on 4.4 and was experimenting with combining the pie and other method (forgot its name) and I was the happiest when I was lucky enough to figure out how to get it back.
So I don't want to do that again. What's the best way to format /data but ideally not touch the other partitions and guarantee that I keep root? I was going to do it in SS but it's not working for me. Every time I try to reboot to SS I just get a black screen. If I restart the phone and choose to boot to SS at the menu it also goes black. Boots the system fine though. SS would have been nice because I could have taken a nandroid too in case I screw things up even worse. I thought of doing it from Android's recovery system (this is a stock BL locked 2013 Maxx so I can't install CWM or get an unlock token) but I think that button does the same thing as the button in settings, meaning that root wouldn't be preserved.
What do you guys recommend?
Thanks!

empoweredh22 said:
Hi guys,
I've got my rooted Maxx on 4.4 (not 4.4.4) but it's been kinda unstable lately. Lots of random reboots. I tried examining some cat logs but frankly it's a bit beyond my skills on how to troubleshoot from those. I wanted to try doing a fresh install and see if that solves my stability problems.
So last time I reformatted my phone I used Android's restore factory defaults option from the settings menu. I lost root, it took days to get it back by pure chance since I was on 4.4 and was experimenting with combining the pie and other method (forgot its name) and I was the happiest when I was lucky enough to figure out how to get it back.
So I don't want to do that again. What's the best way to format /data but ideally not touch the other partitions and guarantee that I keep root? I was going to do it in SS but it's not working for me. Every time I try to reboot to SS I just get a black screen. If I restart the phone and choose to boot to SS at the menu it also goes black. Boots the system fine though. SS would have been nice because I could have taken a nandroid too in case I screw things up even worse. I thought of doing it from Android's recovery system (this is a stock BL locked 2013 Maxx so I can't install CWM or get an unlock token) but I think that button does the same thing as the button in settings, meaning that root wouldn't be preserved.
What do you guys recommend?
Thanks!
Click to expand...
Click to collapse
With fstrim now incorporated in all memory actions on the newer phones, formatting in not so vital.
But without SS on your locked phone, you in a pickle!
Fix it.
---------- Post added at 02:42 PM ---------- Previous post was at 02:35 PM ----------
Is Helium backup working well now?
Look at reviews filtered for the ultra.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
Boot safe mode & that may let ss work.
Hold vol down at the moto splash screen.

Thanks for the reply! That was interesting and scary. So I tried to boot into safe mode....and the phone started bootlooping. It showed me the M logo, then a black screen, then started with the M logo again, and that was it. Beyond baffled. When I plugged in the USB charger (wireless charger didn't work) it finally booted to safe mode correctly. Coming out of safe mode back into normal mode I had the same issue--it only booted correctly when plugged into the wall with a physical charger. And my phone had plenty of battery left so it's not like it was dead. I was still at about 30% and once booted everything worked fine on battery. Wtf!? This is a reason why I feel like this build is completely messed up and want to reformat. You mentioned it's unnecessary now...is there a better option? In terms of helium, I've never had much luck with it, but it doesn't do anything with the /system--it's just apps, isn't it?

empoweredh22 said:
Thanks for the reply! That was interesting and scary. So I tried to boot into safe mode....and the phone started bootlooping. It showed me the M logo, then a black screen, then started with the M logo again, and that was it. Beyond baffled. When I plugged in the USB charger (wireless charger didn't work) it finally booted to safe mode correctly. Coming out of safe mode back into normal mode I had the same issue--it only booted correctly when plugged into the wall with a physical charger. And my phone had plenty of battery left so it's not like it was dead. I was still at about 30% and once booted everything worked fine on battery. Wtf!? This is a reason why I feel like this build is completely messed up and want to reformat. You mentioned it's unnecessary now...is there a better option? In terms of helium, I've never had much luck with it, but it doesn't do anything with the /system--it's just apps, isn't it?
Click to expand...
Click to collapse
Read the posts on the sister phone, X, about downgrading. Other than that, you need to restore with RSD. There are tricks that are harmless/even vital like removing commands from the XML file like getvar. But try the latest unmodified. See SamuriHL's general posts. You can even keep data.
---------- Post added at 12:59 AM ---------- Previous post was at 12:57 AM ----------
Are you using the stock charger & cord?
---------- Post added at 01:04 AM ---------- Previous post was at 12:59 AM ----------
Just unenable SS & then uninstall. Reboot. Then try safe mode again. Keep on uninstalling one app at a time until you get safe mode working right. Start with the latest installed apps.

So the plot thickens. Turns out I can't use House of Moto because adb doesn't work. In fact, the phone doesn't give any visual recognition when I plug it into the computer and the computer also doesn't see it as a camera or music device or as a ADB device when I plug it in. In fact, it simply resets almost on demand when I try to plug it into the computer. It also doesn't charge with a wired cable apparently; it now only charges wirelessly. So it knows when it's plugged in but doesn't do anything in terms of power or communicationand just resets. Weird!

empoweredh22 said:
So the plot thickens. Turns out I can't use House of Moto because adb doesn't work. In fact, the phone doesn't give any visual recognition when I plug it into the computer and the computer also doesn't see it as a camera or music device or as a ADB device when I plug it in. In fact, it simply resets almost on demand when I try to plug it into the computer. It also doesn't charge with a wired cable apparently; it now only charges wirelessly. So it knows when it's plugged in but doesn't do anything in terms of power or communicationand just resets. Weird!
Click to expand...
Click to collapse
Try the Ultra/Maxx brick resurrection thread in general.