Database Develop

Jellybean

So is the hp tp ever getting jb? I saw teasers a while back but no news since.
Couldn't find another topic on the subject
Sent from my using xda app-developers app

Work is progressing on it. If you'd looked in all of the Touchpad forums, you would have found an oft-beaten thread about it in Touchpad General. It's being worked on, and will come when it is ready. Please don't ask for a date, because nobody knows, and the more you ask, the slower dev's will work.

i have to disagree. theres been no news since the little teaser video. who knows if anyone is still working on it. its being held behind closed doors so no one else can contribute. and people are basically saying "no one else talk about it or work on it because there might sorta be this one guy who may still be working on it but you may never know". and its kinda sad cause it feels like we are waiting as if this was a manufacturer release which is not what these forums are about.

+1^^ If we just had something, we could all work on it and give advice/opinions. Things could/would be moving at a much faster rate.
Sent from my Galaxy Nexus (4.1.1) using xda app-developers app

If I knew how to port I would be working on one myself, but alas..
Sent from my Galaxy Nexus using xda app-developers app

In case no one informed you all...
Ahem, unofficial cm10 everybody
http://goo.im/devs/jcsullins/cmtouchpad/preview
Do a nandroid before completely wiping in case you want to go back.

i saw that. its very interesting. a shame that its not daily driver ready. but, finally! an update! and, something actually released to public. this is more what xda is about.

its very smooth and there dont seem to be THAT many bugs besides the fact that audio does not work what so ever. Wifi works fine. Video doesnt seem to work either at least not in the youtube app it just says to retry. So ya def not a daily driver but besides all the driver stuff it is smooth.

slyr114 said:
its very smooth and there dont seem to be THAT many bugs besides the fact that audio does not work what so ever. Wifi works fine. Video doesnt seem to work either at least not in the youtube app it just says to retry. So ya def not a daily driver but besides all the driver stuff it is smooth.
Click to expand...
Click to collapse
Its a placebo effect. I have a Gnex with real JB, and the experience isn't even close. I'm convinced that project butter has a lot to do with the kernel now, because, cm9 nightlies still feels quicker, even with UI interactions. Which is mostly what JB is about.
Not trying to troll, just saying it like it is, with an unbiased opinion.. I want it to be butter smooth, as much as, anyone else here.
Sent from my Galaxy Nexus using xda app-developers app

for true "project butter" you need more advanced hardware acceleration. since hardware acceleration isnt working at all, its indeed not as smooth as it could be. butter is made up of faster frame rate ui animations that do work, and an old gaming trick called triple buffering. this is why one person will say its smoother, while another will say its less smooth.

So I had JB installed. I plugged my touchpad in and it registered as charging last night. Woke up with 0 battery. So in other words, it wasn't actually charging. Now my touchpad won't turn on at all. I get the plug that says unauthorized charger that everyone just loves!
Don't use this ROM!! If devs can read this, take off the link until that problem is fixed. Now I won't be able to use this for at least 24 hours...
Sent from my Galaxy Nexus using xda app-developers app

nikeman513 said:
So I had JB installed. I plugged my touchpad in and it registered as charging last night. Woke up with 0 battery. So in other words, it wasn't actually charging. Now my touchpad won't turn on at all. I get the plug that says unauthorized charger that everyone just loves!
Don't use this ROM!! If devs can read this, take off the link until that problem is fixed. Now I won't be able to use this for at least 24 hours...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I installed it yesterday and it charges just fine. Something went wrong with your flash or charger cause there are no issues in that regard....

slyr114 said:
I installed it yesterday and it charges just fine. Something went wrong with your flash or charger cause there are no issues in that regard....
Click to expand...
Click to collapse
same here, no issues

Charging issue
nikeman513 said:
So I had JB installed. I plugged my touchpad in and it registered as charging last night. Woke up with 0 battery. So in other words, it wasn't actually charging. Now my touchpad won't turn on at all. I get the plug that says unauthorized charger that everyone just loves!
Don't use this ROM!! If devs can read this, take off the link until that problem is fixed. Now I won't be able to use this for at least 24 hours...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Well, I don't know about everybody... But I don't have my original charger, so I use an extra charge block from an older Palm Pre... These are apparently lower in output amperage and when the unit is completely off will by default give a message about using the correct charger, but it does indeed charge although slowly, this message has nothing to do with the flashing as it did this bare stock... HOWEVER, after flashing this CM10 ROM I too woke up to mine being completely dead even though it was plugged in all night... The ROM was running great the little bit I had to play with it so far... I did not have this issue with the CM9 ROM, but can't help thinking that this not using the correct charging block has something to do with this issue... So don't feel bad, it's not just you, I have the EXACT same problem as you have stated... I'm charging with the unit off now and will do further testing, hopefully an easy fix for this surely... I want it to charge regardless of the block amperage, I have different chargers all around the house and office and have always used them all in the past without issue... I am a first time poster to XDA, but a far cry from a NOOB, and look forward to contributing more into the future...
irie111
P.S. - Great work guys on these android ROMS’s, I am/was a webOS lover like many of you I’m sure and just hate how that project has gone down the drain, it was without doubt, and remains, the best concept for a phone/tablet OS PERIOD... I used my Pre 3 and TouchPad stock right up to the point of becoming sickened by the lack of apps and long term device selection option... I do however love android and now have a newer Android phone for the obvious reasons (APPs, support, performance, latest hardware, etc) and am thrilled the good ol’ Touchpad is so capable... I really wasn't aware of how great the specs were on this thing until I looked into the CM9 flash... Plus I love flashing and customizing anyway... Much thanks to the DEVS that make this possible!!!... :good:

