Database Develop

[I9000] No "internet calling" option in settings of Galaxy S Gingerbread

I'm sorry if this is a noob question, but even the omniscient Google failed to give me a satisfactory answer to my dilemma.
I've waited, prayed and even made some ritual sacrifices to the Gods of the mountains under the sea to make Samsung update the I9000 to Gingerbread. And all that for this one feature: to use integrated SIP calling.
But when I updated to Gingerbread this morning and looked in the "Call Settings" menu, I couldn't find the "Internet Calling" option. With a sinking feeling that the mountain Gods have failed me, I decided to turn to the Tech Wizards of the xda-developers for help.
I saw in a few sites that it is possible to enable the option, but I couldn't understand anything as i'm a total noob in these matters. My phone's details:
Model: Samsung Galaxy S GT-I9000.
Firmware version: 2.3.3
Baseband version: I9000DDJV4.
Kernel Version: 2.6.35.7-I9000DDJV6-CL198883
Build Number: GINGERBREAD.DDJV6
Please help me out here. I'm desperate to the point of doing something crazy, like getting a Nokia.

Sorry for bumping this up. Somebody please help me out here.

Udayakiran said:
Please help me out here. I'm desperate to the point of doing something crazy, like getting a Nokia.
Click to expand...
Click to collapse
lol That's TOO crazy! Personally, I never used SIP or Internet calls. But if it's that important to you, you can try flashing CM7 on your phone. It has this feature implemented extensively in the settings. Besides, you won't come back from CM7. Everything else is pretty much inferior!

Or find another rom like XWJVH or XWJVO they have all the stuff

Prasad007 said:
lol That's TOO crazy! Personally, I never used SIP or Internet calls. But if it's that important to you, you can try flashing CM7 on your phone. It has this feature implemented extensively in the settings. Besides, you won't come back from CM7. Everything else is pretty much inferior!
Click to expand...
Click to collapse
Okay, but is CM7 stable? I read that some features are not working properly. Anyway, i'll try it out.
I felt that using inbuilt SIP instead of Skype or Fring would lessen battery usage. I also liked the idea of dialling from the dialler and video calls over IP.
Taxiozaurus said:
Or find another rom like XWJVH or XWJVO they have all the stuff
Click to expand...
Click to collapse
Wont that change the product code? That happened to me when I flashed a froyo leaked ROM. My phone had the product code as "KOR" instead of "INU".
And thanks for your replies, guys. I had almost given up hope.

I looked into CM7 and some of the bugs are a bit scary. Esp, the issue with the phone unable to charge when it is powered off. I routinely run the risk of a fully drained battery, even with daily charging. Besides, the gingerbread update has speeded up the phone considerably. So, I'm quite happy with it, except for the SIP thing. I'll have to consider it more before I make the jump.

Udayakiran said:
I looked into CM7 and some of the bugs are a bit scary. Esp, the issue with the phone unable to charge when it is powered off. I routinely run the risk of a fully drained battery, even with daily charging. Besides, the gingerbread update has speeded up the phone considerably. So, I'm quite happy with it, except for the SIP thing. I'll have to consider it more before I make the jump.
Click to expand...
Click to collapse
That is not a bug, just operating according to CM7 spec. When you plug in the charger, the phone boots up. You can then turn the screen off and go to Airplane mode if you wish it to charge more quickly. No big deal.
As for the rest, there are very few standing issues left with CM7, and those tend to only occur on a case by case basis. However, it is an acquired taste, and rewards people who enjoy tinkering and learning about their phone and Android. Since it is so easy now to install CM7 and then return to Samsung ROMs if you need to, it makes sense to try it out and see how you like it.

