Hi guys, i recently got CyanogenMod 10.1 Nightlies in my Galaxy Note, now i realize that I CAN'T activate my 3G connection, and also got another problem, when I turn off the WI-Fi , the phone signal also disappear , I mean that I can't send messages or make calls. Somebody of you dudes. Help me please!! I'm afraid of what is happening with my device..!
About Phone:
Android Version : 4.2.1
Baseband Version : N7000UBLB2
Kernel Version : 3.0.15-CM-g0b391df
[email protected] #1
Wed Jan 16 06:28:12 PST 2013
CPU : ARMvt Processor rev1 (v7l)
CyanogenMod Version : 10.1-20130116-NIGHTLY-n7000
Compilation Number : cm_n7000-userdebug 4.2.1 JOP40D eng..20130116.062155 test-keys
XaviInsane said:
Hi guys, i recently got CyanogenMod 10.1 Nightlies in my Galaxy Note, now i realize that I CAN'T activate my 3G connection, and also got another problem, when I turn off the WI-Fi , the phone signal also disappear , I mean that I can't send messages or make calls. Somebody of you dudes. Help me please!! I'm afraid of what is happening with my device..!
About Phone:
Android Version : 4.2.1
Baseband Version : N7000UBLB2
Kernel Version : 3.0.15-CM-g0b391df
[email protected] #1
Wed Jan 16 06:28:12 PST 2013
CPU : ARMvt Processor rev1 (v7l)
CyanogenMod Version : 10.1-20130116-NIGHTLY-n7000
Compilation Number : cm_n7000-userdebug 4.2.1 JOP40D eng..20130116.062155 test-keys
Click to expand...
Click to collapse
Try wiping and installing ROM again.
Check if the correct APN is selected for your 3G connection.
warfareonly said:
Try wiping and installing ROM again.
Check if the correct APN is selected for your 3G connection.
Click to expand...
Click to collapse
I've tried that, configured the APN. It doesn't work, the signal doesn't appear to be working.
I've read about restoring /efs. What do you think about that?
XaviInsane said:
I've tried that, configured the APN. It doesn't work, the signal doesn't appear to be working.
I've read about restoring /efs. What do you think about that?
Click to expand...
Click to collapse
Unless, you have a messed up imei there is no use restoring /efs (provided you took a backup in the first place).
Did you try wiping and reinstalling the ROM ?
Try a different modem, maybe the UBLS1 modem. Look in the asylum FAQs, there is a link in there somewhere.
If nothing works, try flashing an older nightly and see if the issue persists.
This is not Asylum ROM
It's safe to flash another modem? I'm new in this.
Update :
I flashed UBLS1 modem (https://www.hidrive.strato.com/lnk/PxORYqo0), it works perfectly!! Thank you warfareonly!
Fix that works for me
Hi.
This worked for me:
- Turn on 3G
- Put your phone on planemode
- Take your phone off planemode
Hopes it works for you too.
Help ive installed CM10.1 Android 4.2.1 ....AND I CANT TURN ON MY BLUETOOTH!!! pls help!!!
i used this app : Bluetooth Fix Repair
and it says 'Sorry, this application can't find your Bluetooth settings folder on this device(GT-P1000)'
About Tablet
Model Number: GT-P1000
Android Verision: 4.2.1
Baseband Version: P1000XXJPZ
Kernel Version: 2.6.35.13-gdafafc9
[email protected] #1
CPU:ARMv7Processor rev 2 (v71)
CyanogenMod version : 10.1-20121206-EXPERIMENTAL-p1-cdesai
wanaqim said:
Help ive installed CM10.1 Android 4.2.1 ....AND I CANT TURN ON MY BLUETOOTH!!! pls help!!!
i used this app : Bluetooth Fix Repair
and it says 'Sorry, this application can't find your Bluetooth settings folder on this device(GT-P1000)'
About Tablet
Model Number: GT-P1000
Android Verision: 4.2.1
Baseband Version: P1000XXJPZ
Kernel Version: 2.6.35.13-gdafafc9
[email protected] #1
CPU:ARMv7Processor rev 2 (v71)
CyanogenMod version : 10.1-20121206-EXPERIMENTAL-p1-cdesai
Click to expand...
Click to collapse
You could try alroger's latest rom: http://forum.xda-developers.com/showthread.php?t=2043421
wanaqim said:
Help ive installed CM10.1 Android 4.2.1 ....AND I CANT TURN ON MY BLUETOOTH!!! pls help!!!
i used this app : Bluetooth Fix Repair
and it says 'Sorry, this application can't find your Bluetooth settings folder on this device(GT-P1000)'
About Tablet
Model Number: GT-P1000
Android Verision: 4.2.1
Baseband Version: P1000XXJPZ
Kernel Version: 2.6.35.13-gdafafc9
[email protected] #1
CPU:ARMv7Processor rev 2 (v71)
CyanogenMod version : 10.1-20121206-EXPERIMENTAL-p1-cdesai
Click to expand...
Click to collapse
I dont think bluetooth even work yet.
Cdesai already stated that in 1st post.
That is well known bug or you can use alroger latest build as suggested by arthur_dent0815
imadork said:
I dont think bluetooth even work yet.
Cdesai already stated that in 1st post.
That is well known bug or you can use alroger latest build as suggested by arthur_dent0815
Click to expand...
Click to collapse
If you really need a reliable bluetooth connection the only real option right now is to restock and go with an ICS build. Otherwise make do, and wait until they have it worked out.
ff
i am running alroger's 10.1 4.2.2 on my P1000
i can detect other device
i can pair with other device
and was able to send files to it
how ever
after the device is paired via P1000
the other device will have it on the device list
but when i try to send file from this device to the P1000
it will not detect
and when i am trying to manually connect to P1000
it says "No profile found"
filteringfields said:
If you really need a reliable bluetooth connection the only real option right now is to restock and go with an ICS build. Otherwise make do, and wait until they have it worked out.
ff
Click to expand...
Click to collapse
I've never really put the Bluetooth (as in AD2P or Earwigs Headphone(s)). on my GT-P1000 into any real world practice yet. So just how stable it is long-term? I know not. But, I have shot many a File mostly (*.apk's) to, and from my GT-I9000 (Galaxy S), or to my Old Man's GT-P1000 to help get his Device set up. We both have CM10 Mod Builds (i.e. Android 4.1.2), and neither of us have had any of the (Frontal) Camera, or Bluetooth problems that are being discussed here.
Mr. Icarus1314 has but, Two choices here, continue using the "SHINY SHINY" and learn to give up both his Camera, and the Bluetooth. Or revert back to a stable CM10 build. I see no benefit at all in reverting all the way down to Ice Cream Sandwich, and its persistent Navigation Bar.
Unfortunately (for us GT-P1000) Users something got broke between CM10, and the .1, and .2 Builds that remains broken still in CM11 (Android v4.4.3 Codename KitKat), and until these bugs get fixed CM10 (Android v4.1.2 Jelly Bean), is pretty much it for now.
I currently have Youngunns AOKP rom installed on my phone which works great.
However I have tried to flash 3 other Roms after clearing Dalvik, Cache and User Data and whenever I use bluetooth and it connects to my car it freezes and then crashes to the Moto unlocked bootloader message and stays there.
The only way to get it to reboot is by holding down the Power & Volume buttons.
Then once the Rom boots up it freezes up and does the same exact thing even if I have the bluetooth off.
Any Ideas what can be causing this as it has done it on Pacman, the other AOKP Rom and Liquid Rom too.
Thanks in advance
Happened to me too with aokp. I haven't found a custom ROM yet that has all I need, so back to stock I went.
Sent from my MB886 using xda app-developers app
I'm on younguns 6/24 AOKP and it does not have the Bluetooth problem.
I'm thinking since I tried the latest versions of the above mentioned roms that maybe they were all built from the same source, thus having the same problem with Bluetooth.
Anyone else running into this problem?
sent from my Atrix HD MAXX
Alright so I just installed the latest liquid ROM v 2.9 and it did the same thing with the BT.
However when I flashed v 2.8. Bluetooth seems to work fine with no bootloop.
So it seems that the latest liquid, PAC, and non-youngunns AOKP all have the same problem.
I hope they fix it in later updates
sent from my Atrix HD MAXX
Guys, A little Help!
I am currently using my old Galaxy S I9000, as my HTC has gone to Service Centre for a week.
Last time I left it with JB Custom Rom (C-Rom Bean v1.9.0 Final) which was working quite OK! Now its too much laggy and slow all over while on JB Rom. I have already tried CM11, CM10.2, Slimkat, SpiritRom and Dark Unicorn (all 4.x.x and above).
Currently I am on CM7.2, which is working quite fine, considering its based on GB 2.3.7. I was also looking for working Lewa OS link, as I liked the one that I installed on my HTC, but couldn't find one.
Can anyone help me to understand what has happed to make this phone go soooooooo slow. Even if I am unable to instal Android 4 and above, I would still need the link for Lewa OS. If anyone has it, that'd be most helpful.
samrat_castle said:
Guys, A little Help!
I am currently using my old Galaxy S I9000, as my HTC has gone to Service Centre for a week.
Last time I left it with JB Custom Rom (C-Rom Bean v1.9.0 Final) which was working quite OK! Now its too much laggy and slow all over while on JB Rom. I have already tried CM11, CM10.2, Slimkat, SpiritRom and Dark Unicorn (all 4.x.x and above).
Currently I am on CM7.2, which is working quite fine, considering its based on GB 2.3.7. I was also looking for working Lewa OS link, as I liked the one that I installed on my HTC, but couldn't find one.
Can anyone help me to understand what has happed to make this phone go soooooooo slow. Even if I am unable to instal Android 4 and above, I would still need the link for Lewa OS. If anyone has it, that'd be most helpful.
Click to expand...
Click to collapse
Mainly, the problem is on the way the different roms use the dalvik vm and the way aforementioned roms are unable to leash cache used. So, my recomendation is a good rom which a good preset over dalvik used of memory and applications like App Cache Cleaner to erase the cache every now and them.
For me the perfect combination is:
1. Stable CM10.2.1 rom
2. Kernel Semaphore 3.3.0 (avoid version 3.3.0s because it gives problems with Netflix, besides version 3.3.0 is perfect and you can activate bigmem with Semaphore Manager App, so 3.3.0s is nonsense) (NOTE: You need odin for installing it, follow this instruction)
3. Gapps: gapps-jb-20130813-signed.zip
4. Semaphore manager app. Settings for Semaphore Manager:
- Smartassv2 Governor: Awake ideal freq 900000 / Up rate 10000 / Down rate 99000 / Max CPU 50 / Min CPU 20 / Ramp up 300000 / Ramp down 300000 / Sleep ideal freq 300000 / Sample rate jiffies 2.
- Deep Idle: Enable
- Lock min freq to 100Mhz: Disable
- Active Scheduler: CFQ
- Bigmem: Enable
5. My build.prop to be placed within /system/ (remember to set for this file rw-r--r-- permissions and change owner to root).
6. A launcher like Zeam Launcher or Lightning Launcher
7. And finally an installed App Cache Cleaner Pro to erase the cache every now and them.
Best.
I have flashed CM10.2.with minimal gapps, but now unable to connect to internet. Tried flashing many times after wiping data, clearing cache and clearing Dalvik cache, but still unable to connect to internet.
EDIT: That as a temp problem with my carrier network. So, I have installed CM10.2 with above details. Working fine so far. Will let you know if there is any problem with this setup.
samrat_castle said:
I have flashed CM10.2.with minimal gapps, but now unable to connect to internet. Tried flashing many times after wiping data, clearing cache and clearing Dalvik cache, but still unable to connect to internet.
EDIT: That as a temp problem with my carrier network. So, I have installed CM10.2 with above details. Working fine so far. Will let you know if there is any problem with this setup.
Click to expand...
Click to collapse
Try to flash the final build 2.2 of SlimBean 4.3 with SlimGapps.
It is faster than CM10.2 and has much better battery life (especially if you use TRDS mode)
tetakpatalked from OPO
samrat_castle said:
I have flashed CM10.2.with minimal gapps, but now unable to connect to internet. Tried flashing many times after wiping data, clearing cache and clearing Dalvik cache, but still unable to connect to internet.
EDIT: That as a temp problem with my carrier network. So, I have installed CM10.2 with above details. Working fine so far. Will let you know if there is any problem with this setup.
Click to expand...
Click to collapse
Good to know, enjoy.
tetakpatak said:
Try to flash the final build 2.2 of SlimBean 4.3 with SlimGapps.
It is faster than CM10.2 and has much better battery life (especially if you use TRDS mode)
tetakpatalked from OPO
Click to expand...
Click to collapse
Thanks for your piece of advice, I tried it long time ago but I still prefer a CM10.2.1 + a tweaked Semaphore 3.3.0 + Zeam Launcher + my build.prop + minor removing of CM apps.
Best.
kuskro said:
Good to know, enjoy.
Thanks for your piece of advice, I tried it long time ago but I still prefer a CM10.2.1 + a tweaked Semaphore 3.3.0 + Zeam Launcher + my build.prop + minor removing of CM apps.
Best.
Click to expand...
Click to collapse
Guys, we have got Android Lollipop 5.0.2 for our device, though an alpha build from @humberos. I am using it as of now, though without Gapps. Its Beautiful! And working!
Download Link: https://drive.google.com/folderview?id=0B7hG2LTQDF3ifjhybEs3TGVGNDlsRk1vS05vNGZOdjVDVXRRbVRwNmVJV2dodGEzdDFmVDA&usp=sharing&tid=0B7hG2LTQDF3ifnZrdWk1MXZYTnZ2dlpUb2JSRHE0Z0l6QmpULWh3SFg2bXdjQTNLbGNMZjQ
More Info: http://forum.xda-developers.com/showthread.php?t=2488037&page=96
samrat_castle said:
Guys, we have got Android Lollipop 5.0.2 for our device, though an alpha build from @humberos. I am using it as of now, though without Gapps. Its Beautiful! And working!
Download Link: https://drive.google.com/folderview...Z2dlpUb2JSRHE0Z0l6QmpULWh3SFg2bXdjQTNLbGNMZjQ
More Info: http://forum.xda-developers.com/showthread.php?t=2488037&page=96
Click to expand...
Click to collapse
I have tried to flash the zip last week but it stucked on "extracting system" every time. It just updated my recovery to TWRP 2.8.4.1, but didn't even reboot.
Maybe it is phone that isn't OK anymore. Its internal memory isn't working correctly anmore.
tetakpatalked from Nexus 7 flo
It takes approx 15-20 minutes for installation. You need to be a bit patient with this
samrat_castle said:
It takes approx 15-20 minutes for installation. You need to be a bit patient with this
Click to expand...
Click to collapse
Cool I tought it failed as the installation process never took that long yet. I will try again then.
tetakpatalked from N7100
OK, I 've flashed it. Lollipop on the i9000. It took 19min until the process was finished.
I have also flashed PA Gapps pico by Tkruzz, all other are probably too big.
The Omni LP alone (just Omni 5.0) is extremely smooth, but quite slow.
After flashing of Gapps (which BTW work perfectly fine) my i9000 has turned into the slowest device I ever used. It is way slower than Eclair, actually just same slow like my S8000 running CM7 from externalSD card.
It takes 15sec to open PlayStore, up to 2min to download and install an app (even smaller apps), about 5-10 sec to react on pressing any button and the device is often running out of memory and soft reboots are the result. It takes up to 15sec until the keyboard appears etc.
Otherwise all important functions work fine, but Lollipop is too big a task for the i9000 and except that it just works, there is simply no many people who would like to use a device with auch slowdowns. Even biggest fans of the i9000 (I might be among them) will have to face the fact that Android 5.0 is actually out of the hardware capacity of the S1
tetakpatalked from Nexus 7 flo
I myself am using CM10.2. Which works fine, with just a bit of lag. Its either that or gingerbread. Anyways, omni 5.0 for i9000 is just experimental at this stage, with promise for a more stable build by @humberos. It may be light on the system, but who knows.
I'd say buy a newer model if we need new OS as software is as good as its hardware and vice versa.
Omni is excellent and very stable, although in Alpha stage. That isn't my point.
LP system cannot get smaller, the i9000 is simply too slow for Android 5.0
It was just an info for people who dream to use Lollipop on i9000. It is a huge slowdown.
I have much faster devices but I don't use LP even there.
tetakpatalked from the legendary i9000 running Omni 5.0
Hey,
I suggest you guys to use SlimBean v2.9 with the latest Slim JB gapps. The phone will be quite fast, despite this device is very old... This version of SlimBean is not available on their site but is here:
https://mega.co.nz/#!6xJnVaBY!qhF1g99N0zE1w6XZd3E2IPgvlBgAJWGrYluZehgajNE
I think further versions are significantly slower and this one offers quite a lot of customization as well. Good luck with the i9000 [emoji3]
aToS88 said:
Hey,
I suggest you guys to use SlimBean v2.9 with the latest Slim JB gapps. The phone will be quite fast, despite this device is very old... This version of SlimBean is not available on their site but is here:
https://mega.co.nz/#!6xJnVaBY!qhF1g99N0zE1w6XZd3E2IPgvlBgAJWGrYluZehgajNE
I think further versions are significantly slower and this one offers quite a lot of customization as well. Good luck with the i9000 [emoji3]
Click to expand...
Click to collapse
Which Android version is that Slim build and why isn't it on the Slim server?
Is there a md5 checksum?
tetakpatalked from N7100
It's an android 4.1.2 and SlimBean version 2.9. It's not on the official site because it's not the latest 4.1.2 version they have distributed. That's the 3.1 if I'm not mistaken.
Sorry I don't have an md5 for the file...
aToS88 said:
It's an android 4.1.2 and SlimBean version 2.9. It's not on the official site because it's not the latest 4.1.2 version they have distributed. That's the 3.1 if I'm not mistaken.
Sorry I don't have an md5 for the file...
Click to expand...
Click to collapse
Good to know. How is the battery life there? With CyanogenMod I remember that 4.1 and 4.2 had terrible battery life, while 4.3 was a lot better.
tetakpatalked from Nexus 7 flo
It can last from morning till the evening but of course depends on the usage.
From what I remember Slim on 4.1.2 was real solid, probably one of my favourite roms. 3.1 wasn't that bad either
Sent from my Note 4
Soryuu said:
From what I remember Slim on 4.1.2 was real solid, probably one of my favourite roms. 3.1 wasn't that bad either
Sent from my Note 4
Click to expand...
Click to collapse
I've tried today build 2.9
It worked fine but for some strange reason it didn't recognize my wifi router...all other networks just fine, but not the important one. I couldn't solve it, tried everything.
But I have feeling that SlimBean 4.3 is at least as good.
Hey, BTW I have filmed Omni 5.0.2, I will try to edit it and upload tomorrow
tetakpatalked from Nexus 7 flo
tetakpatak said:
I've tried today build 2.9
It worked fine but for some strange reason it didn't recognize my wifi router...all other networks just fine, but not the important one. I couldn't solve it, tried everything.
But I have feeling that SlimBean 4.3 is at least as good.
Hey, BTW I have filmed Omni 5.0.2, I will try to edit it and upload tomorrow
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
I don't think I ever got around to trying the 4.3 version, I remember the 4.2.2 version was a bit hit and miss when it came to battery (but then again, all 4.2.2 roms save Gamerzrom and a few others were). By the time the 4.4.x version came out I moved onto the S3 so I can't vouch for that, but Slim roms are pretty good
And you legend, thanks a lot
So my radio came in today and android auto doesn't work. It says my phone was not compatible. I have a rooted note 4 running android 5.0.2 (cm 12).
killa2009 said:
So my radio came in today and android auto doesn't work. It says my phone was not compatible. I have a rooted note 4 running android 5.0.2 (cm 12).
Click to expand...
Click to collapse
I had the same issue. Something is missing from the CM12 based ROMs. Android Auto will work with the International version of the Vision team's ROM, but the ROM isn't stable. Random reboots, contacts FCing and battery pulls are common. I went back to my Nexus 5 for stable AA use.
mindtrip1016 said:
I had the same issue. Something is missing from the CM12 based ROMs. Android Auto will work with the International version of the Vision team's ROM, but the ROM isn't stable. Random reboots, contacts FCing and battery pulls are common. I went back to my Nexus 5 for stable AA use.
Click to expand...
Click to collapse
OK, thanks
mindtrip1016 said:
I had the same issue. Something is missing from the CM12 based ROMs. Android Auto will work with the International version of the Vision team's ROM, but the ROM isn't stable. Random reboots, contacts FCing and battery pulls are common. I went back to my Nexus 5 for stable AA use.
Click to expand...
Click to collapse
What ROM are you using ?? Ive heard that the ASOP ROMS work well . Im going to be testing this real soon and i will let you know ...