Charging problem as well
I installed the cm-10-20121216-Experimental-tenderloin... on Jan 3rd and it appeared that everything went well in the installation except that my TP won't charge while running CM10. I have to reboot into webOS to charge (using original TP charger) and after charging is complete I reboot back to CM10. Any suggestions for fixing this issue? Also, battery seems to drain much faster on CM10 than webOS. Is that normal? Other than the charging issue I'm loving my TP more than ever.

tlmacson said:
I installed the cm-10-20121216-Experimental-tenderloin... on Jan 3rd and it appeared that everything went well in the installation except that my TP won't charge while running CM10. I have to reboot into webOS to charge (using original TP charger) and after charging is complete I reboot back to CM10. Any suggestions for fixing this issue? Also, battery seems to drain much faster on CM10 than webOS. Is that normal? Other than the charging issue I'm loving my TP more than ever.
Click to expand...
Click to collapse
Check Settings -> Storage -> USB something or other (in upper right) -> MTP.

bananagranola said:
Check Settings -> Storage -> USB something or other (in upper right) -> MTP.
Click to expand...
Click to collapse
Thanks, problem solved.

Second that
tlmacson said:
Thanks, problem solved.
Click to expand...
Click to collapse
I can also tell you that after I ordered the proper high amp tablet USB charger block the problem is fixed without changing this option as well, but this is great and allows it to charge on a standard USB computer port as well, although slowly... Thank you guys for the support on this!!!...

cm10
Running latest version by JC and I am having no problems. I am using it as a daily.

I also installed this.
just turn on mtp device mode in settings>storage and tap 3 circles on top right. and enable mtp.
this should help:laugh:

they say it cant happen

well, i read all the time how nexus devices are unbrickable and maybe (hopefully) im wrong! so i been running stock rom rooted for a few days actually since yesterday i flashed back to stock and rooted only and flashed cwm recovery thats it. today (actually just a little while ago) i was messing around and was running antutu benchmark with stock then i flashed franco r53 kernel using his auto flash method in his app. no sooner that i started the test in antutu phone went completely black. will not respond to anything. so i said well maybe i can connect usb and get it to go into fastboot so i got lucky (or so i thought) soon as i plugged it in i saw red light at the bottom and battery charging icon. so i press power and volume down and was able to get into fastboot, i was kinda happy about this. i flashed back to stock wiped everything first wipe boot wipe cache wipe recovery wipe system flash bootloader reboot bootloader and flashed the system img and boot img and all that went thru succesfully. but it still will not boot it goes in and out red light battery icon google image. so i tried again flash stock images locked bootloader and fastboot reboot nothing i unplug usb goes straight black screen and wont respond. plug back in get red light and battery icon in and out back and forth between icon and black screen with red light. so i know allot of people get complacent in thinking that because you have a nexus you cannot brick but it is possible to brick this phone. or maybe someone can tell me im wrong. lol anyways just posting this here for people to think twice and not get so comfortable thinking you cannot brick a nexus. tommorow ill take the phone to t-mobile and get another one. and no i wont tell them it was my fault! (< for that one guy) lol good night!

I read lot about "antutu benchmark" as it's bad for Nexus 4 and cause this problem!.
hope somebody can help you out.

