yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] pisherthefisher:
Are you referring to a new build or the current one? Because I've done multiple tests on the current build and the bugs still exist.
[Samsung Galaxy S (4G Model)] turtlepa:
What are you talking about. Our phones are supposed to deep sleep. They are supposed to wake up from deep sleep. We shouldnt be changing these values or changing amything. The devs have to change their code in the kernel. Look at beanstalk forum do they have ppl ranting trying all these values that wont work. They have deep sleep call drop too. Doesnt have the text issue though so they arent knitted together like that. Get noiphone and airfluip to fix it or get help from beast if they even wanna acknowledge its a bug. which IT IS

---------- Post added at 07:24 PM ---------- Previous post was at 07:23 PM ----------

I guess forget what i just said. Airfluip1. The call bug is there. Sorry to break it to you
[Samsung Galaxy S (4G Model)] pisherthefisher:
I'm fully aware our phones are suppose to deep sleep, but obviously they aren't doing it right if they disconnect from the network while doing that.
[Samsung Galaxy S (4G Model)] johnadelic:
I really don't want to jump in on this ranting that I see happening in a Dev thread. But I am not having any issues. I have my governor set to interactive, min CPU set to 200, max CPU set to 1200. I don't have any problems with deep sleep, missing calls, network issues, multiple texts. These two wonderful guys hand delivered roms and kernels that brought our phones up to be usable daily drivers. I think they deserve my appreciation they they are getting. Is there a problem or a bug that happens when we undervolt our phones sure but that is something I am sure is and will be fixed just like how everything else.

I guess what I am saying is say thank you and provide help with debugging the ROM or ....... I was going to say something bad there but I am better than that.
[Samsung Galaxy S (4G Model)] Fluidification:
Yes, THAT is a bug, but if you follow my directions on max/min cpu, it doesn't happen. And overvolting isn't actually taking that much battery away.
[Samsung Galaxy S (4G Model)] turtlepa:
if you read the logcat it's not a disconnect from the network.... actually i'll make a second logcat more verbose or -vv

---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------

airfluip1 am i going delusional from flashing back n forth aries 10.1 beanstalk ultragen or am i really not seeing performance setting in build 2? to set it to 200... my previous post states that we shouldn't have to do that. if you look at the logcat and research it it's one file that needs editing. but for the mean time i'll test it at 200 if i can find performance option in settings. where is developer options too? im gonna test it again and bring a logcat... at 200 if need be... but seriously that's not how you fix bugs,
[Samsung Galaxy S (4G Model)] pisherthefisher:
I didn't look through to log cat yet, but in cm 10.1 the performance settings are hidden. Go to about phone and touch it 5 times to unlock the performance and developer settings
[Samsung Galaxy S (4G Model)] turtlepa:
thanks, there is an app to open developer options too its in there. i will test this same release i tested before, im flashing now i'm going to call fro two different phone numbers and test it on both sgs4gs i have and return with logcat.
[Samsung Galaxy S (4G Model)] Fluidification:
If you are plugged into logcat, it won't ring when asleep.
[Samsung Galaxy S (4G Model)] johnadelic:
Jesus, I can hear the foot steps of the mods coming to clean this thread.

---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------

You have to click on Build Number 5 times in the About Phone section to get Developer Options and Performance.
[Samsung Galaxy S (4G Model)] CSP III:
Dude....I have followed your directions to the "T" Every one of them and I (like a lot of others) am still having issues. I don't know what to tell you man, it is happening and for you to say "it is safe to say that the call thing is fixed for most" indicates that you know there is an issue. Whether its for some, or for all, it is there. It kinda sounds to me like you're saying I don't have it and he doesn't and he doesn't and he doesn't so the rest of you are SOL. Too bad so sad! Well that sucks Airfluip1 and that sort of attitude isn't gonna get you very far in life. You're ROM rocks except for these issues and if your saying it is what it is well that's cool. You have that right. But people also have the right to not support you either, and that will happen. Thanks much for the ROM either way. Someone is gonna figure it out sooner or later, and I for one will be right there....supporting that dev. Good luck to ya!
[Samsung Galaxy S (4G Model)] turtlepa:
im not plugged in airfluip1. logcat extreme allows deep sleep. im going to do extensive testing and report in morning. as of now the bug is still there missing call. my recent two wait/calls have worked at 200mhz, i just believe that shouldn't be the fix, we didn't need that for ics or gb

Okay, even at 200mhz i still tried 2 t959v with two diff numbers and they didn't recieve the call set on the default [row] for manager. im going to test it with cfq, but like i said this isn't working with a mhz tweak, it's not about that, it's dispatcher shutting down in the call process.