rschenck said:
That is not a bug, just operating according to CM7 spec. When you plug in the charger, the phone boots up. You can then turn the screen off and go to Airplane mode if you wish it to charge more quickly. No big deal.
As for the rest, there are very few standing issues left with CM7, and those tend to only occur on a case by case basis. However, it is an acquired taste, and rewards people who enjoy tinkering and learning about their phone and Android. Since it is so easy now to install CM7 and then return to Samsung ROMs if you need to, it makes sense to try it out and see how you like it.
Click to expand...
Click to collapse
I didn't know it boots up completely, even in the case of a low battery. Some person said that as soon as it powers on, it finds out that the battery is low and hence powers off again. It keeps going on through it cycle and hence never powers up.
Still i'll look into it. Thanks.

Udayakiran said:
I didn't know it boots up completely, even in the case of a low battery. Some person said that as soon as it powers on, it finds out that the battery is low and hence powers off again. It keeps going on through it cycle and hence never powers up.
Still i'll look into it. Thanks.
Click to expand...
Click to collapse
Nope....untrue. It just boots up. The behavior is similar to the iPhone / iPod touch.
Sent from my GT-I9000 using XDA Premium App

After a 21-hour marathon session of flashing and re-flashing Eclair, Froyo, Gingerbread and CM7 on my phone, I finally managed to get CM7 working. After using it for a couple of days, I haven't found anything useful to justify the effort. Though the fact that devs are going into so much pains to develop this ROM is astounding. So I finally bought ROM Manager premium this morning to support the movement. Also I am planning to stick with CM7 for the predictable future. BTW, your guide for installing CM7 is amazing, rschenck. Thanks a lot.
As for the SIP feature, I tried it and found the results to be under-whelming. Quality is poor and implementation is half baked. I found Skype to be better. Also all my contacts are on Skype and none are using SIP. Finally battery drain was much higher than using Skype. Hence i'm not returning to SIP anytime soon. I feel Skype or Fring is better suited for my purposes.
Thanks for all your help, guys. And also thanks for introducing me to CM7.

[Q] black screen of death

I'm baffled and trying my very best to work out why I'm getting the BSOD on this phone. There appears to be no logic or pattern to when it occurs, so it's very difficult to diagnose what's causing it. I've now had two of these phones where it has occurred. The first one I took back and got a replacement under warranty. The second one worked like a charm on stock GB with no flashing of basebands, but since messing about and installing both CM10 and the latest ICS ROMS it's started happening again.
It seems to occur most when I go to charge the phone. It'll just die a death and I'll have to take the battery out before it even thinks about starting up again. Perhaps the most annoying thing of all is that it resets all time and dates and will then fail to use the network provided settings.
Has anyone else had this problem and found a solution that works long term? What about the cause? The strange thing about it is that it can go for a week without doing it...then, it'll happen twice in one day. And it's getting frequent to the point of being very irritating. I'm wondering If a different baseband would help. It currently detects it as unknown, but if memory serves I flashed the old 528 original stock baseband for use when I first installed CM10.

I have experienced it in every rom (I have experienced it in: cm10, all GB roms Ive tried, all ICS roms etc..) but not in cm 7 ... so I usually go back to that rom most of the time..

What baseband are you using? Whether or not it has anything to do with it I don't know. Desperately trying to find a fix. I'm thinking it can't be a rom issue. I'm just hoping it's not the phones hardware.
Sent from my LG-P990 using xda app-developers app

The worst thing is don't know how we carry cm10 bugs after flashing over different roms even with full wipe..I lost my amazing battery life after cm10 flash got new battery calibrated food full wow did smart flash still battery life drains like in 10% in hour even without any use....gross

This bug has been reported in the CM10 Bug Thread, you should take a look at it.
Basically the workaround is to turn on your screen before plugging the phone to a charger. There are users saying that they also have a lot of BSOD's when plugging the phone in CM10.

Don;t you think that questions has its own thread? Hope your eyes are still in good condition.
To prevent BSOD you can try hihger min cpu clock frequency.

