Related
I love this phone, its really the best phone money can buy @its price.
But like allways, there must be something there that must drive us/me crazy.
This phone losses 30% of its "beauty" because of the "touchscreen pushed makes CPU go to 100%" , losses another 40% for the "buttons working but the touchscreen freezes" bug and It wont unfreeze until you do a "lock and swipe unlock" .
So untill this phone gets an official update that fixes all the problems above (2.3, or 2.2 or 2.2.1, really dont care", I'm using this beauty just as a phone (30% calls and sms).
Additional notes: till now i've tried Pimev2 and now runing void (Thanks for your work Noejn).
What do you guys think about this ?
Kel_Sceptic said:
I love this phone, its really the best phone money can buy @its price.
But like allways, there must be something there that must drive us/me crazy.
This phone losses 30% of its "beauty" because of the "touchscreen pushed makes CPU go to 100%" , losses another 40% for the "buttons working but the touchscreen freezes" bug and It wont unfreeze until you do a "lock and swipe unlock" .
So untill this phone gets an official update that fixes all the problems above (2.3, or 2.2 or 2.2.1, really dont care", I'm using this beauty just as a phone (30% calls and sms).
Additional notes: till now i've tried Pimev2 and now runing void (Thanks for your work Noejn).
What do you guys think about this ?
Click to expand...
Click to collapse
About touch-100%-CPU-problem - this problem have many devices, but unfortunately, as other phones have about 50% CPU when screen is touched, optimus have 100%. Anyway, this main problem should be fixed in 2.3 android release.
About buttons-working-but-the-touchscreen-freezes problem I have to say, sorry. I didn't notice this problem at all.
And at the end I would like to add ARMv6-CPU, which brings too many limitations, one of the worst is Flash player support, which we will never see
who needs flash for phone, flash lite is enough...
The_ERROR said:
And at the end I would like to add ARMv6-CPU, which brings too many limitations, one of the worst is Flash player support, which we will never see
Click to expand...
Click to collapse
Some of the guys working/testing on the CM7 port say that flash works. Have you tried it?
I tested the ROM, but I can't seem to get an IP address from the router, so I can't install Dolphin to test flash
EDIT: And oh. So I could be of any help to this thread, I checked to see if the touchscreen cpu thing still exists, and yes, it's still there. Sorry :/
How could you figure that out since there are no 3d drivers and everything is supported by CPU ? I really hate it when somebody talks crap..
Sent from my LG-P500 using XDA App
The_ERROR said:
About touch-100%-CPU-problem - this problem have many devices, but unfortunately, as other phones have about 50% CPU when screen is touched, optimus have 100%. Anyway, this main problem should be fixed in 2.3 android release.
Click to expand...
Click to collapse
This has been fixed thanks to mok_os and his fine work
The_ERROR said:
About buttons-working-but-the-touchscreen-freezes problem I have to say, sorry. I didn't notice this problem at all.
Click to expand...
Click to collapse
I've made a video with how my touchscreen reacts when its stressed with multi touched
Kel_Sceptic said:
This has been fixed thanks to mok_os and his fine work
I've made a video with how my touchscreen reacts when its stressed with multi touched
Click to expand...
Click to collapse
why are expecting so much from a budget phone??
be satisfied with wat u have, its jst a phone :|
OK, I have written an app to attempt and stop call wonkyness on CM7 builds. Specifically the phone locking up when making and receiving calls.
It's my observation that it's the mic that causes the phone to lock up and so this app opens and closes the mic every minute to keep it "fresh". It's a long shot, but I can't seem to duplicate wonkyness with it enabled so I'm posting it for other to try.
Now after a few positive comments to help boost my confidence in the app, I've made it's own thread to make it easy to track comments.
Just install and run (or just reboot as it auto-start on boot). To disable, uninstall it.
Please post your results!
Change Log:
Version 1.4
Made service more persistent by adding notification bar. Turns out, Android was killing off the service when memory was running low causing wonk to surface.
Version 1.3
Can only be installed on internal memory. Needed to make sure the service can started up on boot. (Thanks to mjukis for pointing this out)
Version 1.2
Only dewonkificates when screen is off to avoid conflicts with any apps you may be using.
Removed debug logging
[Post edited because the wonkyness is still there and this .apk works fine to fix it]
Dude.... As best as I can tell in 20 minutes' time, this damn thing seems to actually work! Gotta tell ya how skeptical I was....but I'm pretty flippin' pleased right now!
Good looking out!!
Much appreciated for this app.
While it's still too early to say it's 100% working, so far so good.
I have had the wonk since build 3 to 23 (except for 16).
I will keep testing and report back often.
That's great news and I'm happy that it looks like it's working for people. I was on the edge of rolling back and this was a desperate attempt to fix it.
Agree with the op. Can't say for sure its the miracle I've been waiting for... but 4 calls in (admittedly 2 from myself, ) no wonks. When I'd expect all to be wonky
If this 'wonklessisity' continues you will surely become supreme ruler of xda!
Will report back soon.
Sent from my Nexus One using XDA App
TheMasterBaron said:
That's great news and I'm happy that it looks like it's working for people. I was on the edge of rolling back and this was a desperate attempt to fix it.
Click to expand...
Click to collapse
What are your thoughts and battery impact?....and would some timeframe greater or less than 1 min. factor in??
Does this fix it?
http://review.cyanogenmod.com/#change,2642
shaggy-h said:
Does this fix it?
http://review.cyanogenmod.com/#change,2642
Click to expand...
Click to collapse
No, that's a different problem.
Sent from my Nexus One using Tapatalk
makelegs said:
What are your thoughts and battery impact?....and would some timeframe greater or less than 1 min. factor in??
Click to expand...
Click to collapse
Currently I can't see any measurable battery drain. Dewonkificator doesn't even show on the About phone->Battery use screen. Increasing the time between dewonkification might be work, but since battery doesn't seem to be a issue and we don't know what the source of the problem is I don't think its worth risking or investigating.
I also believe it have something to do with the mic, since all apps that use it have the same freeze, and it seems to work for me. Thanks
TheMasterBaron said:
Currently I can't see any measurable battery drain. Dewonkificator doesn't even show on the About phone->Battery use screen. Increasing the time between dewonkification might be work, but since battery doesn't seem to be a issue and we don't know what the source of the problem is I don't think its worth risking or investigating.
Click to expand...
Click to collapse
Seems reasonable enough, to me.
TheMasterBaron said:
Currently I can't see any measurable battery drain. Dewonkificator doesn't even show on the About phone->Battery use screen. Increasing the time between dewonkification might be work, but since battery doesn't seem to be a issue and we don't know what the source of the problem is I don't think its worth risking or investigating.
Click to expand...
Click to collapse
Maybe watchdog would be a better app for checking. Would give us a better idea of CPU use. Also juice plotter may help see prior and after install battery consumption
I've tested it,and havent got any wongkiness for today. I think its working...
Sent from my Nexus One using XDA App
Got source?
fitsnugly said:
Got source?
Click to expand...
Click to collapse
Added to the OP
TheMasterBaron said:
Added to the OP
Click to expand...
Click to collapse
gracias!
You deserve an E-Cookie for coming up with such an awesome name
Wonky just visited me when my wife called. Installed your dewonky app for testing.
Thanks.
This bug is the reason I got off CM7 nightlies, so damn annoying. Maybe this is a Gingerbread thing rather than a Nexus S problem cause the Nexus S is supposed to be rebooting itself while in calls as I'm sure everyone knows.
I have tried finding answers on my own but I haven't been able to find anything that has worked on the Meanbean forum or anywhere else. I'm obviously on the latest Meanbean Rom.
My issues:
1. When I am in my vehicle using Waze for navigation (the issue would likely happen no matter what I'm using for navigation but I haven't tested it) I either get a pop up alert that my phone is using more current then the charger can supply or I don't get the alert and my battery percent drops a couple percent every couple of minutes, eventually my phone goes dead on a long drive.
I have tried the following with no success: OEM Charger, multiple aftermarket 1 and 2 amp chargers that were hacked (so that phone allows AC Charging instead of the limited USB charging) and unhacked, changed governors/kernels to power conservative versions, removed any overclocking, kept phone cool and out of sun, and wiped/clean installed Meanbean.
2. When I go running and turn on my workout tracking application (Runkeeper) and then I try to turn on music, Runkeeper shuts off. This same issue happens no matter what application I use, if I'm listening to music and turn on the flashlight, the music application quites working in the background. I have also duplicated this while driving by running torque and then opening any navigation application, Torque quits, or whatever is not being focused/interacted with in the front of the screen is terminated (or crashes for all that I know). I have duplicated this with almost every application that I run and the same thing happens, the background application is terminated.
I have tried the following with no success: I have flashed the Meanbean Rom zip that allows users to create a white list of applications that shouldn't be terminated. I didn't input the entire application name but according to the instructions, using just "waze" or "runkeeper" should work the same. I have also tried changing governors/kernels, adjusting multitasking memory settings, wipe/fresh install of Meanbean, and I have also used the application Pimp My Rom to keep the specified application in memory using a tweak in the application.
If anyone has any suggestions for either of these issues I would greatly appreciate it. At this point I don't know what to do; I'm getting ready to drive cross country and the charging issue will be an absolute deal breaker and I also go running everyday and not being able to listen to music while tracking my run is also a deal breaker.
Have you tried an aosp rom? That should at least fix the closing apps, and maybe the charging issue too. If you look for one with a Fast Charge option, that would be something to try also...I know Carbon has it, not sure which others do
Sent from my EVO LTE
Have you tried it in another vehicle, charging that is, maybe the outlet in your car can't output enough juice and it isn't the charger at all. I know when I stay in hotels, a lot of the lamps with an outlet show that they can only output .5 amps. Just another suggestion to try. I run waze in my Jeep and it charges fine with a cheap BB charger with MeanBean.
Sent from my icrap 2 using Tapatalk HD
Kernels have the fast charge option.
Sent from my EVO using Tapatalk 2
premo15 said:
Have you tried an aosp rom? That should at least fix the closing apps, and maybe the charging issue too. If you look for one with a Fast Charge option, that would be something to try also...I know Carbon has it, not sure which others do
Sent from my EVO LTE
Click to expand...
Click to collapse
I tried CM10 when it was first released for our phones but I left because it seemed to have a lot of bugs to work out. Is it stable now?
akboy82 said:
I tried CM10 when it was first released for our phones but I left because it seemed to have a lot of bugs to work out. Is it stable now?
Click to expand...
Click to collapse
Yeah, I think so...pretty much every aosp rom for our phone is built from cm source (if not all) and I've been using several of them as daily drivers for a couple of months. Try using the komodo kernel also, as tl stated above the fast charge functionality is part of it, not the rom...plus it's just an all around badass kernel.
Sent from my EVO LTE
premo15 said:
Yeah, I think so...pretty much every aosp rom for our phone is built from cm source (if not all) and I've been using several of them as daily drivers for a couple of months. Try using the komodo kernel also, as tl stated above the fast charge functionality is part of it, not the rom...plus it's just an all around badass kernel.
Sent from my EVO LTE
Click to expand...
Click to collapse
You think I will be able to get away with a dirty flash, since im on on a sense rom?
akboy82 said:
You think I will be able to get away with a dirty flash, since im on on a sense rom?
Click to expand...
Click to collapse
No, you'll need to do a full wipe for best results.
Sent from my EVO LTE
Again if you want to stay on sense there are a couple of kernels that can help with both issues. Mine and flar2s. They have adjusted lowmemorykiller settings and usb fastcharge.
Sent from my EVO using Tapatalk 2
thicklizard said:
Again if you want to stay on sense there are a couple of kernels that can help with both issues. Mine and flar2s. They have adjusted lowmemorykiller settings and usb fastcharge.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I'm using yours right now but I'm still having the same problem for some reason. Is there something I'm not doing right when using your kernel on meanbean? Is there a trick to using the white listing built into meanbean when using your kernel?
I'm also wondering if the charging problem is related to the power output of my vehicles cig lighter since someone earlier suggested that could be an issue but I also have my doubts since my truck has 110 volt plug built into it and I have the same issue if I use my house charger...
Did you enable fast charge? If you use kernel tuner you can enable it in misc menu. Also with kernel tuner there is a menu oom adjust that and see if it helps there are many options and 2 of them being multi tasking.
Sent from my EVO using Tapatalk 2
thicklizard said:
Did you enable fast charge? If you use kernel tuner you can enable it in misc menu. Also with kernel tuner there is a menu oom adjust that and see if it helps there are many options and 2 of them being multi tasking.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Is that available in the free version or only in the paid?
Thanks again, I will play with all of that this weekend. If I can get these two issues sorted out my phone will be perfect for me..
akboy82 said:
Is that available in the free version or only in the paid?
Thanks again, I will play with all of that this weekend. If I can get these two issues sorted out my phone will be perfect for me..
Click to expand...
Click to collapse
Kernel tuner is free. All those features are available
Sent from my EVO using Tapatalk 2
Hey all
Having a few troubles with my gyroscope. Here's the story so far.
I first noticed the issue when seeing significant sensor usage by 'Android System' - see screenshot of GSam. I started digging what part of 'Android System' it could be. GSam Battery monitor confirmed that the Gyroscope is always on during any screen on activity - see screenshot. This never used to be the case, as a month or so back I never had any sensor time used in this app. So something is holding my sensor on. Using BBS, and conferring which packages are included in 'Android System', I can narrow it down to 'system', 'com.android.systemui', or 'surfaceflinger'. (I think.) - see screenshot. Note: during screen off times, the sensor is not active at all.
I've thoroughly googled/searched xda for correlations of these to the gyroscope. This is where I've come to a dead end. I can't find any info on what it actually is that's forcing my gyro sensor to stay on.
The sensor is on with the screen regardless of auto rotation, all 'flip to mute', 'flip to silence'...etc off. Also in chrome, the tilt to scroll is off. I'm stumped.
These links are links which I've read, but nothing seems to bite me with a solution:
http://forum.cyanogenmod.org/topic/38291-orientation-sensor-is-using-a-lot-of-cpu-time/
http://developer.android.com/guide/topics/sensors/sensors_motion.html
http://forum.xda-developers.com/showthread.php?t=1755180
Any bright ideas? All suggestions are appreciated.
(Note that in one of the screenshots, '....androsensor..' has nothing to do with the forcing of the sensor on. It was an app I was hoping to log the sensor use with. It was useless.)
Does it happen with stock (or a clean install of the rom & kernel you're using) ? Could be something unknown that's funky in your current install. Could be the sensor itself on the fritz if it does happen with both of those as well.
MistahBungle said:
Does it happen with stock (or a clean install of the rom & kernel you're using) ? Could be something unknown that's funky in your current install. Could be the sensor itself on the fritz if it does happen with both of those as well.
Click to expand...
Click to collapse
Mmm not too sure about stock. It's been a looooong time since I've been stock. Might have to try a clean install of Rootbox first though. I already flashed back one of my reliable nandroids which I always revert to if I have issues, so I'd kind of neglected that side of things and just assumed that my bullet-proof nandroid would fix it if that was the issue. I'll try a clean install of RB though. Just annoying coz there should be a way to figure out what's actually using the sensor, but I haven't found one.
Yep that's an unusual one, you would have thought you'd have nailed it given everything you've looked at (and you've been pretty thorough).
MistahBungle said:
Yep that's an unusual one, you would have thought you'd have nailed it given everything you've looked at (and you've been pretty thorough).
Click to expand...
Click to collapse
Thanks for the compliment, especially coming from you I'll have to re-flash tomorrow, I'm on 13% battery now... better charge a bit before flashing or I could face worse issues than a gyro stuck on will report back when I know more.
Hopper8 said:
will report back when I know more.
Click to expand...
Click to collapse
Ok, so I flashed a clean install of Rootbox 4.0 with dorimanx 9.16. (flashed gapps as well). Gyroscope was still stuck on with the screen on. As a last thing to try before full stock, I flashed the kernel that comes bundled with rootbox. Fixed!... But what about Dorimanx? I've used that kernel for about 3 months now. 9.16 I've used literally since it was released, with no dramas.
To make sure that it was the problem, I flashed back Dorimanx 9.16. Gyro on. Reflash Stock kernel: gyro off. Using the stock kernel isn't really an option. Dorimanx allows so much more tweaking plus bln etc
I'd post in the Dorimanx thread, but I imagine it won't be received too well. @MistahBungle any ideas?
Edit: And yes, I've tried searching both the Dorimanx dev and discussion threads for similar issues. No luck
UPDATE: So, with more screwing around with kernel wipe scripts, I managed to make the gyro turn off with both dori and stock rootbox kernels. All was going well until it turned back on a few hours later. I don't know why. Now I can't get it to turn off at all.
Before it turned on, I'd only been tapatalking. A while later I played a bit of hill climb racing (game), then checked GSam to see if the gyro was active, and it was. The game doesn't actually use the gyro, so this is a long shot... Is anyone able to check for me if this also makes their gyroscope turn on (check using GSam battery monitor as in OP screenshot). Much appreciated.
Since then I've uninstalled hill climb racing, wiped, reflashed dori, & stock kernel, but nothing has made it turn off.
Stumped again.
Sent from my GT-P7510 using Tapatalk 4 Beta
Got me stumped as well Hopper, narrowing it down to a Dorimanx-specific issue looked promising, but that's now obviously not the case.
I'd do that clean install of stock (take your pick re: ICS or JB, just stay away from 4.0.4) I was talking about yesterday.
MistahBungle said:
Got me stumped as well Hopper, narrowing it down to a Dorimanx-specific issue looked promising, but that's now obviously not the case.
I'd do that clean install of stock (take your pick re: ICS or JB, just stay away from 4.0.4) I was talking about yesterday.
Click to expand...
Click to collapse
Literally had just turned wifi on to download a stock firmware. I will attempt to flash with mobile Odin (first time) so I can everroot.... Can't have an unrooted phone might flash the 4.1.2 I was on before root. Again, I'll post updates as I know more
Sent from my GT-I9100 using Tapatalk 4 Beta
Great minds eh ? ;-D Yep I hear ya re: having a rooted phone. Let us know how you go; this is a really interesting problem & makes a nice change from the 'OMGZ ! I broke my phone because I couldn't be bothered learning or taking proper care !' threads we usually get on here
Tell you what, if you still find the problem persist on stock, I'll DL that game (or something similar that makes use of the gyro) & see if I can replicate it on my phone (running RB 3.9.1 & Dori 9.12; Yes, I know I'm a bit behind. I like stability ). I must admit I don't play games that make use of it on my phone, so I've never really noticed anything wrong like this before.
Yep well I'm kind of enjoying it too. Now I have an excuse to buy & use mobile Odin alright, thanks! You've got yourself a deal. I won't get a chance till tomorrow, but I'll post my findings!
Sent from my GT-I9100 using Tapatalk 4 Beta
Hopper8 said:
I'll post my findings!
Click to expand...
Click to collapse
Ok, so the fun of Mobile Odin made me flash stock tonight. Aaaaand gyroscope is on still, but only when screen is on (see screenshot). This is with: stock LSH (4.1.2) firmware (rooted using Everroot in mobile odin during flash). Everything (I mean everything) is unchanged, apart from installing GSam to see if the gyro was being used.
The only conclusions I can think of:
- My hardware is faulty
- The gyroscope is always on, checking to see if I'm in landscape mode for videos (as in how the device doesn't need to be on auto rotate to watch a youtube video etc. in landscape). If this were the case, then wouldn't everyone's gyro's be on 100% of the time though?
Any enlightenment appreciated.
Edit: now I remember why I hate touchwiz :/
OK Hopper
Firstly, I hate you. I couldn't stop playing that goddamn game ! (I had to freeze it).
Secondly, I played it for 25-30 mins solid & no sign of gyro in GSam (I also have screen rotation, all the flip options in alarms turned off, etc).
So that doesn't seem to be the culprit.
I
MistahBungle said:
OK Hopper
Firstly, I hate you. I couldn't stop playing that goddamn game ! (I had to freeze it).
Secondly, I played it for 25-30 mins solid & no sign of gyro in GSam (I also have screen rotation, all the flip options in alarms turned off, etc).
So that doesn't seem to be the culprit.
Click to expand...
Click to collapse
Many many thanks for that and apologies for your addiction hmmm. Well I literally have no idea what to try now, I'm completely out of ideas.
Any bright ideas to try? Or a way of logging what is actually using the gyro? I couldn't find one.
Ps. Try to unlock the monster truck as soon as you can
Sent from my GT-I9100 using Tapatalk 4 Beta
Alright, so maybe time for a bit more drastic action... I'm thinking of disabling the gyroscope. I don't use tilt at all, so I have no need of it. Only problem being, I can't find a way to disable it. I've searched xda, as well as plain google. @MistahBungle, I don't suppose you've come across a way to do that in your vast experience?
Sent from my GT-I9100 using Tapatalk 4 Beta
Logcat during the period the gyro seems to be most in use might be helpful, but I'm no dev & not really au fait with deciphering them (Hopefully someone else who is might read this thread).
No. I can't say I've seen a problem like this or seen a way to disable the gyroscope. You'd need to talk to a dev I reckon. Given you've been using RB & Dori, maybe try the discussion threads for those, assuming the dev(s) read them & ask the specific question there, both about whether logcat would be useful & whether the sensor can be disabled by some kind of hack.
Sorry I haven't been able to help more I'm sure this is really frustrating for you & will be keeping an eye on the thread to see how this thing progresses & if you eventually find some kind of solution (Also happy to test anything else out at this end again that might help).
Well if that's the case, all I need to do is logcat for a minute while my screen is on. Guaranteed the gyro will be on! I will take some time & post in those threads. Thanks so much for your help! I will let you know if I manage to fix it, or if there's something else to test thanks again!
Sent from my GT-I9100 using Tapatalk 4 Beta
No worries, happy to help If you need me to try anything else let me know & keep us posted on how you go with it in this thread.
Update :
Since posting here, I posted in the dorimanx discussion thread, no replies (not that I really expected any). No progress with the problem, until yesterday.
I flashed NeatROM out of curiosity to see what it was like, with Apolo kernel. Gyroscope is off. I have no idea why, seeing as gyro was locked on with stock ROM. Now I'm even more confused... I would have thought it was possibly a problem which arose & is a result of flashing a 4.2.2 ROM, but @MistahBungle, you don't have this issue.
Apart from knowing that it is possible for my gyro to be off, it hasn't helped at all, unless I'm missing something....?
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
MistahBungle said:
No worries, happy to help If you need me to try anything else let me know & keep us posted on how you go with it in this thread.
Click to expand...
Click to collapse
AHA!! I think I might have a solution.... @MistahBungle, are you still ok to test something?
I managed to make the gyroscope go off by using hawkerpaul's ROMNuke script, and flashing stock. Then, I used the script again and flashed Rootbox, and the gyro stayed off. I flashed Dori 9.16, sensor was off. I set up Dorimanx in Stweaks how I usually do, and my gyro was on.
I started configuring Stweaks one setting at a time, checking with GSam battery monitor to see if the gyro was turned on. The gyro turned on when I configured the 'Screen' tab, specifically:
Set the 'min_bl_level' to 100 and set my brightness to 'Auto'
I re-nuked my ROM, and did the same test, with exactly the same result. I have since found that setting brightness to 'Auto' will trigger the gyroscope. Note this is only on Dorimanx, it won't trigger on any other kernels. Although it won't trigger on another kernel, the gyro will sometimes seem to stay on, as if the trigger is 'carried over' from another kernel. I don't know when or why though.
Summary:Setting brightness to 'Auto' triggers the gyroscope on Dorimanx. MistahBungle, could you confirm this? If not, next step is to flash a heap of different Dorimanx's kernels and see if some don't trigger it.
I've just turned my phone on auto-brightness, running Dorimanx 9.12. I'll check GSam in a couple of hours to see if the gyro has been running for any length of time (and I won't do anything with the phone that actually requires the use of the gyro).
Still not ready but people wanted it as is to play with until i fix up the rest. You can get data on this build easy if you follow my instructions.
Warning:
Data hand offs, signal strength, MMS, phone call reliability, and it randomly sending your personal data to the NSA are all potential bugs.
MIUI v5 3.8.23 ported from bmarko's i9505 ROM.
*Gapps are included for now until I get it all worked out (I hate flashing multiple files)
Bugs:
Probably a lot. Report them.
Understand this is a WIP and not my main project. I take no responsibility for your phone or your ability to fix our restore anything. Always make a backup and always keep Odin packages ready.
Instructions:
Download
Backup
Install
Reboot
Skip through the setup in the beginning
Go to settings
Network settings
Subscription
It will auto set to NV. You need to set it to UIM.
Reboot.
Open phone info app
Set your network to CDMA/GSM/LTE
Wait a minute
You should be connected to full 1x/3g/4g now
Then go and add your Google account in the settings and play with the ROM.
Note: on every reboot you will need to go back into phone info app and reselect your network settings. This is because the framework doesn't have the ability to default to CDMA service yet.
Note 2:
No other kernels work on this yet. Don't try, you will boot loop.
Download link:
https://copy.com/tjs7D
Pictars:
sent from my Verizon Galaxy sIV
Pictars: redux
sent from my Verizon Galaxy sIV
And 3
sent from my Verizon Galaxy sIV
downloading now! thanks so much for your work man
Now we're talking! Love some MIUI!
Sent from my SCH-I545 using Tapatalk 4
I think I love you.
Guess I'm not sleeping tonight!
Sent from my SCH-I545 using Tapatalk 4
Running very well so far, just had this weird problem with a phone call where I couldn't hang up
alekurkudi said:
Running very well so far, just had this weird problem with a phone call where I couldn't hang up
Click to expand...
Click to collapse
That's part of the hand off issue I was talking about. Until its fixed if you want to keep using it title airplane to hang up :good:
sent from my Verizon Galaxy sIV
Have been waiting for this... Thanks a lot...
Sent from my SCH-I545 using xda app-developers app
Dubbsy!
Good to see this thread up. I'm still going to get that donation to you asap, my girls tire blew, so had that unexpected expense pop up.
Glad to see this so much further than I got, and appreciate you taking on my request!
One more reason to not trade my G 4
Sent from my SCH-I545 using Tapatalk 4
ahhhhhhhh nice
I would like to mention as many of you are probably aware that Google is draining some major battery life off my Galaxy S4. I had 5h 32m off the charger with only about 30 minutes screen on time and had 14% battery. After that I watched a youtube video, and the next thing I knew I had 4%. I know this is a work in progress, so believe me i'm not complaining. I love MIUI. I know this isn't ready to be a daily driver yet.... but I love MIUI so much that I will keep it one more day just to test it and see how I like it. If these battery issues were fixed, I'd use it as my daily driver regardless of bugs. Keep up the good work! I can't wait for the next update
Basketballhero75 said:
I would like to mention as many of you are probably aware that Google is draining some major battery life off my Galaxy S4. I had 5h 32m off the charger with only about 30 minutes screen on time and had 14% battery. After that I watched a youtube video, and the next thing I knew I had 4%. I know this is a work in progress, so believe me i'm not complaining. I love MIUI. I know this isn't ready to be a daily driver yet.... but I love MIUI so much that I will keep it one more day just to test it and see how I like it. If these battery issues were fixed, I'd use it as my daily driver regardless of bugs. Keep up the good work! I can't wait for the next update
Click to expand...
Click to collapse
make sure you disable nfc!
asf1187 said:
make sure you disable nfc!
Click to expand...
Click to collapse
Does NFC on this build drain battery more than it does on other roms?
Will this work on us cellular with a converter?
Sent from my SCH-R970 using Tapatalk 4
Franzferdinan51 said:
Will this work on us cellular with a converter?
Sent from my SCH-R970 using Tapatalk 4
Click to expand...
Click to collapse
Potentially. I didn't include all CDMA APNs on this build like I normally do on my builds. But changing APNs isn't hard.
Getting data itself to work would be the same process as I laid out in my op. If it doesn't work out after you try it I'm sure I could get together with the gurus over at teamusc and we could work something out.
Let me know.
sent from my Verizon Galaxy sIV
Awesome I'll give it a try tonight or tomorrow night and message you with the results
Edit: downloading now results after possible restore lol I hope this works
Sent from my SCH-R970 using Tapatalk 4
I have NFC on and am getting good battery life. For this being beta it runs a lot better than many other roms I have tried. Great work!
PS just need to take care of the phone problem