maddoggin said:
well, i read all the time how nexus devices are unbrickable and maybe (hopefully) im wrong! so i been running stock rom rooted for a few days actually since yesterday i flashed back to stock and rooted only and flashed cwm recovery thats it. today (actually just a little while ago) i was messing around and was running antutu benchmark with stock then i flashed franco r53 kernel using his auto flash method in his app. no sooner that i started the test in antutu phone went completely black. will not respond to anything. so i said well maybe i can connect usb and get it to go into fastboot so i got lucky (or so i thought) soon as i plugged it in i saw red light at the bottom and battery charging icon. so i press power and volume down and was able to get into fastboot, i was kinda happy about this. i flashed back to stock wiped everything first wipe boot wipe cache wipe recovery wipe system flash bootloader reboot bootloader and flashed the system img and boot img and all that went thru succesfully. but it still will not boot it goes in and out red light battery icon google image. so i tried again flash stock images locked bootloader and fastboot reboot nothing i unplug usb goes straight black screen and wont respond. plug back in get red light and battery icon in and out back and forth between icon and black screen with red light. so i know allot of people get complacent in thinking that because you have a nexus you cannot brick but it is possible to brick this phone. or maybe someone can tell me im wrong. lol anyways just posting this here for people to think twice and not get so comfortable thinking you cannot brick a nexus. tommorow ill take the phone to t-mobile and get another one. and no i wont tell them it was my fault! (< for that one guy) lol good night!
Click to expand...
Click to collapse
If it's easy to take back do it. However couple of folks have got it fixed by opening the backplate and disconnecting/reconnecting battery terminals.
Almost 90%+ people having this issue were running Antutu.

Why would you think its a good idea to flash a custom kernel on to stock?

There are tons of threads about this, do some searching your phone is not bricked, also to the poster above me there is nothing wrong with flashing a custom kernel over stock.
Sent from my Nexus 4

http://forum.xda-developers.com/showthread.php?t=2128392

XxSilent22xX said:
There are tons of threads about this, do some searching your phone is not bricked, also to the poster above me there is nothing wrong with flashing a custom kernel over stock.
Sent from my Nexus 4
Click to expand...
Click to collapse
Actually that is incorrect, it is not okay. Most Devs will post comparable kernels, or flash your own kernel on to this rom at your own risk on every rom thread op. Stock only supports its own kernel, so while some kernels might work as a stock replacement kernel, it is never a good idea to flash a custom kernel on to a stock rom unless the Dev says otherwise.

This for the help. I'll try this tomorrow morning. Of course I tab a search bit could not find the threads. I hit red light and it took me to legacy phone. I type brick in search fort n4 and nothing. So I never saw those threads about this issue. So thanks. And ive never had a problem with running custom kernels on stock ROM. Never! Lol
Any ways thanks for help! Can moderator close this thread please! Thanks!
Sent from my Galaxy Nexus using xda premium

And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app

Franco R53 is fine on stock - running it here with minimal other changes (I.e. root + email security policy hack)
I've updated every Franco kernel and all seen OK. Perhaps the benchmark related hardware failure is worth looking closely at.
FWIW, if you're back to stock, lock the bootloader and send it back as it sounds hardware to me.
Daern
Sent from my Nexus 4 using Tapatalk 2

synergeticink said:
Actually that is incorrect, it is not okay. Most Devs will post comparable kernels, or flash your own kernel on to this rom at your own risk on every rom thread op. Stock only supports its own kernel, so while some kernels might work as a stock replacement kernel, it is never a good idea to flash a custom kernel on to a stock rom unless the Dev says otherwise.
Click to expand...
Click to collapse
:sigh: No. Franco says his kernel supports the stock ROM. In fact, stock is the standard to test a kernel on. Unless a ROM is created with very specific additions that rely on a custom ramdisk to function, there is nothing wrong with it. Even then, it's not really wrong, you'll just have some missing features.

Charge your phone?
Im pretty sure you get the red light if your device has not enough power to display the screen.. Put your phone on charge through the main plug

qazibasit said:
And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
So true man so true!
Sent from my Galaxy Nexus using xda premium

This happened to me, except I was bone stock. You need to hold down all 3 buttons at the same time; several times, and then try to get into the bootloader. That's what worked for me. Once you're in the bootloader you can flash the stock image(s) via fastboot.

qazibasit said:
And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4

OniV2 said:
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4
Click to expand...
Click to collapse
if this is true then why do i need to pull the phone apart and disconnect the battery and reconnect? apparently this is a known issue and has happened to others and taking phone apart and disconnecting battery and rconnecting it fixes the issue. unfortunately i dont have the right tools to do this so i will be taking my phone to t-mobile this morning. thanks for all the help guys. really appreaciate all the responses i got.

At times the power button wont work. In some cases of soft bricks. I have this issue since i had HD2.
Sent from my GT-N7000 using xda app-developers app

estallings15 said:
:sigh: No. Franco says his kernel supports the stock ROM. In fact, stock is the standard to test a kernel on. Unless a ROM is created with very specific additions that rely on a custom ramdisk to function, there is nothing wrong with it. Even then, it's not really wrong, you'll just have some missing features.
Click to expand...
Click to collapse
That's exactly what I said in my last post. Next time the op needs to clarify if the custom kernel supports stock. But regardless I was correct.

