Develop Bugs

[Q] Data connection Slim hspa:11 vs CM9 hspap:15

I have recently started using Slim rom instead of CM9. One issue I'm having that I'd like to resolve is the differences in the data connection between the two roms. On stock 4.0.4 and CM9 I get hspap:15 (when active) and around 7 down / 2.5 up.
On Slim when using data I get hspa:11 (when active) and around 4 down / 1 up.
All 3 roms are reporting the same radio. Does anyone have a suggestion as to whether this could a kernel issue?
It's not a huge deal but I would like to maximize my connection speeds if possible.
TIA, Jeff

I have't seen my device showing hspap yet. According to your case,it's the problem of slimics?
I will try cm9 again although I have no choice but receiving its animation of navbar.
Sent from my Galaxy Nexus using xda premium

stayreal,
Please let me know the outcome.
I'm very happy with leanKernel so I really don't want to start experimenting with different kernels. And since all 3 roms report the same radio I don't really want to start flashing other radios.
I'm hoping one of the slim devs might see this and have a suggestion.
Jeff

Solved it. I'm very happy now with Slim rom.
The RIL and BaseBand didn't match. Slim ROM or leftover from an old flash but either way GetRIL identifed the mismatch. As soon as I flashed the matching RIL and rebooted I'm good on hspap:15.
Jeff

stayreal said:
I have't seen my device showing hspap yet. According to your case,it's the problem of slimics?
I will try cm9 again although I have no choice but receiving its animation of navbar.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I believe the new Galaxy S3 uses HSPAP 15 on Vodafone.
Regards.

Bell Mobility Network Problems?

Alright, I was wondering, I've been having some problems lately with the CM10 roms, and I switched back to the stock unrooted rom.
My problem was it was disconnecting me from the server every once in a while, had to reboot to reset the connection, now even when on the stock rom it does this, is this a Bell Mobility problem? Or a phone problem? I see I had to create a new APN with the Bell settings, but I really dont know why!
I was wondering, is this a network problem? Or a phone problem? I've had my phone for about a 1.5months and just the past couple days that it does this to me!
Thanks,
JP

I'm on Bell.
If it happens on stock ROM it's either hardware issue or Bell is having problems.
Yeah network connection is only good... 98% of the time in my experience with AOSP Rom's (including CM10). Sometimes it stops working altogether and I have to toggle flight mode a few times. I must have flashed AOSP Rom's about 50-60 times and each and every single time I have gotten literally double the latency I get on TW rom's regardless of which Modem I use. Other people do not seem to be having this issue, just people with Bell.

scorpion667 said:
I'm on Bell.
If it happens on stock ROM it's either hardware issue or Bell is having problems.
Yeah network connection is only good... 98% of the time in my experience with AOSP Rom's (including CM10). Sometimes it stops working altogether and I have to toggle flight mode a few times. I must have flashed AOSP Rom's about 50-60 times and each and every single time I have gotten literally double the latency I get on TW rom's regardless of which Modem I use. Other people do not seem to be having this issue, just people with Bell.
Click to expand...
Click to collapse
Thanks, seems like its back to normal with the stock ROM, so I might try another AOKP or AOSP rom... Which TW rom did you use?
So it's better with an AOSP rom or worst? Pardon my english, french is my primary language!

jproy12 said:
Thanks, seems like its back to normal with the stock ROM, so I might try another AOKP or AOSP rom... Which TW rom did you use?
So it's better with an AOSP rom or worst? Pardon my english, french is my primary language!
Click to expand...
Click to collapse
I recommend Task650's AOKP ROM.
But be aware all non touchwiz ROM's have some bugs currently. But they are smoother and faster, that's why I use them.

If you are looking for a TW rom, I have been using this one since it came out and don't have any serious issues with it.
http://forum.xda-developers.com/showthread.php?t=1956463
Edit: I'm also on Bell