Rayman96 said:
Don;t you think that questions has its own thread? Hope your eyes are still in good condition.
To prevent BSOD you can try hihger min cpu clock frequency.
Click to expand...
Click to collapse
You seem to be in a foul mood lately, passing such comments on all threads.
And for your info, increasing min cpu clock frequency has no effect on cm10 bsod. It may work in some roms, but not on this one.

Rayman96 said:
Don;t you think that questions has its own thread? Hope your eyes are still in good condition.
To prevent BSOD you can try hihger min cpu clock frequency.
Click to expand...
Click to collapse
Dude if you read my post im saying it occurs whether cm 10 or not. Changing clock frequency did nothing for me so thanks for pointing out the obvious. Like i say, it's a problem I've always had with this phone whether I was on stock gb or not and im getting sick of it. I just wondered if anyone knew the reason and a sure, concrete solution.
Sent from my LG-P990 using xda app-developers app

I am on CM10, and I never get random BSODs. I am on the 11/20 nightly.
For me, the one and only time a BSOD occurs is if my screen is off, and I plug in the charger (USB or wall), and the charger doesn't cause the screen to turn on automatically. If the screen turns on the moment the charger is plugged in, I won't get a BSOD.
My "solution" at the moment is to always turn on the screen before plugging in my charger. No more BSODs.
I used to get random BSODs even off the charger on earlier nightlies, but after 11/10 it was all right.

Mine is just the opposite....whenever i dont have it charging the bsod will appear sooner or later if its plugged in everything is ok...i tried changing min freq and clean installed all cm 10 nightlies so far but nothing has helped.
Sent from my LG-P990 using xda premium

haunterx said:
Mine is just the opposite....whenever i dont have it charging the bsod will appear sooner or later if its plugged in everything is ok...i tried changing min freq and clean installed all cm 10 nightlies so far but nothing has helped.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Same here with CM10, and some days worse than others. Although weirdly it was exactly the opposite with stock GB or CM7 - it would do it mostly while charging.

See this is my point.. Just how many folk are having this problem with the device? I might contact LG support to see if it's a known issue. I have it both whilst charging and not whilst charging. A Google of the topic does support a fair number of everyday stock users as having this issue. I just don't think it's a rom specific issue. The occurance is so spasmodic I think it's simply coincidental.
Sent from my LG-P990 using xda app-developers app

withoutwings said:
Same here with CM10, and some days worse than others. Although weirdly it was exactly the opposite with stock GB or CM7 - it would do it mostly while charging.
Click to expand...
Click to collapse
Same here. With CM7, very, very rarely would the phone just "die" with a black screen when charging. If I had it plugged in via USB to my computer and then immediately plugged into the wall charger, it would almost always BSOD. The only way to recover was to unplug it, pull out and re-insert the battery. This happened so rarely (especially if I always rebooted the phone after using USB) that it wasn't a problem for me.
With CM10, it will instead BSOD if it's just left idle with nothing connected. This happens 0 to 10 times a day with no logical pattern. Some days, I almost think the problem is gone, others the phone is almost unusable because it keeps dying. It has never had a BSOD while charging. This has happend with every nightly build of CM10. I've also had the problem where the caller/person I call just hears "dialup modem" type noise.
Monday evening I flashed SU660 V30c baseband. Still no BSOD as of today (noon on Wednesday). However it has gone this long without BSOD before, so fingers crossed. I have a "Made in Korea" P990 and it previously had Baseband 20I-EUR. Also going to do a few test calls to see if the noise problem is still there.

That's very useful to know. As you say the problem is so bizarre and so random that's almost impossible to know until weeks later if it's been solved for good. I just hope that final ics and baseband release will put the issue to bed once and for all. Can anyone confirm whether or not they have had this issue with the latest leaked ics baseband?
Sent from my LG-P990 using xda app-developers app

48 hours without a BSOD after flashing BB 30C however now calls have gone completely quiet. Neither party can hear a thing.
Back to the drawing board :silly:

Is anyone else's phove really hot when BSODed or is it just mine? When I was on Gueste 3.6 everything was ok until it BSODed, that's when cm10 came out, tried it, changed a few basebands and didn't have it for almost a month, suddenly a few days ago while I already returned to default bootldr and partition sizes on gueste 3.8ext3 with v28g bb I think (20121110)
Sent from my Optimus 2X using xda premium

UPDATE ON BSOD: I used Titanium Backup to freeze the stock browser (using chrome now lol) and for the past 3 days I haven't had a BSOD. Can people try to do the same and report what they find?

neovdr said:
UPDATE ON BSOD: I used Titanium Backup to freeze the stock browser (using chrome now lol) and for the past 3 days I haven't had a BSOD. Can people try to do the same and report what they find?
Click to expand...
Click to collapse
Truth is that I always use root uninstaller and remove the stock browser and this is the first time I haven't. Hmm... let's see...
Sent from my Optimus 2X using xda premium

I think BSODs occur when the relationship between rom, kernel and baseband is not so good.

Yes it appears to be that way. Unfortunately we don't have a BB for the P990 that works properly with ICS/JB ROM (call audio bugs etc.), which is why development of CM10 for P990 was abandoned. I'm now back on CM 7.2 and everything works as it should.

[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

Possible AOIP battery life issue???

OK, I know the battery life issue for 4.2 ROMs has been beat to death, but I've got something weird happening with AOIP on my phone that doesn't happen with other ROMs.
Basically, when I'm at work, the battery graph (from Battery Monitor Widget Pro) looks like in the AOIPbattery image attached below.
As you can see, it ate all but 3% of the battery in about 11 hours. At times Battery Monitor Widget Pro indicated it was using the battery at 11%/hr or more! This is while I'm at work, and the phone is not doing anything, just sitting on the desk with the screen off, connected to a wifi network but not doing anything with that either.
After a few days of that, I decided I needed to try something else. Originally was going to go back to my "old reliable" backup of 4.1 Rootbox, then thought instead that I'd try the last build of 4.2 Slimbean I still had as a backup. Restored that and got all my current data for the apps reloaded, seemed to be working fine (though still had the stuttering and dumping of apps issues, which was why I wuit using it). Thing is, it's using battery not much faster than the Rootbox one did. See the SlimbeanBattery image to see how it did at work. Same scenario (sitting on the desk, connected to wifi, screen off almost all day). The little bit of high usage was while I was at lunch, reading some web pages and rss feeds, so the screen was on for about a half hour.
So, I'm wondering what the heck is making it use batter so fast on AOIP? I tried several things before switching to Slimbean. Airplane mode made no difference. Used Wakelock Detector to see what was using it up, and it was some part of Android OS making AlarmManager go nuts with wakelocks.
I even backed everything up, factory wiped it a couple times, then loaded the base AOIP 6/3 ROM and loaded GAPPS to see if it still did it.
Nothing seemed to make any difference.
In one sense, I'm hoping the new build that keeps getting hinted at might correct some of this, but I kinda doubt it considering how everyone who brings up battery issues usually gets treated.

That's normal for 4.2 Roms
Sent from my HTC One X using xda premium

I see your point, why does one 4.2 room use that much more battery life then the other, it makes no sense to me. Maybe camcory can shed some light in this issue
Sent from my SGH-T679 using xda app-developers app

That's how my battery life has been on all 4.2 Roms. If aoip is worse for you then most obviously you need to switch Roms.
Sent from my HTC One X using xda premium

I really was hoping that you would see that there might be something wrong with AOIP and take a look at it at least, and not throw out the same tired response. While I do appreciate the work put into AOIP, forum thanks have not happened due to the refusal to notice the glaring issue that everyone else does.
I would really like to know if you even read my post, Smartguy? Seems not or you would have noticed that AOIP in that scenario eats battery three times faster than another 4.2 ROM. Why?
I'm not trying to upset anyone, just trying to hopefully get this resolved in an amicable manner.

Some people don't have battery drain issues that bad with AOIP. You should keep in mind that this phone was never intended to run anything above gingerbread. Every one of these phones handles issues differently, which is unfortunate, but if a Dev doesn't have the same issue it is hard to address. Its just how it is.
Sent from my SGH-T679 using xda app-developers app

Yes I read your post I wouldn't respond if I didn't. I have ran all the 4.2 Roms and with all of them I might get 10-11 hours of life. So no I don't see a problem with the ROM and if you do use another one.
Sent from my HTC One X using xda premium

smartguy044 said:
Yes I read your post I wouldn't respond if I didn't. I have ran all the 4.2 Roms and with all of them I might get 10-11 hours of life. So no I don't see a problem with the ROM and if you do use another one.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Wow hard to believe (well not really) this horse has been beat to death more times than a cat has lives! I'm pretty happy with battery life for the performance and OS I'm getting with AOIP. No hiccups and I have access to all the latest android features. The phone has a small battery anyway so if you want better battery life, time for a new phone or switch to a Gingerbread OS. I charge the phone once a day typically so that's hardly an inconvenience.

Thing is there is something major different in AOIP, as I can typically get just over 24 hours out of this battery in anything other than AOIP, including while I'm at work where the battery usage is a little higher than at home in every ROM I've tried (4.1 and 4.2 based included).
AOIP for some reason eats battery at more than 10% per hour only when I'm at work (less than 3% per hour at home) even when I haven't loaded any apps.
Every time I look at what is using it, it is either "cell standby" or "android os" that is using the most with the other of those two second and the screen usage following in a distant third.
I've tried to figure out what specific item in those two are the source, but it always comes back to some generic service or component in the os that is used by almost everything.
Really any advice to try and improve this, other than "use another ROM", would be appreciated.

Try putting your phone in airplane mode while at work and turn on WiFi. That might help with eating the battery. Especially if where you work had a poor cell reception
Sent from my SGH-T679 using xda app-developers app

get a new battery. i dont know what else to tell you. if you are getting 24 hours out of every other 4.2 rom youll be the only one. as i stated i get 10-11 tops on ANY 4.2 rom. so you have 2 choices new battery or different rom

Best thing to to is kill background data turn off Bluetooth WiFi sync and locations when not using your phone for a couple of hours. But your best bet would spring for an 2900mh battery.

tazmaniondvl said:
Try putting your phone in airplane mode while at work and turn on WiFi. That might help with eating the battery. Especially if where you work had a poor cell reception
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
That was the first thing I thought, but it acts the same.
Sent from my SGH-T679 using xda app-developers app

im going to vote you get a new battery if its that big a deal....:good:

go back to gingerbread OS. we gave you suggestions already. 1) new battery. 2) gingerbread OS. simple as that