OniV2 said:
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4
Click to expand...
Click to collapse
The service manual says ten seconds but yes it fully cuts power from the battery.

So sitting in my car waiting for t mobile store to open I decide to plug phone in to car charger since I know this will be first thing t mobile does and lo and behold phone booted up and start working. Battery drained to 0 and charging now. Go figure
Sent from my Nexus 4 using xda premium

[Q] Heavy battery drain when on charger

Hi there!
Ok so recently my Cappy has decided its going to be screwy. For some reason if I plug it in to charge, it doesn't charge, instead I get a battery drain 5-7% within about 20 mins. I've tried 5 different cables (Zip cord, walmart one, random ones I found/borrowed, one staright plug in one not usb) and 5 different chargers (car/wall plugin hybrid, apple wall charge two different computers.) and its all the same result. I can still use it as a USB no problem, moved some files around and removed and added soem photos no problem. There is no issue with the port itself (on the outside) my cover snapped off but I make sure to keep it clean.
I also have no odd battery draining I can usually get about 12-14 hours out of it. No out of place wakelocks, no apps running wild, and all my backups are on the cloud or on my laptop. Only thing I could think this is is a hardware issue. That or its just time to get a new phone. Thankfully I have an external battery charger and I've just been switching out batteries.
Any thoughts?
On Slimbean 4.2.2 build 4.2

athdaraxen said:
Hi there!
Ok so recently my Cappy has decided its going to be screwy. For some reason if I plug it in to charge, it doesn't charge, instead I get a battery drain 5-7% within about 20 mins. I've tried 5 different cables (Zip cord, walmart one, random ones I found/borrowed, one staright plug in one not usb) and 5 different chargers (car/wall plugin hybrid, apple wall charge two different computers.) and its all the same result. I can still use it as a USB no problem, moved some files around and removed and added soem photos no problem. There is no issue with the port itself (on the outside) my cover snapped off but I make sure to keep it clean.
I also have no odd battery draining I can usually get about 12-14 hours out of it. No out of place wakelocks, no apps running wild, and all my backups are on the cloud or on my laptop. Only thing I could think this is is a hardware issue. That or its just time to get a new phone. Thankfully I have an external battery charger and I've just been switching out batteries.
Any thoughts?
On Slimbean 4.2.2 build 4.2
Click to expand...
Click to collapse
My guess is that you need a new battery.
Does it show the charging animation? Also, when plugged to the pc, does fast charge help at all?

Does it charge when the phone is turned off?
sent by the scare crow, tin man, and cowardly lion on the yellow brickfree cm10.1 road.

BWolf56 said:
My guess is that you need a new battery.
Does it show the charging animation? Also, when plugged to the pc, does fast charge help at all?
Click to expand...
Click to collapse
That's just it, I bought 2 new batteries, RavPower ones. They work great and last forever when I charge. My original battery and my cheap one off ebay do the same.
And yes it shows the charging thing, by battery monitor says it's charging and shows the different kinds like a/c or usb, everything acts as it should just no charging.
I have never tried the fast charge, I forgot I even had that. I'll give it a shot.
laughingT said:
Does it charge when the phone is turned off?
sent by the scare crow, tin man, and cowardly lion on the yellow brickfree cm10.1 road.
Click to expand...
Click to collapse
Also something I haven't tried over a long period. I will try that as well.
Thank you both.
Sent from my SGH-I897 using Tapatalk 2

Also are you OC'ing or changing the Voltages? Probably won't make a difference in this issue but worth looking into. My Cappy refuses to OC at all, even at 102% it starts to act weird (System UI crashes sometimes, I lose signal, etc).

x0ne215 said:
Also are you OC'ing or changing the Voltages? Probably won't make a difference in this issue but worth looking into. My Cappy refuses to OC at all, even at 102% it starts to act weird (System UI crashes sometimes, I lose signal, etc).
Click to expand...
Click to collapse
I actually have mine stable at 110% still don't know how lol. Cappys seem to be very picky. I'll try turning it back down.
Also fast charge didn't change anything sadly. 2% lost in about 6mins. It was sitting on my bed doing nothing l
Sent from my SGH-I897 using Tapatalk 2

Apparently Samsung's hardware consistency control was lacking when the Captivate was made, so that's why they're so picky, which sucks for any kind of troubleshooting or development.
I wish I could get my Cappy to 110%. But try turning it back to 100% see if that changes anything. Also does this happen on multiple ROMs or just the one you're currently on (probably not the issue but hey I've seen weirder).