scorpion667 said:
I recommend Task650's AOKP ROM.
But be aware all non touchwiz ROM's have some bugs currently. But they are smoother and faster, that's why I use them.
Click to expand...
Click to collapse
Thanks, I know, I'll wait till they get some bugs out before making the switch again... Back on the stock rom and seems solid again.
acme anvil said:
If you are looking for a TW rom, I have been using this one since it came out and don't have any serious issues with it.
http://forum.xda-developers.com/showthread.php?t=1956463
Edit: I'm also on Bell
Click to expand...
Click to collapse
I'll take a look at it, but it says for sprint?

Yah. But it works. And if you chk a lot of the roms, they're built on AT&T base and they also work fine on a Bell device.
My biggest issue (for me at least) with AOSP, AOKP and CM10 roms is that voice mail notification doesn't work. It's been a known issue for some time but it hasn't been fixed yet. I should qualify by saying I haven't run every single rom out there but anything built off CM10 seems to have this issue on Bell devices.

acme anvil said:
Yah. But it works. And if you chk a lot of the roms, they're built on AT&T base and they also work fine on a Bell device.
Click to expand...
Click to collapse
I can download the rom you posted and load it no problems? It's basically JB upgraded a bit? Can you post a screen shot of what it looks like? Have you had any bugs with it? Seems like the last update was on October 29th...
Thanks!
Sent fr om my SGH-I747M using Tapatalk 2

Also on all AOKP Rom's I can not receive MMS at all. Not sure if it worked on CM10
I triple checked APN every time I tested.

[Q] Porting CM10 A100 to A101

Hi Everyone, can anybody tell me how to port CM10 A100 to Iconia A101, coz I always use A100 ROM but I lose my 3G capability?
Thanks Before

Well, I you'd need 3g drivers. Etc maybe drop the 3g apps in? I may not be possible. Might also need source changes.
Sent from a Soviet base in Indiana

I know this thread is older... But to answer your question: it must be built into the source before compile it - just to sum it up. But that's what I want to do.
I planned some projects for A100/101
- build an existing Rom (cm9) with 3g to serve a101 users (cm9 is most stable)
- recovery with dual boot (and run Ubuntu n near android)
- start 4.2 builds
This is lot of work and will take a lot of time, any help appreciated.
Gesendet von meinem A100 mit Tapatalk 2

Eh. 4.2 was booting just no WiFi and lots of little UI stuff.
Sent from my vangogh using xda app-developers app

das_webos_transformer said:
Eh. 4.2 was booting just no WiFi and lots of little UI stuff.
Sent from my vangogh using xda app-developers app
Click to expand...
Click to collapse
Well, nice to know. Could be a good starting point.
Gesendet von meinem XT910 mit Tapatalk 2

dtrail1 said:
I know this thread is older... But to answer your question: it must be built into the source before compile it - just to sum it up. But that's what I want to do.
I planned some projects for A100/101
- build an existing Rom (cm9) with 3g to serve a101 users (cm9 is most stable)
- recovery with dual boot (and run Ubuntu n near android)
- start 4.2 builds
This is lot of work and will take a lot of time, any help appreciated.
Click to expand...
Click to collapse
How are things progressing? I found the following old info:
pio_masaki said:
It can have 3g just fine, I've asked a few times for the 3g ril files from 101 users wanting me to build for them, they always vanish and I never hear back about it.
A100 just had its rotation for builds last night / this morning so it'll come up again sometime between wed-fri I think. Been looking at updating the black bean build and maybe adding AOKP as well, I'll use them for testbeds. I may go ahead and just do an extra day on the A100 and see about getting a potential 3g build up for you.
Side note, sosei will use gps if you use the newer cm10 boot.img.
Current rotation is:
Nexus 7 holds priority as I've been invited to Team Sorcery as their N7 dev.
Toshiba Thrive 4.2 development, 4.1.2 updates and kernel work (voodoo sound) comes second as they've been extremely generous to me.
Droid DNA aosp porting as the device was pretty much donated
Slight GNex work as needed, rare
A100 is bottom/last as I don't own one, luckily fixes from the thrive usually directly move over to the A100
Other devices I don't own.
I have a few things planned for the A100 for some nice updates and releases to jeep you guys in a variety of ROMs, like AOKP and some updates to the cm9 kernel I use.
Sent from my Nexus 7 - JBSourcery 4.5
Click to expand...
Click to collapse