I just don't understand this. Why is it that everyone refuses to see that there might be something wrong with AOIP compared to other _4.2_ ROMs?
I wasn't complaining about battery life on 4.2 ROMs, just noting that ONLY AOIP has this issue that I saw.
All other 4.2 ROMs used less than half the percent per hour as AOIP.
Telling me to just buy a larger battery when I don't have the money for it is not an acceptable answer. Neither is telling me to go back to the crapload called "gingerbread", whose only advantage is battery life, at the drawback of making everything else run like crap.
Guess I shouldn't have bothered, since it seems the developers may be able to code, but sure could learn a thing or two about listening to others with valid issues they should be addressing in their code.
Sent from my SGH-T679 using xda app-developers app

dwolfman said:
I just don't understand this. Why is it that everyone refuses to see that there might be something wrong with AOIP compared to other _4.2_ ROMs?
I wasn't complaining about battery life on 4.2 ROMs, just noting that ONLY AOIP has this issue that I saw.
All other 4.2 ROMs used less than half the percent per hour as AOIP.
Telling me to just buy a larger battery when I don't have the money for it is not an acceptable answer. Neither is telling me to go back to the crapload called "gingerbread", whose only advantage is battery life, at the drawback of making everything else run like crap.
Guess I shouldn't have bothered, since it seems the developers may be able to code, but sure could learn a thing or two about listening to others with valid issues they should be addressing in their code.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
sorry dude, i think your the one refusing to see. you seem to understand your way around, you sure your not doing something goofy on the install ?