x0ne215 said:
Apparently Samsung's hardware consistency control was lacking when the Captivate was made, so that's why they're so picky, which sucks for any kind of troubleshooting or development.
I wish I could get my Cappy to 110%. But try turning it back to 100% see if that changes anything. Also does this happen on multiple ROMs or just the one you're currently on (probably not the issue but hey I've seen weirder).
Click to expand...
Click to collapse
I haven't been on a different ROM since I found Slim x3 if anything I'll try turning my phone off to see if it charges.
Oh and I forgot to say I didn't mess with voltages.
Sent from my SGH-I897 using Tapatalk 2

athdaraxen said:
I haven't been on a different ROM since I found Slim x3 if anything I'll try turning my phone off to see if it charges.
Oh and I forgot to say I didn't mess with voltages.
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
Got it, off-topic but any reason you haven't gone to Slim build 4? I saw slight improvement in performance on my Cappy. Was my daily driver until this morning when I flashed C-Rom v16, which for me is as fast. Just trying to get used to how big everything is compared to Slim, I liked being able to read about 7-8 messages in the messaging app, but now I can only see about 3 lol.

x0ne215 said:
Got it, off-topic but any reason you haven't gone to Slim build 4? I saw slight improvement in performance on my Cappy. Was my daily driver until this morning when I flashed C-Rom v16, which for me is as fast. Just trying to get used to how big everything is compared to Slim, I liked being able to read about 7-8 messages in the messaging app, but now I can only see about 3 lol.
Click to expand...
Click to collapse
Sorry x3 was a smiley not a build number, I'm on 4.2.
Anyways! I let my phone charge while off for about an hour. It was at 49% turned it back on and it was at 23% see what I mean? That's a crazy amount of juice.
Also, yeah I did play around with some other ROMs and I hated how big they all are, I like how small everything is on Slim. It just works better for me. X3
Sent from my SGH-I897 using Tapatalk 2

Oh, sorry haha so used to seeing x5 x6 x7 etc.
I don't understand why it's DRAINING your battery instead of charging it. Seems like something got reversed?
I asked because maybe it was a bad flash or something, although it seems unlikely.

I
x0ne215 said:
Oh, sorry haha so used to seeing x5 x6 x7 etc.
I don't understand why it's DRAINING your battery instead of charging it. Seems like something got reversed?
I asked because maybe it was a bad flash or something, although it seems unlikely.
Click to expand...
Click to collapse
I'll try not to use it so you don't get confused. Its just habit.
I don't either. I really did see much on hardware issues that would drain it like this. I really am stumped by this.
And recently I did flash back to stock and work my way back up to Slim to see if it would help and it didn't. I didn't think to see if it would charge on stock or CM 10 but if it really came down to it I guess I could flash back to stock and play with it. Only reason I don't think it's the ROM is because to my knowledge no one else is having this particular issue.
If you have anything I can do to test or provide info just ask. I'll do whatever is needed to help figure it out. And I'd really like to as I'll have this phone for a bit longer then I thought so I'd like to see it fixed
Sent from my SGH-I897 using Tapatalk 2

Do you have a battery charger? Like one that you just attach the battery to, to charge it. We could then see if it's your batteries (highly doubt) or your cappy (99.999% sure).
I don't really want to suggest checking with multi-meters only because the phone internals would be exposed while it's on and if you're not used to working with hardware like that you could accidentally short something etc.
Why not make a nandroid, flash to CM10, see what happens with your battery then. That way, if you ever need to go back to your current ROM you could just restore it.

x0ne215 said:
Do you have a battery charger? Like one that you just attach the battery to, to charge it. We could then see if it's your batteries (highly doubt) or your cappy (99.999% sure).
I don't really want to suggest checking with multi-meters only because the phone internals would be exposed while it's on and if you're not used to working with hardware like that you could accidentally short something etc.
Why not make a nandroid, flash to CM10, see what happens with your battery then. That way, if you ever need to go back to your current ROM you could just restore it.
Click to expand...
Click to collapse
Yeah I do, it's what I've been doing to keep using my phone, I've had this problem for a month now. I think.
It was suggested I open up the phone and check the charge port, make sure it's clean, that kinda stuff but I don't want to do that unless I'm absolutely 100% sure it's not something else.
Wouldn't hurt. I'll go try it. Thanks for being so helpful. :3
Sent from my SGH-I897 using Tapatalk 2

athdaraxen said:
Yeah I do, it's what I've been doing to keep using my phone, I've had this problem for a month now. I think.
It was suggested I open up the phone and check the charge port, make sure it's clean, that kinda stuff but I don't want to do that unless I'm absolutely 100% sure it's not something else.
Wouldn't hurt. I'll go try it. Thanks for being so helpful. :3
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
No problem, I do this kind of thing daily at my job so being able to help with something I actually like is nice :victory:

x0ne215 said:
No problem, I do this kind of thing daily at my job so being able to help with something I actually like is nice :victory:
Click to expand...
Click to collapse
Huzzah! Well, I got CM loaded, did a full wipe too. Everything looks so big. I'll report back in an hour or two. :3
EDIT
And its charging!
I guess it is in fact the ROM. Dang. I wonder why?
I'm going to see if I can get this to charge fully before bringing it to the SlimBean thread. Just to be extra sure.
EDIT
It seems to get to around 30% (31% as of now) and it just stops. It won't charge any higher. Been like that for about 45 mins.
And EDIT again. x3
Ok so I (still on CM10) couldn't get it go charge past 30% so I decided, I'm gonna poke around and I thought back on the fast charge, I wondered if it had an app, I managed to find one (Fast Battery Charging x2) and ITS CHARGING! I downloaded another app before this called Battery Mix, I love it as it has awesome battery graphs, anyways before I used Fast Battery Charging x2 it (Battery Mix) didn't have any stats on how long it would take to charge, now it does, says about 3 hrs to full, so we shall see where it goes. I don't know how the app works but I will wait and see. If this works I'll hop back to Slim and see if I can't make it work there. I don't know if it will though.
EDIT:
Got to 100%, going to flash back to Slim and see if I can't get it to charge there with the setup in CM 10 I have now, if I doesn't then I guess it must be Slim?
Edit!
Alright so back to Slim and the best I could muster is to keep my battery level the same over night. I tried using the phone for a bit and the battery drain happened again. Overnight I had nothing installed aside from gapps.

Hm...So CM10 w/ fast charge seemed to work, but when you went back to Slim the problem re-appeared? That's extremely odd. I reverted back to Slim 4.2 when C-Rom v16 was slowing down, just dirty restored and charging isn't an issue. Have you tried C-Rom v16? It's based off of Slim Rom I think.
Try it I guess, lets see if it's any other custom CM10 based ROMs. This seems like such an odd issue...

x0ne215 said:
Hm...So CM10 w/ fast charge seemed to work, but when you went back to Slim the problem re-appeared? That's extremely odd. I reverted back to Slim 4.2 when C-Rom v16 was slowing down, just dirty restored and charging isn't an issue. Have you tried C-Rom v16? It's based off of Slim Rom I think.
Try it I guess, lets see if it's any other custom CM10 based ROMs. This seems like such an odd issue...
Click to expand...
Click to collapse
Yeah, C-Rom worked great. Charged and everything. I ended up going back to Slim due to my power button being stupid again. It goes in and out and I couldn't find an option to do volume rocker wake on C-Rom so I switched back to Slim.
Its the weirdest thing. I don't even care about fixing it anymore as just figuring out the puzzle. X3
Sent from my SGH-I897 using Tapatalk 2

athdaraxen said:
Yeah, C-Rom worked great. Charged and everything. I ended up going back to Slim due to my power button being stupid again. It goes in and out and I couldn't find an option to do volume rocker wake on C-Rom so I switched back to Slim.
Its the weirdest thing. I don't even care about fixing it anymore as just figuring out the puzzle. X3
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
Haha, I share that feeling. Once something is wrong and I can't figure it out, it's not even about fixing it so much as knowing WHAT was wrong. Not sure if those settings are also available on the new ROM I'm trying now (GamerzROM, oddly enough I was going to port it for the captivate this weekend but I guess the devs beat me too it). If I see them while I'm playing around today I'll shoot you a PM.
But the fact that C-ROM works great, even though it's built off Slim (I think), puzzles me completely. Have you tried any other version of Slim?

x0ne215 said:
Haha, I share that feeling. Once something is wrong and I can't figure it out, it's not even about fixing it so much as knowing WHAT was wrong. Not sure if those settings are also available on the new ROM I'm trying now (GamerzROM, oddly enough I was going to port it for the captivate this weekend but I guess the devs beat me too it). If I see them while I'm playing around today I'll shoot you a PM.
But the fact that C-ROM works great, even though it's built off Slim (I think), puzzles me completely. Have you tried any other version of Slim?
Click to expand...
Click to collapse
Its just so annoying as I don't know a lot but I am trying to learn.
And thanks that would be fantastic actually. I appreciate it. :3
No I haven't I've tried CM 10 stable, Avatar, Pac-ROM (very fun ROM so many settings to mess with), C-ROM, Xylon, and Slim.
Sent from my SGH-I897 using Tapatalk 2

Navbar not responding