Things are going slowly... Too much work in the office. But I set up a working tree some weeks ago for CM9 and a kernel. As soon as I have some more time I'll continue this. I was also busy with a kernel for the moto razr. Once I had a whole team, but now I'm alone... Will take time.
M.o.t.o.r.o.l.a.R.a.z.r - JBX-Kernel 0.5a - Tapatalk4

sorry for revived such an old thread,
i've managed to port cm10 to iconia a101, 3g and other is working properly.
but it still got a couple of bug,just wanna know if there someone here who could help me fix some bug left (let's say like gps) :fingers-crossed:

What is your base and port ROM that you used? ie what CM10 rom did you use or did you build from source? What kernel did you use?
Also you need to be more specific on the issues that you have, as well as logcats otherwise there is nothing any of us can do.

I port the rom for a500 from tegra owner forum and using gm kernel with it,
So far bug that i noticed just the gps and flash,
The gps won't start, in the gps log it mention something wrong with the hal configuration
And i noticed that the file in /dev/bus/usb/002 doesn't exist which were the configuration was set to look.
I'll explain more specific and take a logcat tomorrow,it's already 2 am here got to work in the morning,
Thanks btw for your reply
Edit: for the base i mainly using your rom,and take some other part from some different rom
here the logcat and gps log when i tried to used gps.
Sent from my Galaxy Nexus using xda app-developers app

Your logcat is also indicating that you don't have 3g connectivity. I'm pretty sure the GM kernel does not have 3G support so no matter what you do and try to get working on this build, you won't have 3g connectivity. The first step to getting it to work is to find a kernel that has 3g activated on it.

hardslog said:
Your logcat is also indicating that you don't have 3g connectivity. I'm pretty sure the GM kernel does not have 3G support so no matter what you do and try to get working on this build, you won't have 3g connectivity. The first step to getting it to work is to find a kernel that has 3g activated on it.
Click to expand...
Click to collapse
A stock a101 ICS kernel should function well enough for testing this in 4.1.
Sent from my Galaxy Nexus using Tapatalk 2

That's what I was thinking too. I just might try that as i have had success doing the same thing with a TF300 to get 3g working
Sent from my A100 using xda app-developers app

hardslog said:
That's what I was thinking too. I just might try that as i have had success doing the same thing with a TF300 to get 3g working
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
I've been meaning to look at 3g for the thrive also, may as well start noe since others are looking at it too lol
Tapatalked from my HTC DNA - Carbon

hardslog said:
Your logcat is also indicating that you don't have 3g connectivity. I'm pretty sure the GM kernel does not have 3G support so no matter what you do and try to get working on this build, you won't have 3g connectivity. The first step to getting it to work is to find a kernel that has 3g activated on it.
Click to expand...
Click to collapse
3g was working just fine, i've tried with several kernel including stock ics,

I'm interested in helping out fauntelroy, was going to start porting a rom, but there seems little point in re-inventing the wheel.
No idea if you're still working on it though, let me know, thanks!

Weaker LTE on AOSP?

At my house I get a fairly weak LTE signal. It seems like I get much slower speeds while on LTE when I'm running an AOSP based ROM on this weak signal. I've tried CM10.1 nighties & CarbonRom. Like I said, the signal is pretty weak so sometimes I'll lose it when on either TW or AOSP but it seems like TW works better with it. What's causing this? Is there a way to fix it? Has anyone else noticed the same thing?

It is pretty much impossible to narrow down the culprit of signal strength, just think of how many variables are out there. It is said by many AOSP ROMs give a more accurate signal bar reading than TW. TW supposedly adds some boost to make it look stronger. One thing you can do is switch modems, they work different for different areas. I personally prefer to be on the most recent one always which right now is MA6. you can also go back to a TW ROM temporarily and make sure your prl and profile are up to date. Also you want to go to settings>about device>status to see you real reading for signal strength don't just rely on what the bars say. There is usually a way to even change this in your notification bar for most ROMs. Or you can download something like sensorly or open signal in the play store to keep track.
Sent from my Nexus 7 using Tapatalk 2

GiantJay said:
It is pretty much impossible to narrow down the culprit of signal strength, just think of how many variables are out there. It is said by many AOSP ROMs give a more accurate signal bar reading than TW. TW supposedly adds some boost to make it look stronger. One thing you can do is switch modems, they work different for different areas. I personally prefer to be on the most recent one always which right now is MA6. you can also go back to a TW ROM temporarily and make sure your prl and profile are up to date. Also you want to go to settings>about device>status to see you real reading for signal strength don't just rely on what the bars say. There is usually a way to even change this in your notification bar for most ROMs. Or you can download something like sensorly or open signal in the play store to keep track.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
The thing is that it isn't just the reading. When I do a speed test I generally get less than 1 mbps on AOSP, but with TW I get 3 to 8 mbps usually. This is from the exact same spot in my room & at the same time of day too. I don't know if there is a difference anywhere else I go because I don't switch ROMs while I'm out. I'm using the MA6 modem right now & found that it works best for me. I'm just confused on how LTE speeds on TW could be so much better when my modem & everything is the same.

I figured out something really weird last night. I clean flashed the CM10 stable build & LTE worked just as well as it does on TW. Then I clean flashed the latest CM10.1 nightly and LTE was performing poorly again. Could it be a problem with Android 4.2?? Anyone experience the same thing ever? I'm going to try some more tests tonight.

Fire Ball said:
I figured out something really weird last night. I clean flashed the CM10 stable build & LTE worked just as well as it does on TW. Then I clean flashed the latest CM10.1 nightly and LTE was performing poorly again. Could it be a problem with Android 4.2?? Anyone experience the same thing ever? I'm going to try some more tests tonight.
Click to expand...
Click to collapse
Strange. May be just some bugs that havent been fully worked out yet

CNexus said:
Strange. May be just some bugs that havent been fully worked out yet
Click to expand...
Click to collapse
Possibly. I did a lot more testing today. LTE signal & speed was better on all CM10 nightlies while it was still performing poorly on all CM10.1 nightlies, Slim Bean stable, and CarbonRom stable. The CM10 nightly from 12/26 (the last CM10 nightly before CM10.1) works great while the CM10.1 nightly from 12/18 (the first CM10.1 nightly) performs poorly. I tried a few more nightlies at random dates for both CM10 & 10.1 also and results were the same. So I'm guessing it has to do with Android 4.2 since all ROMs on 4.1 work fine! I'm not really sure what else I can try.

Try not using nightlies and only use stable or m snapshot. Of course you won't get stable results from a nightly. That's why they are called a nightly.
Sent from my Nexus 7 using Tapatalk 2

GiantJay said:
Try not using nightlies and only use stable or m snapshot. Of course you won't get stable results from a nightly. That's why they are called a nightly.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Haha, true. I just find it really weird that CM10 nightlies are fine while CM10.1 has the problem. The Slim Bean & CarbonRom builds I tried were supposedly stable releases.

GiantJay said:
Try not using nightlies and only use stable or m snapshot. Of course you won't get stable results from a nightly. That's why they are called a nightly.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Eh well it depends. I've found that developer builds and test releases and the such tend to function better than the "stable" releases of the same rom or package
But thats just my experience

[Q] Liquidsmooth 4.2.2 d2spr 3G Slow Bad Reception

I am on the 4.2.2 [OFFICIAL] LiquidSmooth v2.2 - d2spr ROM, and although I really do love many things about it (Very efficient, non glitchy, extremely smooth and very good performance), the reception on 3G is not so good for some reason / bordering on non-functional. Wifi, I believe, is also a bit slower than my previous ROM, but not by that much. I have a Sprint Galaxy S3 that is on Verizon's Page Plus service (3G only, which works fine for me as I am not a heavy net user on the road). I previously had the new JB Goodness Reborn ROM (TW) for Sprint and it worked really well. My reception on 3G was typically always 5 bars and was very responsive and fast on both 3G and wifi. On the Liquidsmooth, the 3G seems to be perpetually at 1 to 2 bars near my house (mostly 1) and 3 at most in the thick of the city (most likely right by a tower), and I do not live that far away from the city at all. A very close suburb, in fact. I have taken it in smaller towns and it is even worse. Extremely slow. It's quite slow near where I live, but extremely slow anywhere out of the city to any degree, which was not the case with JB Goodness Reborn (TW). I even switched ROMs back and forth in the more rural areas, and noticed my Reborn ROM was loading webpages just fine, while the Liquidsmooth was struggling to load a basic page.
I am running a KT747 kernel for both the liquidsmooth ROM and the Goodness Reborn ROM. I was running the included Lean kernel before on the Liquidsmooth, and noticed it was having 3G reception problems as well, so I don't think its the kernel.
And yes, I am aware that AOSP Roms often display the data reception only for the bars as compared to TW with can display both the data reception and voice reception combined in one, but I can tell the speed is ridiculously slower at times on the Liquidsmooth, whereas it is great on the JB Goodness Reborn. Takes forever for a page to load. On top of that, in the middle of the city, the GPS loses data connection, whereas with the Reborn Rom, the connection is rock solid and never fails.. Voice typing / search is also non-functional on the Liquidsmooth, which I do understand is just on a new build, so this does not bother me as much. It would be nice if it would work, but I do understand. I do really like the Liquidsmooth ROM, and its quite a bit better on my battery, but the slowness of the 3G often forces me revert back to the JB Goodness Reborn (especially when I have to use GPS). I have tried to use Hidden Menu apk to check out the 3G settings, but I do not believe it works on this ROM. If anyone has any suggestions or possible solutions, I would be most appreciative. And yes, I would post this to the Official forum, but it is locked and that prevents me from posting any feedback or receiving any possible solutions directly. Thank you for any suggestions in advance.

The Voice works if you update the Google now app. As a slow connection, I would just switch back to your other ROM.
Sent from my SPH-L710 using xda app-developers app

WindroidApps said:
The Voice works if you update the Google now app. As a slow connection, I would just switch back to your other ROM.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That's good to know about the voice with Google now. I just know when I hit voice on the keyboard, it shuts down. Have you noticed your reception / connection speed decrease precipitously with Liquidsmooth 4.2.2 as well? I have read a few posts about how to increase data speeds and tried a few of their possible suggestions with no luck. It's a pity the thread is locked for Liquidsmooth. I am sure I am not the only person having this issue.
Out of curiosity, I have seem many designations besides the one for Sprint phones.. Like RC9, RC 2.2, a deviant ROM. Would one of these work better on the connection issues? Also, I assume I am using the right ROM, as my phone is Sprint...? But I am running on a verizon network, but that never seemed to be an issue with the other JB Goodness Reborn ROM, which was made for Sprint S3.

DO NOT FLASH ROMS THAT ARE NOT SPRINT. You could reallllly mess up your phone!!! I would recommend trying out aokp. It's really good. Link?
Sent from my SPH-L710 using xda app-developers app

WindroidApps said:
DO NOT FLASH ROMS THAT ARE NOT SPRINT. You could reallllly mess up your phone!!! I would recommend trying out aokp. It's really good. Link?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
A link would be great. Thanks. I was considering other Roms as well like the Paranoid ROM or super nexus ROM. Both are jb 4.2.2 compared to my previous ROM that was 4.12 and mb1 Goodness reborn. I have never tried an AOKP ROM. I have been mostly looking for performance and sound. are AOKP Roms compatible with ac!d audio or other such apps for sound? What would you characterize as the difference between AOSP and AOKP? Thanks.

Not a whole lot. Both clean Google roms, I will link the aokp rom in the next post.
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 11:44 PM ---------- Previous post was at 11:40 PM ----------
Here's the link to aokp. Pure AWESOME NESS.
http://forum.xda-developers.com/showthread.php?p=29387442
Also check out the peoples rom. I get great batt life on it.
Sent from my SPH-L710 using xda app-developers app

I made a thread recently about me having worse signal on AOSP roms vs TW roms, now although that isn't your issue specifically, I got a few posts on that thread on how to increase data speeds
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2237516
One method involves messing with your build.prop, and the other involves another system file, both are dangerous so make sure you read my thread entirely on words of caution, and then go ahead and see if you feel comfortable tweaking your system files.

While that's handy, I think he just wants a simple solution. Aokp is a lot like smooth. Anyways, dreamer, you can message me anytime if you need more help.
Sent from my SPH-L710 using xda app-developers app

sevenpioverthree said:
I made a thread recently about me having worse signal on AOSP roms vs TW roms, now although that isn't your issue specifically, I got a few posts on that thread on how to increase data speeds
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2237516
One method involves messing with your build.prop, and the other involves another system file, both are dangerous so make sure you read my thread entirely on words of caution, and then go ahead and see if you feel comfortable tweaking your system files.
Click to expand...
Click to collapse
I have actually tried some build.prop tweaks, but they did not work for me either. I read your post.. did you actually find something that worked? The last entry I read stated that all their suggestions still did not help your connection speed issues with AOSP. I am currently experimenting with DeviantXone ROM 1.5. So far it seems to be faster than the Liquidsmooth Official, but I have not taken it on the road yet and it only shows 1-2 bars as well. I may try to AOKP ROM. Do you know if Ac!d Audio is compatible with AOKP? I really do like those audio apps. Thanks.

I could build you aokp with acid if you can't get it stock.
Sent from my SPH-L710 using xda app-developers app

WindroidApps said:
While that's handy, I think he just wants a simple solution. Aokp is a lot like smooth.
Click to expand...
Click to collapse
Theres really no "simple" soltuion, especially when it comes to increasing data speeds. The "smooth" feel of the rom, or how fast it runs, is for the most part independent of data speeds.
AOSP will inherently never be as good as TW on this phone, mainly being that the S3 wasnt built to run on AOSP. Thats why you get issues like these on non-Nexus/Google phones because of the simple fact that you can only approach 100% functionality since you are building for an unsupported device

WindroidApps said:
I could build you aokp with acid if you can't get it stock.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I might hit you up on that if the versions I have of acid audio are not functional on the aokp link you provided. Sent you a pm with a link of the best sounding versions I have found so far.

CNexus said:
Theres really no "simple" soltuion, especially when it comes to increasing data speeds. The "smooth" feel of the rom, or how fast it runs, is for the most part independent of data speeds.
AOSP will inherently never be as good as TW on this phone, mainly being that the S3 wasnt built to run on AOSP. Thats why you get issues like these on non-Nexus/Google phones because of the simple fact that you can only approach 100% functionality since you are building for an unsupported device
Click to expand...
Click to collapse
An interesting observation... How, in your opinion will an AOKP ROM compare to a TW ROM? Any suggestions of very fast,well performing TW ROMs? I do want to try AOKP and do have a very good TW MB1 ROM, but I am interested in finding the most functional, best performing ROM with this device.. Of course, based on how i use it, as i understand one person's favorite ROM will not be a favorite for someone else who uses it in a different way. Although, it may seem like heresy to some, i am more interested in speed, functionality, and audio quality, as compared to battery efficiency.

dreamer609 said:
An interesting observation... How, in your opinion will an AOKP ROM compare to a TW ROM? Any suggestions of very fast,well performing TW ROMs? I do want to try AOKP and do have a very good TW MB1 ROM, but I am interested in finding the most functional, best performing ROM with this device.. Of course, based on how i use it, as i understand one person's favorite ROM will not be a favorite for someone else who uses it in a different way. Although, it may seem like heresy to some, i am more interested in speed, functionality, and audio quality, as compared to battery efficiency.
Click to expand...
Click to collapse
So you're more interested in features than battery life if I understand correctly? And I personally have never run AOKP on any of my devices, just never really grabbed my attention
For the best and "fastest" TW rom, i would recommend grabbing either TPR or MOAR (because theyre the most used custom stock roms, so have already been modified for performance), then stripping down everything you dont need. As in apps, widgets, themes, skins, etc. All of that. Flashing CrossBreeder and using Greenify effectively can also help keep the device from lagging, there are also build.prop edits to increase audio quality, and things like Ac!d, BeatsAudio, XLoud to improve it too
Just look around for interesting mods and flash em' (making sure that they are either for all android devices or for the Sprint S3 specifically, no international S3 mods unless you want a brick), because this way you'll tailor the rom to your liking and your usage, then just make a backup and you can go flash anything else to test run and maybe check out the features in other roms as well