by the way i would recommend everyone use logcat extreme from playstore it allows deep sleep not to interfere with logcat and you can get a lot more info with the radio switch or in dmesg, also you can test this yourself, set your phone to timeout at 15s disable data let phone go to sleep wait 2 min and cal from http://www.wheresmycellphone.com if you don't have another phone logs will be attached soon. trying to see if there's a diff with ondemand
[Samsung Galaxy S (4G Model)] Stuck on hold:
I don't know how SMS works on the system level, but I assume the network sends the message and when the phone receives it an ACK is sent back. If the network doesn't see an ACK, it resends several times until it does or the message times out. Maybe the phone receives it, but doesn't send an ACK to the network, resulting in multiple copies received? Or it doesn't send ACK back in a way the network recognizes. Or doesn't turn the transmit on...

If that's a, No DUH!, I apologize. Just trying to think where it could break.
[Samsung Galaxy S (4G Model)] Fluidification:
I did not know that, Thanks.

[MENTION=4152592]turtlepa[/MENTION], whether you use logcat, or logcat extreme, logcat doesn't even let the phone see anything when an incoming call is received. Even adb logcat lets the phone go into deep sleep. It doesn't receive calls that way though. You have to just leave it alone, then call.
[Samsung Galaxy S (4G Model)] Madein Cyberspace:
Not true that I'm aware of. If you can show me where you read that I would appreciate it. I've used ADB quite a bit and have never been able to get the phone to deep sleep using it. It will stay on the lowest frequency the phone is set to. Getting logs of issues like this has been very difficult in the past. I'm sure this will be no different.
[Samsung Galaxy S (4G Model)] Hey Jacob:
Initial boot took longer than usual but alas I'm restoring my google information! I will post later on my thoughts about this =D
[Samsung Galaxy S (4G Model)] turtlepa:
Thats what i did. The bug still affects at 200mhz. Hopefully its fixed one day

Here's the logcat: search for dispatch

I let this ring 4 times without my phone picking it up, i woke the phone and it caught the signal but missed the call. so i tried to get you whatever i could, if you want just the missed call look at other logcat i posted

http://pastebin.com/j6fPhCbw
[Samsung Galaxy S (4G Model)] Fluidification:
that looks interesting.

Will do research.
[Samsung Galaxy S (4G Model)] turtlepa:
Can someone on release 2 try calling their phone while in deep sleep? But do this with lockscreen set to none? Trying to see if something in new logcat has anything to do with that. If not ill test it tomorrow

---------- Post added at 05:11 PM ---------- Previous post was at 04:56 PM ----------

Here is a logcat of radio ril mostly for sms bug possible data disconnects etc

http://pastebin.com/ebdzQWpJ
[Samsung Galaxy S (4G Model)] RaverX3X:
just skmmed over.... Did anyone check to make sure that they setup a wake lock to the broadcast recever to wake the device from deep sleep? Airflip is right during deep sleep if you get a notfication unless its broadcast to wake the device and notify you wont actually get any notfication at all.

example would be

new Handler().postDelayed(new Runnable() {

public void run() {

PowerManager pm = (PowerManager) getSystemService(POWER_SERVICE);

WakeLock wl = pm.newWakeLock(PowerManager.SCREEN_BRIGHT_WAKE_LOCK|PowerManager.ACQUIRE_CAUSES_WAKEUP, "bbbb");

wl.acquire();

wl.release();

}

}, 10000);

just remember airflip u only have a 10 second broadcast time for the notification and you cant do it from handlers do to the fact when the devices goes to standby all handlers are ignored tell the device is manually woken up.

WakefulIntentService - make your MyDataService extend WakefulIntentService and in your receiver call WakefulIntentService.doWakefulWork(context, MyDataService.class)

i know not for data but just trying to give u some ideas where to snoop
[Samsung Galaxy S (4G Model)] Fluidification:
Can you comment on github with some more info?

I am not that experienced, so I lost you a few times.
[Samsung Galaxy S (4G Model)] turtlepa:
Wow raver from left field outta nowhere. My man we need your help !

Its something in the kernel code causing all this
[Samsung Galaxy S (4G Model)] RaverX3X:
prob not

more or less without looking at anything it would be something like this

SystemBootReceiver --> (DataSyncService)Service --> (MyBroadcastReceiver)BroadcastReceiver --> (MyDataService)Service .

So here on system boot start DataSyncService where you set up the AlarmManager (repeated) and call the MyBroadcastRecever .After calling the BroadcastRecever you stop DataSyncService by calling stopself() .

Now the MyBroadcastRecever calls the MyDataService.