Hi,
1. So i was on xenon HD and started experiencing touch sensitivity issues where in lock screen did not respond or opened up google now instead of unlocking.
2. So I thought of switch over and flashed PAC and was really satisfied as I also got my GPS working. But the very next day it started to behave unusually and the home button of navbar kept on activating all by itself hence taking me out of any app or even app drawer.
Thought of it as ROM issue and decided would flash the latest version sometime later as my net was down.
3. Used liquidsmooth but the same problem of intermittent home button and back button too started and I had to switch off the phone within 5 minutes of flshing liquidsmooth.
4. Finally thought of getting 4.1.2 and hence flashed holoblur. By this time navbar went numb :crying:. Didn't respond to anything.
5. Restored to the stock ROM. But still navbar is not working.
Just hoping that this is not hardware related issue:fingers-crossed:. Would really hate to part away from this phone.
Please help out guys.
EDIT : So the navbar just started responding by itself. But still not perfect. Sometimes it does sometimes it doesn't.

aquaticbullet said:
Hi,
1. So i was on xenon HD and started experiencing touch sensitivity issues where in lock screen did not respond or opened up google now instead of unlocking.
2. So I thought of switch over and flashed PAC and was really satisfied as I also got my GPS working. But the very next day it started to behave unusually and the home button of navbar kept on activating all by itself hence taking me out of any app or even app drawer.
Thought of it as ROM issue and decided would flash the latest version sometime later as my net was down.
3. Used liquidsmooth but the same problem of intermittent home button and back button too started and I had to switch off the phone within 5 minutes of flshing liquidsmooth.
4. Finally thought of getting 4.2.1 and hence flashed holoblur. By this time navbar went numb :crying:. Didn't respond to anything.
5. Restored to the stock ROM. But still navbar is not working.
Just hoping that this is not hardware related issue:fingers-crossed:. Would really hate to part away from this phone.
Please help out guys.
EDIT : So the navbar just started responding by itself. But still not perfect. Sometimes it does sometimes it doesn't.
Click to expand...
Click to collapse
Try using xperiamod and by the way holoblur is 4.1.2 not 4.2.1
Sent from my Atrix HD using Tapatalk 4 Beta

Aingaran said:
Try using xperiamod and by the way holoblur is 4.1.2 not 4.2.1
Sent from my Atrix HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
My bad.
Flashed xperiamod but still same thing.
The phone is really not usable. All the navbar buttons are behaving frantically. I really cant understand what is wrong.

aquaticbullet said:
My bad.
Flashed xperiamod but still same thing.
The phone is really not usable. All the navbar buttons are behaving frantically. I really cant understand what is wrong.
Click to expand...
Click to collapse
may be a hardware error, contact your nearest store to fix it, before that flash stock and flash boot logo too, so untill they check the bootloader, they might not know your bootloader is unlocked...

Aingaran said:
may be a hardware error, contact your nearest store to fix it, before that flash stock and flash boot logo too, so untill they check the bootloader, they might not know your bootloader is unlocked...
Click to expand...
Click to collapse
I am in delhi.
This phone has not been launched in India. Hoping local guys could fix it. Really wont like to pay those leech for some software bug which i can fix up with community's help.

aquaticbullet said:
I am in delhi.
This phone has not been launched in India. Hoping local guys could fix it. Really wont like to pay those leech for some software bug which i can fix up with community's help.
Click to expand...
Click to collapse
Completely flash a stock fast boot. Issue could be kernel related. If the issue persists after a fully wiped stock flash this is a hardware issue. As is, issue sounds more like either bad settings from dirty flashing or kernel issues. The stock ROMs don't come with kernels, if your last 4.2.2 ROM had a bad kernel, same bad kernel is more than likely being used. I recommend flashing Mex Retail.

skeevydude said:
Completely flash a stock fast boot. Issue could be kernel related. If the issue persists after a fully wiped stock flash this is a hardware issue. As is, issue sounds more like either bad settings from dirty flashing or kernel issues. The stock ROMs don't come with kernels, if your last 4.2.2 ROM had a bad kernel, same bad kernel is more than likely being used. I recommend flashing Mex Retail.
Click to expand...
Click to collapse
Holoblur has a clean full working kernal right?
Sent from my Atrix HD using Tapatalk 4 Beta

The navbar works fine sometimes before again going into madmode. So i really doubt it is a hardware issue.
@Aingaran : Holoblur has custom kernel http://forum.xda-developers.com/showpost.php?p=43430196&postcount=131
@skeevydude : I need to follow the instructions mentioned here for stock JB ? http://forum.xda-developers.com/showthread.php?t=2226527 OR simply use myth tools to flash the mexican retail rom zip ?
facepalm: for asking this but is there anything else i need to do ?? )

So flashed the stock but same issue. Now the particular strip of the touchscreen where navbar rests has totally become unresponsive. Hence hardware is at fault here.
So flashed PAC ver 23 and using pie controls as of now as a temporary solution. Would try and get it repaired during weekend. @Aingaran : I guess I need to change screen and digitizer. Since you broke yours can you gimme rough idea how much it will cost ?

