I'm looking to get some information on my what can be done to fix the Data Usage counter on my wife's i927R (Rogers) running the stock GB os. Currently any data counter application that is put on doesn't actually keep track of 3G/4G data correctly.
I have been reading up on just upgrading it to ICS but I recently read all about the phone call issues after it goes to sleep so I'll be holding off on that upgrade to that gets worked out.
I did notice that there were some GB Kernels (like ardatdat's) that say they fix the issue but they also do a bunch of other things like overclock which i'm not interested in.
Is there a way to just patch the existing stock kernal to correct the data counter issue? If so can you point me in the right direction of the files and steps to update?
Any help would be great.
Thanks
If you want a count of your data, message, and phone calls and are on att, dial *3282# into the phone and press call. It is very accurate and gives you the data in the form of a text message. Not sure if this is what you want, but this is what I do.
Sent from my SGH-I927 using xda app-developers app
The standard stock kernel can't be given that feature, you have to recompile it from source and then hope you get a working version. We are a small group compared to the other phones as our model is not quite as epic as the original as the original captivate galaxy s is still a great phone and being an attention whore still lol..
But we are All trying to do our best to get more mods out there.
I personally use ICS 4.0.4 stock (custom modded to my needs)
And run lite kernel 1.1.1 you may want to try an update to your ROM from gingerbread to ICS and I beleive at&t launched an official update with samsung, maybe try it and see if it helpa
Thanks for the replies but i'm not on AT&T but rather Rogers in Canada.
Also, I would update to ICS but from the other ongoing threads there is an issue with the phone not receiving calls\sms on those roms once it goes to sleep mode so i want to avoid that until it is fixed.
From the sounds of it the only solution is to flash a new kernel (such as ardatdat's) thats specifically says it fixes the issue. Perhaps I can figure out how to change overclock settings so that it runs stock speeds.
To flash a Kernel do I just use Odin like a Rom flash? Are there any How To's on Kernel flashing? I haven't found one around here for the glide.
Thanks
The AOSP ROMs default to stock clocks, why haven't you upgraded yet?
Craigatitus said:
Thanks for the replies but i'm not on AT&T but rather Rogers in Canada.
Also, I would update to ICS but from the other ongoing threads there is an issue with the phone not receiving calls\sms on those roms once it goes to sleep mode so i want to avoid that until it is fixed.
From the sounds of it the only solution is to flash a new kernel (such as ardatdat's) thats specifically says it fixes the issue. Perhaps I can figure out how to change overclock settings so that it runs stock speeds.
To flash a Kernel do I just use Odin like a Rom flash? Are there any How To's on Kernel flashing? I haven't found one around here for the glide.
Thanks
Click to expand...
Click to collapse
I come from rogers too.. the ICS update will work fine for you and overclock doesn't affect anything. I was using literom with lite kernel 1.1.1 before upgrading to cm10.. then pacman 18.2 and now on liquid smooth
You should at least upgrade to Ics.. phone runs faster and smoother and GPS is fixed in literom too.
What version of GB are you using ? I upgraded to the latest GB first when I got my glide and I don't recall data stats not working
The current os is 2.3.5 (Kernel 2.6.36.3), The latest one available for the phone through Kies. All the data usage counting apps do not work on this phone. They all report about 1/1000th of the actual usage. Wifi data reports correctly but thats not what's important.
roothorick: I searched for "AOSP Rom" and what i found was an alpha build with a bunch of known issues. As this is my wife's phone, this wouldn't go over well. Keeping the phone looking and functioning the same as much as possible is key.
yohan4ws: I was planning on upgrade to ICS but now i'm reading the threads about the issues with the phone not receiving calls or sms once it goes to sleep. That is unacceptable as it is the main purpose of having a phone. So you aren't experiencing any "no radio wake" issues with your setup?
Related
As the title says, should i stay with my 2.1 (i did clock workmod and using Mobile AP to pair it to my Samsung Galaxy Tab) or should i go and update to 2.2(EB13)
the question is cuz i have heard a lot of bad thing about the update (2.2), that it doesnt work properly, problems with data connectivity, problems with the sd card and that even Samsung pulled out the update from their web page cuz of the complaints etc etc etc...
dont know what to do
guy's what do you recommend
i just what to keep using my Mobile AP
The stock Eb-13 is horrid, it does have problems, but if you flash a good stable rom, you'll be able to use Wireless Tether from marketplace and have the same setup. Froyo enables so many more features than Eclair so I would update.
Syndicate ROM will be a perfect ROM to run once he updates his ROM (mostly tomorrow) to v1.0.1.
I would honestly upfmgrade to eb13. Yeah it has some problems but most of the problems have been patched. You could stay on stick rom and flash a.custom kernel that has the patches into it or flash a custom rom that will have the kernel built into it. As far as best ron's its up to but I like bonsai rom. Version 3.0.1 is getting ready to be released as I am a beta tester and it's very fast and stable and has all the carrier IQ removed. Good luck with your decusionr
Sent From My Evo Killer!
But if i get EB13 , would i b able to get Mobile AP, i like it cuz it pairs easy with my Samsung Galaxy tab and with tether my tablet never find my Epic 4g (wifi)
were can i download that custom EB13 ??? whats its name??? Syndicate rom it is??
I'm having the same issue. I'm wondering if I should even update to EB13, I just received a replacement Epic through Sprint and I don't want to run the chance of ruining my new phone with EB13. Especially with the data connectivity bugs, sd card, profile and prl not updating etc... (which I don't believe I had any of these issues, but not sure I want to take the chance). Is it OK to update, really?
dcraig723 said:
I'm having the same issue. I'm wondering if I should even update to EB13, I just received a replacement Epic through Sprint and I don't want to run the chance of ruining my new phone with EB13. Especially with the data connectivity bugs, sd card, profile and prl not updating etc... (which I don't believe I had any of these issues, but not sure I want to take the chance). Is it OK to update, really?
Click to expand...
Click to collapse
EB13 was working fine for me, noticeably faster! Although perhaps not so good a battery life... but I just made the jump to Syndicate. Couple issues, but they're being worked through and it is fantastically efficient as is. But if you update either way, do a fresh install. Avoid most of the issues you've read about by doing a clean install.
In my opinion I would upgrade, You cant make judgement on a few people mishaps. If anything you can just root & rom, after you upgrade.
First Android phone, so I still getting up to speed so hoping someone could answer a couple quick questions. I'll start with the questions and then give the history.
1) How do you determine what ROM you have installed?
2) Any ideas why 4G won't connect? Is there any way to troubleshoot this?
3) Is there anyway to tether on 4G?
So I dove right in after purchasing this phone and flashed a ROM (Zedomax) so I could tether. After installing this ROM my battery life went down the drain and it wouldn't hold a charge for more than 6 hours.
So then I flashed the EG30 stock kernel and my battery life returned to normal. Still wanting to tether I tried another ROM (don't remember which one). This ROM had the same battery issues so I once again flashed the stock kernel back to my phone.
So now my battery life is great, but 4g won't connect (i'm in NYC) for a few days now. I've tried pulling battery, want what not to no success.
I believe I am running the stock kernel, but to my surprise I still have root access. No triangle on the home screen and ODIN says I'm using the Samsung Official binary.
Just to clarify, you are flashing kernels, not ROMs. Zedomax is a kernel, EG30 is a kernel, etc. You can find your current kernel version under Settings > About phone > Kernel version.
Also as an FYI, I wouldn't be going all willy nilly flashing kernels that you can't remember the name of. I'd have to imagine that's a good way to possibly brick your phone or have problems like you are with 4G.
I'm no expert on this stuff by any means but I'd probably recommend flashing Bubby's stock kernel or chris41g's version of it that is packaged up with CWM. These will get you back to the stock kernel (assuming you're not there already) and probably get your 4G working. Otherwise you probably need to update your PRL or something along those lines. Someone who actually knows more about this stuff (i.e. not me) may have a better suggestion for you.
Thanks.
Kernel version is 2.6.35.7-SPH-D710.EG30-CL435734
Is that stock?
walkingcrow said:
Thanks.
Kernel version is 2.6.35.7-SPH-D710.EG30-CL435734
Is that stock?
Click to expand...
Click to collapse
Yep! 10 char
Cool.
So flashing to chris41g's or Bubby's kernels probably won't help me. I'll go searching to figure out how to update my PRL but if anyone has any other ideas I'd be grateful.
Also does anyone know if it is possible to tether over 4G? I was never able to connect unless I turned off 4g before tethering.
It is working again. I started over and flashed Stock-EG30.tar and all is good now.
Out of curiosity did you update your system profile after you flashed? I think it's recommended to do that every time you flash a new kernel.
Settings > About phone > System updates then choose update profile.
Edit - Ahh cool looks like you got it worked out. Cheers!
Nope, I never updated my system profile. That could of been a fix....
Interestingly enough, I was retracing my steps after going stock, after each step I checked 4G connectivity. I lost 4G after enabling AdAway. So I disabled (each change requires a reboot) and got 4G back after the boot. I enabled it again hoping to be able to isolate the issue but after that next reboot I got 4G access with AdAway enabled.
Can't say it is AdAway, but after toggling it, I got 4G back.
Hello everyone,
Couple of days ago I upgraded my E4GT to Calkulin's 1.3a (from a previous version). Since then, I noticed the phone reboots on its own at least once a day and sometimes I miss calls (this might be Sprint's fault though).
This is what I have installed right now:
Code:
Android version: 4.0.3
Baseband version: S:D710.10 S.EL29
Kernel version: 3.0.15-SPH-D710.FC24-CL287574 [email protected] #3
Build number: Calkulins.E4GT.2.ROM.v1.3a
Hardware version: D710.10
The reason my baseband is EL29 is because I read somewhere that newer versions do not support GPS as of yet.
Can someone show me the way please?
Thank you very much
I'm on 1.3a and have super fast gps. I'm on all fc24 stock. No reboots or any issues. The gps can be fixed in several ways. I ran Faster fix and GPS Fix. Now it lock before map is even loaded. The reboot issue can usually be fixed by a good clean install.
Sent from my SPH-D710 using Tapatalk
What version did you flash from? I have not had any problems with the random reboots. I have been flashing every tweaked calk rom since fc05. They don't even require format to get up and running.
The only problem I've encountered is that I lost GPS on fc24. I had to use the old "go back to el29 gb for a lock and restore my nandroid backup" trick to get it back.
Did you try the format all and clearing cache?
If you flashed the rom from GB to ICS, then you must make the clean install (using Calk's format all tool). Otherwise, you will experienced the many issues that no one is going to help you because you did not follow the instruction.
I had the same issue after going from 1.3 to 1.3a. No wipe or resets helped. Just went back to el29 like usual and flashed 1.3a again it was fine.
kobridge said:
If you flashed the rom from GB to ICS, then you must make the clean install (using Calk's format all tool). Otherwise, you will experienced the many issues that no one is going to help you because you did not follow the instruction.
Click to expand...
Click to collapse
Not so true I've been flashing every ICS leaks and I always make a clean install and I"m in the same boat as him so I did some testing and I found out that when I have 4G on ( in which I always do ) that's when my phone reboot at least 3 or 4 times during the day. Now on 3G it NEVER reboot so I d/l the Calk 1.3a again with clean install and flashed it and I still have the same problem.
Something to this as the reboots were significantly worse when I was on 4g, though not exclusively. The reboots were bad enough on my phone while on ics that am now back to 2.8.1
Sent from my SPH-D710 using XDA
LilWeech said:
Not so true I've been flashing every ICS leaks and I always make a clean install and I"m in the same boat as him so I did some testing and I found out that when I have 4G on ( in which I always do ) that's when my phone reboot at least 3 or 4 times during the day. Now on 3G it NEVER reboot so I d/l the Calk 1.3a again with clean install and flashed it and I still have the same problem.
Click to expand...
Click to collapse
I can confirm that reboots occur only on 4g
Sent from my SPH-D710 using xda premium
Having the same random reboots. Always do full wipe with calks format all. Tried several different modems and versions.
Sorry guys, after some testing I noticed that only when I leave 4G on do the reboots occurr. I have turned off 4G and it has been going for over 24 hours without reboots. I never use 4G but I felt like using my "unlimited" Sprint data plan so I started to use 4G and then I noticed the reboots.
I have gone from GB to ICS without a clean install, which I believe is the reason why I have the EL29 in my specs.
Seeing as how this version has "a" in the name, I am blaming this on the alpha release.
Hopefully it will get addressed by Calk (who is the man, btw).
Thank you!
I updated phone by going to settings/about phone/system updates and ran the updates and havent noticed any reboots since. But this is at home where I get intermittent 4g so I will know for sure if its fixed when I'm at work tomorrow.
tyler2time: thanks for the info, I just updated Profile and PRL (but Firmware and Android were up-to-date already). I will test this out throughout the day tomorrow and report back.
sTr3utr said:
Sorry guys, after some testing I noticed that only when I leave 4G on do the reboots occurr. I have turned off 4G and it has been going for over 24 hours without reboots. I never use 4G but I felt like using my "unlimited" Sprint data plan so I started to use 4G and then I noticed the reboots.
I have gone from GB to ICS without a clean install, which I believe is the reason why I have the EL29 in my specs.
Seeing as how this version has "a" in the name, I am blaming this on the alpha release.
Hopefully it will get addressed by Calk (who is the man, btw).
Thank you!
Click to expand...
Click to collapse
The EL29 Baseband is the modem you are using. It does not change when you flash a new Rom. You can flash any modem you want to try but they have to be flashed separately. The a in the 1.3a build is because in v1.3, Calkulin accidentally used the FC22 kernel. He uploaded the Rom again with the FC24 kernel and renamed it to 1.3a. I consider every one of these leaks Alpha builds since they are built for testing purposes. Thanks for posting your results.
Hi DataHawg,
Thank you for the info. I found out that the modem is updated independently of the ROM. I am planning to do a format_all and re-install with latest modem, hopefully that will be more stable.
Another strange thing happened: I went to sleep with phone battery at 46% and woke up today with a dead phone. I saw that battery was drained somehow. I don't leave apps/services running except for a few (dropbox, box.net, facebook, twitter).
I will report how the new upgrade goes.
Thank you again, you guys are doing a helluva job here!
Today I read in the original Calkulin thread that modems used in ICS all have trouble with 4G data reboots, so I guess it's a known issue.
But now I'm having another issue with HTC_IME mod crashing. Can anyone help?
Thanks!
EDIT: Found the problem to be text prediction. I turned it off in the HTC_IME mod settings and all works fine now, no crashes so far. Thank you everyone!
My Epic is pretty much stock (EI22, Kernel 2.6.35.7), it is rooted and I added the GPS fix and the 4G boost.
I have been experiencing reboots every other day, and I think they match the issue described in
toadlife's The spontaneous reboot (solution?) thread
So I just ran out of patience; and I'm thinking to either upgrade the kernel or install a whole new ROM.
Also, since I use the phone for job related tasks, stability is a must.
I don't know if just a new kernel may help, hence my question:
What do you recommend and why (other than a GS III )?
If you're rooted and don't want to stray too far from "stock" Gingerbread I would suggest trying out The People's ROM.
Very stable, I go days/weeks without rebooting (my current uptime is 425:18:46) and don't think I've ever had a spontaneous reboot. The only thing I run different from TPR standard is the CleanGB kernel.
The CleanGB ROM is very good, but it stopped at EL30 (TPR is running the latest FC09 release) and requires some fiddling to stop the OTA update messages.
Other than that, CM10 is very impressive but still a work in progress (and a lot more demanding on the battery).
No matter what you decide I would suggest updating the modem to FC09.
Or fc09 stock prerooted
Sent from my SPH-D700 using xda premium
Hi Guys really need help on this one.
As a brief background on the problem, from stock I have flashed a few custom roms mainly paranoid android, carbon, android revolution hd. Flashing was always successful. No problem with odin flash as well. My concern is this. I noticed that I was getting SODs after flashing a few custom roms. So in order to fix it, I tried to flash stock rom. No problem with flashing however SODs continue to exits. Have tried flashing quite a few stock roms but basically SOD problem still exists. By the way when flashing through ODIN I always just flashed with the PDA option never with the others. Getting really frustrated about this. I can get rid of the SODs temporarily by using SoftLocker. However, I wish to get back to a stable rom base before I try any new customizations. Hope you can help me. Thanks.
On an added note, when I connect my phone to the PC the phone is not automatically detected. I still have to input *#7284# change modem to pda in order for it to be detected. I think this is somehow related because this happened during my encounters with SODs.
Your help would be greatly appreciated.
By the way, I have already checked for the SDS chip and happily my phone doesn't use the insane chip.
Just wondering about this SOD thing.
Should it be enough that I flash into stock (PDA only) to get factory stock?
Should mention that original ROM of phone did NOT have SODs.
So I'm guessing the culprit is flashing the customized ROMs.
However, I cant get stability back even when flashing back to stock.
I can still see some residual effects of previous roms in my current stock rom (like the usb connection not detected).
Just looking for some clues and glad if someone could help.
t3kn1ks said:
By the way, I have already checked for the SDS chip and happily my phone doesn't use the insane chip.
Just wondering about this SOD thing.
Should it be enough that I flash into stock (PDA only) to get factory stock?
Should mention that original ROM of phone did NOT have SODs.
So I'm guessing the culprit is flashing the customized ROMs.
However, I cant get stability back even when flashing back to stock.
I can still see some residual effects of previous roms in my current stock rom (like the usb connection not detected).
Just looking for some clues and glad if someone could help.
Click to expand...
Click to collapse
HI Guys,
Just an update on this, in case someone is experiencing the same problems, it seems I got the SOD fix. I found it out by switching back to an AOKP rom. Suddenly, no more SOD. After a bit more experimenting, I found out that it had something to do with the kernel (stock kernel even!). My basic fix is this: install a stock rom then switch kernel to Note2Core. It seems certain "configuration updates" within the kernel prevents the device from going into sleep of death. (Note that my device now can "sleep" properly ... saw this using cpu spy ... deep sleep is still attained with NO SOD). Hope this helps people out there with the frustrating SOD problem.
Incidentally, if someone could point out how the kernel change fixed the SOD problem it would be a great help.
By the way, usb connection is still not detected by default but fixed by doing *#7248" and then choosing pda for usb.
Fixed! and Solved!
t3kn1ks said:
HI Guys,
Just an update on this, in case someone is experiencing the same problems, it seems I got the SOD fix. I found it out by switching back to an AOKP rom. Suddenly, no more SOD. After a bit more experimenting, I found out that it had something to do with the kernel (stock kernel even!). My basic fix is this: install a stock rom then switch kernel to Note2Core. It seems certain "configuration updates" within the kernel prevents the device from going into sleep of death. (Note that my device now can "sleep" properly ... saw this using cpu spy ... deep sleep is still attained with NO SOD). Hope this helps people out there with the frustrating SOD problem.
Incidentally, if someone could point out how the kernel change fixed the SOD problem it would be a great help.
By the way, usb connection is still not detected by default but fixed by doing *#7248" and then choosing pda for usb.
Click to expand...
Click to collapse
As an end note, I was able to bring back the ROM to stable state.
I believe my mistake was that I accidentally flashed an S3 ROM to my Note 2.
Probably corrupted some files.
The fix seems to be this:
Flash N7100_OXA_N7100XXDLJ2.
It will fail at sboot.bin.
Flash another stable rom (I did it with stock rom Stock_Deodex_Rooted_N7100XXDMC3_N7100OLBDMD1_N7100DXDLK5_THL)
Finish up.
Test for SODs.
CPU spy is the best way to check for it.
If deep sleep occurs without SOD then your phone is back to stable state.
USB connection is working properly as well as bluetooth (which I failed to notice was defective as well).
Hope this helps someone as it took me almost 5 months to get the phone stable. Cheers.
t3kn1ks said:
As an end note, I was able to bring back the ROM to stable state.
I believe my mistake was that I accidentally flashed an S3 ROM to my Note 2.
Probably corrupted some files.
The fix seems to be this:
Flash N7100_OXA_N7100XXDLJ2.
It will fail at sboot.bin.
Flash another stable rom (I did it with stock rom Stock_Deodex_Rooted_N7100XXDMC3_N7100OLBDMD1_N7100DXDLK5_THL)
Finish up.
Test for SODs.
CPU spy is the best way to check for it.
If deep sleep occurs without SOD then your phone is back to stable state.
USB connection is working properly as well as bluetooth (which I failed to notice was defective as well).
Hope this helps someone as it took me almost 5 months to get the phone stable. Cheers.
Click to expand...
Click to collapse
Thanks man i thumbs up ur account....i was changing my dead screen to a new one and i thought it was the new screen that kept turning off even after trying stock kernels and even pegasus but because of ur note2core recommendation and worked like a charm ....thanks man