dwolfman said:
since it seems the developers may be able to code, but sure could learn a thing or two about listening to others with valid issues they should be addressing in their code.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
maybe you can code in a "battery fix" and share it with all of us.

Just use a different ROM. Jesus Christ!

teerout said:
sorry dude, i think your the one refusing to see. you seem to understand your way around, you sure your not doing something goofy on the install ?
Click to expand...
Click to collapse
It didn't matter what I installed or didn't install. Once I got the phone at work with AOIP on it, it ate the battery three times faster than any other 4.2 ROM. One time, to rule out anything I was setting or loading, I loaded AOIP, gapps, then put in my account info and disabled auto updates with nothing else changed. It still did it.
As QA software tester, I know how to identify software issues and bugs. The only explanation for what I have happening is there is something going on with AOIP itself to cause this. Like I've already demonstrated other 4.2 ROMs only use the battery a little faster than RootBox 4.1 (RB about 0.6%/hr vs slimbean 4.2 using 1.1 to 1.5 %/hr) with that screenshot in my OP. AOIP uses about 2.5 %/hr at home but over 10%/hr at work.
In any case, it's quite apparent now that this little group of ostriches with their heads still stuck in the sand isn't interested in hearing the truth, so consider this a closed thread.
Sent from my SGH-T679 using xda app-developers app

[ROM][4.4.4][Unofficial] AOKP TF701T [06-27-1014][Nightlies]

Just wanted to share an unofficial build of AOKP for our TF701T's I did for myself.
Special thanks to Team AOKP for their wonderful rom!
Disclaimer: You flash it, you break it, you fix it. I will be update the builds weekly or so as new features are added into AOKP regularly.
Flash the same as any other rom. Use current Banks Gapps.
Known issue: I have enabled the glcomposer in the build.prop because the overall smoothness and battery life is greatly improved. However, because ASUS hasn't updated past 4.3, there may be occasional graphical glitches. You can disable the glcomposer by removing the one line in build.prop containing glcomposer in it BUT do try as it is first and see the difference for yourself. I have been using it for a couple weeks now and the graphical glitches are very small and barely noticeable.
Examples of where to see smoothness include: Scrolling homescreens. Swiping pages in App Drawer. Swiping pages in the widget drawer. Swiping away notifications while on homescreen. Swiping down notifications and quicktiles while on homescreen. Swiping to Google Now page in GEL launcher.
Latest Rom here:
ROM Download
Sources used:
Device: tf701t device tree
Kernel: Kernel tree
Vendor: Vendor tree

Anyone tried it yet?
Reports are welcome and help to get some traction going.!
Sent from my K00C using XDA Free mobile app

Paulicat said:
Anyone tried it yet?
Reports are welcome and help to get some traction going.!
Sent from my K00C using XDA Free mobile app
Click to expand...
Click to collapse
Excellent work. Very fast. No graphical glitches so far that i can see. Lets of options.:good:

It's great to see another ROM option for the tf701t! I just tried this out. The graphics really are quite smooth, and I love all of the customization options. Alas, as with cyanogenmod and cromi, Bluetooth functionality is severely diminished -- a mouse barely moves the cursor at all and a keyboard has severe typelag making it unusable. Any idea what's going on thereand how to fix it? I'm happy to be a guinea pig.

Awesome, glad to see other people trying this out!
I will post weekly build updates as often as possible.
Sent from my K00C using XDA Free mobile app