Yup.. Its just digitizer LCD panel is fine if you get display... And the kit for replacing digitizer cost me 3770 rs... You can search on ebay.in and don't forget to get T5 screw driver and digitizer sticker to stick digitizer to frame...
Sent from my Atrix HD using Tapatalk 4 Beta

Aingaran said:
Yup.. Its just digitizer LCD panel is fine if you get display... And the kit for replacing digitizer cost me 3770 rs... You can search on ebay.in and don't forget to get T5 screw driver and digitizer sticker to stick digitizer to frame...
Sent from my Atrix HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Okie. So I am gonna order it soon. Did you get the digitizer replaced by yourself or through a repair shop ?
Asking because here in delhi noone even touches motorola phones for repair sake.

aquaticbullet said:
Okie. So I am gonna order it soon. Did you get the digitizer replaced by yourself or through a repair shop ?
Asking because here in delhi noone even touches motorola phones for repair sake.
Click to expand...
Click to collapse
I did it myself and if u wanna know how.. Just search atrix HD digitizer replacement in YouTube

Aingaran said:
I did it myself and if u wanna know how.. Just search atrix HD digitizer replacement in YouTube
Click to expand...
Click to collapse
So basically I have to get this http://orders.ebay.in/ws/eBayISAPI.dll?ImportHubViewItem&itemid=321142293549
This is inclusive of t5 screw right ??
There is no mention of what I am gonna get in the tool kit. Do I need to order something else ?
@Aingaran please just confirm.

aquaticbullet said:
So basically I have to get this http://orders.ebay.in/ws/eBayISAPI.dll?ImportHubViewItem&itemid=321142293549
This is inclusive of t5 screw right ??
There is no mention of what I am gonna get in the tool kit. Do I need to order something else ?
@Aingaran please just confirm.
Click to expand...
Click to collapse
yes this exactly what you need...

We neeed a gummy targa thread

We have been needing a gummy thread for a long time. This will be my first thread start. So. 1/29 has been running very well for me with only occasional black screen, no response. Pull battery issues. Only every now and then. So, today j was happy to see a new build. When I went to install it safe strap said can't open zip error. Failed. Disappointed. Rebooted back into 1/29. Oh well I'm sure they'll fix it. They are great about that.

Also got the red error in safestrap on last build.
Sent from my XT875 using xda app-developers app

Strange. 2/08 is out. but its only 17.3 mb. Not sure if its a mistake or if we flash it then flash 2/07. Guess I ll try that and report back.

Nah, think the last two are junk...not sure there's any changes going on anyway. Probably just bot-builds over the latest aosp base.
Sent from my XT875 using xda app-developers app

Ya saw on twitter that they had issues with oldandroid uploading ROMs. Ours is not the only ROM not complete looks like. I looked at some others and half of them didn't look right. Hope they get it fixed, I really like gummy.

2/10 is 194 mb.

2/10 is good so far. Haven't had time to play with all of it yet but so far its smooth. Tether works, I flashed the cm WiFi fix to be sure.

2/11 so far has the best battery life of any I've flashed lately.

KC69 said:
2/11 so far has the best battery life of any I've flashed lately.
Click to expand...
Click to collapse
when you say 'any' do you mean to include other kitkat roms

Yes. Only problem is it charges slowly.

KC69 said:
Yes. Only problem is it charges slowly.
Click to expand...
Click to collapse
can you give a link to the newest build

oldandroidfilehost, then scroll down to team ghmmy.

KC69 said:
Yes. Only problem is it charges slowly.
Click to expand...
Click to collapse
which gapps are you running

Haha ALL of them! Honestly I flash pa full and liquid and aio slim gapps as well as the cm WiFi fix. So far ts been working great. And I only wipe cache and system since I've been running art.

KC69 said:
Yes. Only problem is it charges slowly.
Click to expand...
Click to collapse
do you think lmt pie uses the battery in terms of drain, any differently than say a hard coded slimpie?
and when do you convert to ART before or after restoring apps

No idea. Don't use either. And I went to art first and have stayed there. At first I switched back and forth, but now I just use art. Never had any issues but for some lag now and then. But I think it mostly had to do with all the different kernels.

2/15 is great. Has the ubuntu#2 kernel and good battery.

Been a week since last update. Hopefully they are fixin to wow us with another milestone. M.2. I'm ready. Its still the most stable, right along with cm.

Newer builds 2/25 on android hosting.org.

Last two builds have the old wifi bug on first boot...wifical.sh does not fix it,nor does reboot
Sent from my XT875 using xda app-developers app