PowerManager pm = (PowerManager)

getSystemService(Context.POWER_SERVICE);

mWakeLock = pm.newWakeLock(PowerManager.PARTIAL_WAKE_LOCK, "My Tag");

mWakeLock.acquire();`

And release() the wake lock before stopping the service.

set the permission in android manifest

to make it fully work you will need to WakefulIntentService and in your receiver call WakefulIntentService.doWakefulWork(context, MyDataService.class)

If using wifi you should also need to use a WifiLock - inside your wakeful intent service

i tried to explain it the best i can. Also u might want to get ahold of bryan sense hes way better at android then i am. Not to mention im using a metered data plan atm but feel free to get me on gtalk or text me lol
[Samsung Galaxy S (4G Model)] teqno:
Also getting the Multi text issue like my phone is possessed. Also cant send mms. It gets stuck on sending. Had the problem with wifi signal being a strong signal but once I tried to connect the signal gets real low. Reflash fixed that. Had a issue with having no signal at all, reflash or fix permission got everything working again.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
flash another modem apart from KJ6 from here: http://xdaforums.com/showthread.php?t=1192436
[Samsung Galaxy S (4G Model)] darnelcach:
Is this kernel issue or modem issued???????...I .like this rom it doesnt have cm10 bugs but the issue with deep sleep really getting on my nerves am get no calls an no sms and multiple sms :( ................hope you guys can fix it .....i had use another ROM because i use my phone daily......

---------- Post added at 07:09 PM ---------- Previous post was at 06:28 PM ----------

has anyone used these steps and got good results?????

1. flash rom, reflash rom

2. flash nelupdate1.zip

3. Reflash nelupdate1.zip

4. fix permission

5. flash another modem apart from KJ6

6. 200min/1000max .. interactive or 200min/1200max.. ondemand

does this fix anything on the rom?????
[Samsung Galaxy S (4G Model)] CSP III:
Done all that and so much more...... apparently some have it, others don't. frustrating. if you need this phone daily, move on...you'll miss a lot of call and get hella lots of repeated texts. if you can deal with these issues then enjoy because it really is super snappy!
[Samsung Galaxy S (4G Model)] darnelcach:
THAT WAS what i was afraid of ....any way am already on ULTRAGEN ROM i¨ll wait if there are any fixes TEAM USER DEBUG"S ROM
[Samsung Galaxy S (4G Model)] turtlepa:
I think airfluip is moving onto paranoid android. I have logcats Posted in this thread for no call multi text if anyone can get an idea on a fix. Also ravers post seemed to be close
[Samsung Galaxy S (4G Model)] Fluidification:
I didn't say I am moving on, I said that I am also working on that.

I am actively building this right now!

Also, trying to port up kernel further.
[Samsung Galaxy S (4G Model)] mattoaida:
Take your time airfluip :)
[Samsung Galaxy S (4G Model)] turtlepa:
I dont know if this this helps but the previous mtd rom you are on, before flashing, if you like pre gingerbread modems like kd1 kc5 (the ones and others that just wont flash on this aries) flash it on the rom you are on then flash jb aries... and u will have the modem working with this rom that if it was flashed after, wouldnt work otherwise
[Samsung Galaxy S (4G Model)] mattoaida:
Umm when signal doesn't work on my lg optimus I flash an old baseband modem and signal works
[Samsung Galaxy S (4G Model)] turtlepa:
Well this is for t959v.. not your lg phone
[Samsung Galaxy S (4G Model)] Fluidification:
Was just about to say that.... For 1 main reason, all non Samsung phones use proper radio partitions. Samsung uses a modem partition with a modem.bin file containing the radio. We wipe all partitions excluding bootloader,sbl,sbl2, and original rfs efs for safety reasons so that the phone has a backup. Using that new space, we make a new yaffs2 efs, system, kernel(boot), and radio. So we are making a new partition just for that.

Sent from Aries within the 1st Galaxy
[Samsung Galaxy S (4G Model)] Fluidification:
NEW BUILD IS UP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Please re-read the OP...

Also, you don't need a data wipe if updating.
[Samsung Galaxy S (4G Model)] turtlepa:
I have been testing for 3 hours, and although ive been using other spare phones and other means to test the call and text bug, i do not think this build has these bugs. I will know for sure by tomorrow if i have a missed call, but as of now if anyone thinks they have gotten a missed call or the bug is still here, please comment. Otherwise, im pretty sure the 2 bugs are fixed
[Samsung Galaxy S (4G Model)] Ahmad_Ashraf:
Where I can check your kernel source please ?
[Samsung Galaxy S (4G Model)] turtlepa:
Read the op
[Samsung Galaxy S (4G Model)] ithunter:
Whats about stability and other bugs ??? is everything is perfect ?
[Samsung Galaxy S (4G Model)] pisherthefisher:
Stability of Aries is great (i would say as good as stock) and the only bugs left are if network disconnections are fixed will be GPS and TV out.

---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------

Keep us updated. Do you still get the random disconnects?
[Samsung Galaxy S (4G Model)] Faisal Merchant:
So far so good been on this ROM for an entire day, No calls missed, and no multiple SMSes. Well done man!! And a huge thank you to the entire team for giving us 4.2.2, I was starting to think that our device would never get JB for sure.

Red outline/frame showing up on the screen, it is quite annoying but can live with it for now, fixing GPS should be your next step towards making this ROM even greater. Take your time man no one is rushing you.

I was wondering that if I could somehow use/flash TW5 with this ROM, I have been scavenging the entire forum for doing this but couldn't succeed, a little help would be highly appreciated!!!
[Samsung Galaxy S (4G Model)] pisherthefisher:
Read my post in the Q&A thread to get rid of the flashing red screen.
[Samsung Galaxy S (4G Model)] turtlepa:
I edited the build.prop but still has red flash, but it's very rare and not that big of a deal
[Samsung Galaxy S (4G Model)] Fluidification:
well, you know...

when setting build to eng, it copies over a truck load of eng specific modules, so that must be causing flash...

Will use userdebug next time.
[Samsung Galaxy S (4G Model)] nazcalito:
I had gotten discouraged that an Aries rom would ever be seen and haven't been around this forum for awhile. I just checked back in and voila, there is a working Jellybean Aries rom! The GPS bug is not a big thing for me since I never used GPS much anyway, it just ate too much battery time whatever the rom was, Froyo, GB, etc. The only complaints I've got are really complaints about Gapps not have the features of the GB versions of those apps and that's not anything we're responsible for. I haven't checked the battery life on my device but otherwise it seems to work just fine. :good:
[Samsung Galaxy S (4G Model)] Fluidification:
I have good news and bad...

Good news, the phone now knows that it has some lib to open when gps is called.

Bad, it sends the phone into infinite reboot loop.

Sent from Aries within the 1st Galaxy
[Samsung Galaxy S (4G Model)] Masterloki666:
Yeah I've did two runs ROMs pretty damn sweet an smooth but after a full battery drain and a reboot it seems to jus boot loop haven't been able to get a logcat yet....
[Samsung Galaxy S (4G Model)] Hey Jacob:
Build 3 looks promising, hope it fixes my network issues.
[Samsung Galaxy S (4G Model)] Cooptx:
Network is fine on mine :) until o deleted the efs folder because I was being stupid...
[Samsung Galaxy S (4G Model)] Fluidification:
here's another status update on GPS.

Maybe we don't need a libgps.

Turns out that all the files being used in our proprietary tree are not our original sgs4g ones.

They are probably from vibrant.

We probably can be fine with a gps wrapper, but i'll try the libgps and see what happens with the new files.

EDIT: as i suspected, they are!!!
[Samsung Galaxy S (4G Model)] johnadelic:
Just wanted to post some battery usage pics. This is with two Google accounts syncing everything and a exchange mail synching.
[Samsung Galaxy S (4G Model)] Fluidification:
IF ANYONE IS LISTENING,,, i AM SUMMONING THE ANDROMEDA CREW IN DEVELOPMENT FOR SOME ASSISTANCE IN FIXING THE GLOBAL POSITIONING SYSTEM.
[Samsung Galaxy S (4G Model)] Fluidification:
also, here is a log for a libgps test build...

In log, "AriesGPS" is the libgps.

http://pastebin.com/XbVEJTCb
[Samsung Galaxy S (4G Model)] Theraze:
We don't crash until around 533, when it looks like the display is actually what's choking there. At 498-500 we have installd fail to read a file properly, then at 501-518 we have the display deadlock, 519-532 we have the phone fail to get its configuration, 533 we have dalvik say that the thread is gone, and then everything closes in preparation for the reboot.

At least, that's where the E/ errors begin. :D

Looks like the real issue with the gps.aries.so MIGHT be that it's conflicting with libandroid_servers.so, since it's not the one that it expects to see there. And in each of those GPS error messages, the two are closely linked. Lines 214/215 and 239/240.
[Samsung Galaxy S (4G Model)] nevkuril:
Looks like the main error happened at #183 and then there's system dump. AFAIK SIGSEGV is a segmentation fault, something someplace tried to access memory it was not supposed to. After that the runtime just collapsed, don't think there's anything interesting after the dump. Backtrace shows gps.aries.so last to load so probably it tried to access invalid 0x0028 address. Anything in the kernel logs (dmesg)?

D/GpsLocationProvider( 2453): set_capabilities_callback: 14
F/libc ( 2453): Fatal signal 11 (SIGSEGV) at 0x00000028 (code=1), thread 2669 (LocationManager)
I/DEBUG ( 123): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
[Samsung Galaxy S (4G Model)] getochkn:
That's what I got screwing around with some Vibrant GPS files. Driver is loaded but that failed call just loops forever.

That was the source built about 2am.
[Samsung Galaxy S (4G Model)] Fluidification:
well I built mine using a debugger branch that I made using libgps.

getochkn, if you want to build libgps, then edit yourcmdir/.repo/local_manifests/local_manifest.xml

and change the revisions for android_device_samsung_galaxys4gmtd_aries and proprietary_vendor_samsung from "cm-10.1" to "debugger".

Then wipe and build again. This way you'll get my libgps built... Just make sure GPS is OFF when you flash so you don't get stuck in the reboot loop. So yeah, when you flash it, you will get stuck in a reboot loop after activating GPS.

if you want to kick yourself out of the loop, you are going to have to reflash to a stable version, or delete your gps.aries.so by running the following the following commands

adb shell

su

mount -o rw,remount /system

rm /system/lib/hw/gps.aries.so
[Samsung Galaxy S (4G Model)] turtlepa:
Airfluip i sucessfully made a build. My first. So if you need another tester. I right here. Good work on everything btw
[Samsung Galaxy S (4G Model)] Fluidification:
I am interested in one thing....

On my debugger branch, I am using libgps, and the output gps.aries.so seems to be functional since it "log tag 'AriesGPS'" isn't throwing out any garbage.

Maybe our gpsd configuration is screwed, I will try something else.
[Samsung Galaxy S (4G Model)] turtlepa:
Did u check dmesg see if the pid or any dependent pids get killed while is trying to load?
[Samsung Galaxy S (4G Model)] Fluidification:
I haven't had time.

Will try when I do.

Sent from Aries within the 1st Galaxy
[Samsung Galaxy S (4G Model)] Johnmonkey0:
Release 2 pretty much bricked my service reception. I used to have issues with trying to get reception but now it just ceases to connect.
[Samsung Galaxy S (4G Model)] turtlepa:
Why don't you wipe and flash release 3
[Samsung Galaxy S (4G Model)] Johnmonkey0:
i'm having the same issue.
[Samsung Galaxy S (4G Model)] TwitchyEye:
It happened to me too. Its legit. I tried everything to fix it.

Seems like a hardware failure. I'll try and get a log from my old phone before I send it back.

Edit: I had it happen with pacman and I had been on beanstalk previously so I think that the kernel with the radio issues is stressing the chip.
[Samsung Galaxy S (4G Model)] Fluidification:
i don't know how that's possible, but it might be...

If you're still under warranty, get a new phone after oneclicking back to stock.
[Samsung Galaxy S (4G Model)] TwitchyEye:
Exactly what I did. Well sorta. I paid the premium handset protection so I paid 5 bucks and they sent me a phone with a broken USB jack :/

Omg the speaker is busted too :banghead: OK T-Mobile get ready for an awkward moment.
[Samsung Galaxy S (4G Model)] turtlepa:
Airfluip on my build I went into terminal ran gpsd gave me this

samsung-gpsd

u0_a20@android:/vendor/bin # gpsd

Starting GpsRun to run [] job from [glconfig.xml] file

fopen: No such file or directory

The file /var/run/samsung-gpsd.pid could not be created

GPS glconfig.xml opening conf file: No such file or directory

GpsRun exit code -1: UNKNOWN

1|u0_a20@android:/vendor/bin
[Samsung Galaxy S (4G Model)] Fluidification:
OK, so that's a GPSWrapper build...

It shouldn't be looking for glconfig.

If anything, it should look for gps.xml.

Edit, nm, it's looking for it since GPS.xml is nonexistant.

Rebuild right now after resync.
[Samsung Galaxy S (4G Model)] Fluidification:
turtle... Maybe I get gpsd to function in terminal, but still not loading in the system, then I might use the libgps as well as the wrapper.
[Samsung Galaxy S (4G Model)] Fluidification:
I again... am confused...

So with a new build, gps IS starting, but then it's telling me that it's looking for data/data/com.android.angryGPS/secgps.conf???? WTF.

I'll keep fishing, but it seems to be getting closer.
[Samsung Galaxy S (4G Model)] foltz61:
Delete. Irrelevant.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
How bout installin angryGPS?