Im amazed how smooth it is. I guess this shows with this tegra4 theres still room for improvement which is a good thing.

It's very nice. The camera doesn't crash, and I the current version of Netflix doesn't crash. With some roms I've had to use 3.0.

lexelby said:
It's great to see another ROM option for the tf701t! I just tried this out. The graphics really are quite smooth, and I love all of the customization options. Alas, as with cyanogenmod and cromi, Bluetooth functionality is severely diminished -- a mouse barely moves the cursor at all and a keyboard has severe typelag making it unusable. Any idea what's going on thereand how to fix it? I'm happy to be a guinea pig.
Click to expand...
Click to collapse
I'll try and take a look, busy weekend/holiday up here. New build will be up in a couple days though.
Sent from my K00C using XDA Free mobile app

Absolutely no rush -- any work you do is appreciated and I'm perfectly happy to wait patiently I'll keep an eye here and try new versions as you post them.

lexelby said:
Absolutely no rush -- any work you do is appreciated and I'm perfectly happy to wait patiently I'll keep an eye here and try new versions as you post them.
Click to expand...
Click to collapse
So I just remembered I had an old Microsoft Notebook mouse 5000. I connected it and it works perfectly normal.
No lag or delay whatsoever...any chance you have another mouse to try?
Sent from my K00C using XDA Free mobile app

Paulicat said:
So I just remembered I had an old Microsoft Notebook mouse 5000. I connected it and it works perfectly normal.
No lag or delay whatsoever...any chance you have another mouse to try?
Sent from my K00C using XDA Free mobile app
Click to expand...
Click to collapse
Not a mouse, but I had another bluetooth keyboard, so I paired it up and gave it a try. Worked perfectly fine with no typelag :/ The one that doesn't work is a combo keyboard/touchpad. I don't think xda will let me link to a product on amazon, but it's a "tp cromeer" branded case with builtin bluetooth keyboard/touuchpad. Made for the N8000, but it fits the tf701t quite nicely.
Any idea why just this one device wouldn't work?

lexelby said:
Not a mouse, but I had another bluetooth keyboard, so I paired it up and gave it a try. Worked perfectly fine with no typelag :/ The one that doesn't work is a combo keyboard/touchpad. I don't think xda will let me link to a product on amazon, but it's a "tp cromeer" branded case with builtin bluetooth keyboard/touuchpad. Made for the N8000, but it fits the tf701t quite nicely.
Any idea why just this one device wouldn't work?
Click to expand...
Click to collapse
I actually have a mini combo keyboard touchpad I can try tonight.
My guess is going to be some sort of silly device incompatibility though...

I dont have any problems with this inexpensive bluetooth keyboard.
I do find though. I dont know if its possibly the kernel or android itself or if too many apps are running in the background. Input in general and reponsiveness is lost completely until reboot. It starts to lag all input I think. Like touch sensitivity etc. I wonder if anyone else has found this on to be the case on this device. Not sure if there is some app thatll restore it by killing processes possibly. Another thing I notice is that Android is running tonnes of threads. Compared to the few that run on linux. 600+ on android. Less then 100 threads on Linux usually depending on the distro. This rom right now has 900+ threads showing in htop. But it is still smooth as butter. Maybe thats not a big deal then.
EDITED

YayYouFixedIt said:
I dont have any problems with this inexpensive bluetooth keyboard.
I do find though. I dont know if its possibly the kernel or android itself or if too many apps are running in the background. Input in general and reponsiveness is lost completely until reboot. It starts to lag all input I think. Like touch sensitivity etc. I wonder if anyone else has found this on to be the case on this device. Not sure if there is some app thatll restore it by killing processes possibly. Another thing I notice is that Android is running tonnes of threads. Compared to the few that run on linux. 600+ on android. Less then 100 threads on Linux usually depending on the distro. This rom right now has 900+ threads showing in htop. But it is still smooth as butter. Maybe thats not a big deal then.
EDITED
Click to expand...
Click to collapse
I have not had any responsiveness issues with this device on any rom to be honest...
For clarity, are you seeing this problem on this rom or no?

Thank you for this ROM, it feels good to know that the TF701 has not been forgotten...:good:

myeepad said:
Thank you for this ROM, it feels good to know that the TF701 has not been forgotten...:good:
Click to expand...
Click to collapse
Cheers! I'll do what I can while I have this tablet!

Paulicat said:
I have not had any responsiveness issues with this device on any rom to be honest...
For clarity, are you seeing this problem on this rom or no?
Click to expand...
Click to collapse
It happens on all roms, but it would be a very subtle thing. I dont see it really as a problem. Just something that requires a reboot.

YayYouFixedIt said:
I do find though. I dont know if its possibly the kernel or android itself or if too many apps are running in the background. Input in general and reponsiveness is lost completely until reboot. It starts to lag all input I think. Like touch sensitivity etc. I wonder if anyone else has found this on to be the case on this device. Not sure if there is some app thatll restore it by killing processes possibly. Another thing I notice is that Android is running tonnes of threads. Compared to the few that run on linux. 600+ on android. Less then 100 threads on Linux usually depending on the distro. This rom right now has 900+ threads showing in htop. But it is still smooth as butter. Maybe thats not a big deal then.
EDITED
Click to expand...
Click to collapse
Yes -- I know exactly what you're talking about I think.
On any ROM I've tried, it happens. A fresh reboot always clears things up, but after running a few apps (and / or putting the tablet to sleep overnight perhaps?) the whole system lags a bit. General stuff, like switching programs and running apps like Tapatalk and Engadget (for example). I'm forced to kill apps manually, and that sometimes does the trick.
One thing I tried out yesterday that seems to be helping -- give this a shot too: in your developer settings, you'll see that you can restrict how many background processes are running. Currently, I have background processes limited to just 2 at a time (and also "strict mode" enabled)... and I have to say, I'm noticing a difference! Might take some more testing to see what the pros and cons of this are, but if it just means that I don't have background processes piling up on me, this might be a workaround?
Aside from that, has anyone tried Greenify with good results?
Sent from my K00C using Tapatalk

Trevor_g said:
Yes -- I know exactly what you're talking about I think.
On any ROM I've tried, it happens. A fresh reboot always clears things up, but after running a few apps (and / or putting the tablet to sleep overnight perhaps?) the whole system lags a bit. General stuff, like switching programs and running apps like Tapatalk and Engadget (for example). I'm forced to kill apps manually, and that sometimes does the trick.
One thing I tried out yesterday that seems to be helping -- give this a shot too: in your developer settings, you'll see that you can restrict how many background processes are running. Currently, I have background processes limited to just 2 at a time (and also "strict mode" enabled)... and I have to say, I'm noticing a difference! Might take some more testing to see what the pros and cons of this are, but if it just means that I don't have background processes piling up on me, this might be a workaround?
Aside from that, has anyone tried Greenify with good results?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Honestly guys, I don't see this issue using this AOKP rom...I've left it for a few days no reboot, and I don't see any slowdowns/lag.
On a brighter note, I have a new build ready to be uploaded tonight.
I messed up some merges for battery/charging and was struggling to sort it out the last couple days.
All good now.
New build will be up later tonight.

Paulicat said:
Honestly guys, I don't see this issue using this AOKP rom...I've left it for a few days no reboot, and I don't see any slowdowns/lag.
On a brighter note, I have a new build ready to be uploaded tonight.
I messed up some merges for battery/charging and was struggling to sort it out the last couple days.
All good now.
New build will be up later tonight.
Click to expand...
Click to collapse
Got it. In that case, I'll have to give this a shot! ☺
Sent from my Nexus 5 using Tapatalk