Hello, all! Long time lurker, but given this great new tablet I got, and the nice, tight nit community here, I thought I would try to ask some questions and perhaps get involved a little bit more.
I am not new to custom ROMs, as I used to do them heavily with my T-Mobile G2 (Desire Z) and my older tablet, the Asus Transformer TF101. I am new to the G Pad, though, having had it less than a week. Now, to the questions...
I started with using the stock ROM, and it's actually not bad, but some of the flakiness with the SD card, along with Amazon Appstore unexpectedly flaking out on me, was impetus to get me to try some ROMs.
First I tried the AICP nightly, then I tried Infected's CM nightly. In both cases, there was the brightness issue (which can be fixed once it's booted up, but it is annoying at first). That's not the end of the world.
What really did bug me though was that none of my 5GHz wifi bands were showing up, and especially with AICP, the wireless in general seems flaky. Can anyone speak to this, or perhaps am I doing something wrong?
In the meantime, can someone recommend a stock-based rom that easily installs with TWRP 2.7.0.1? I could not get a previous version to work properly, and LRS G Pad would not install without rebooting in the middle on 2.7.0.1. I had a heck of a time attempting to install 2.6.3.2... so no, that is not an option. I rewiped my tablet dozens of times trying to get it to work.
Thank you for your help!
Have you checked the country setting under advanced wifi settings? I think that influences which wifi bands will work.
That makes sense! Thank you! I should have known this also, since I was setting up my laptop a few weeks ago and had to set the country code there also.
Thanks again - I'll give it a shot later once I run another nandroid.
To my surprise, 5GHz just worked on the latest 5/22 CM11 build. I ended up going to LRS for other reasons, but not that one.
Related
Need some help here. I never usually need help, been modding everything possible on Android for years now. But can't figure this one out, getting worried.
Had my LTE Nexus since launch day. No issues like this before.
Been on all Team Kang AOKP toro ROM updates since release, always on the latest. Stock kernel. Was on build 20 since it came out.
Yesterday at work, had a few bugs from probably not data wiping from build 19, so I wiped it all and re-flashed 20 again. Restored Titanium and started re-setting things up, I believe these are the only things I did. I was at work where I would normally have minimal, but some, service.
Ever since around there, I have not once had a bit of 3G or 4G service. I have not seen the 3G logo for even an instant, only few, gray bars. Wifi works fine of course. It's possible I even lost service before wiping and re-flashing, but I can't recall or didn't notice.
I tried all the usual stuff, wiping everything again, re-flashed AOKP 20, re-flashed other/older ROMs, re-flashed latest radio, restored old Nandroid backups, pulled battery and sim card and put back/rebooted...NOTHING IS WORKING. Also, I have driven through several towns since yesterday so I know it's not a local outage. Also, other people with Verizon phones here have service fine.
I have basically torn the phone down software-wise and nothing has fixed the issue. I still have no service. Each time I re-flash a ROM, it always makes me go on Wifi when it wants me to sign into Google...it never picks up mobile service then or after.
The About>Status screen says:
Network: Verizon Wireless
Signal Strength: shows an actual number reading that changes
Service State: In Service
Roaming: Not roaming
Mobile network state: Disconnected
Please suggest things I can try, but I guaranteed I have already tried them. Can't understand or imagine what is causing this, because I did nothing different than I normally do.
Also, I posted this on Rootz as well, and many replies so far. Still no luck though.
If you have an idea I can try, maybe post there instead at this point for me?
Thanks guys in advance.
http://rootzwiki.com/topic/16407-bi...ile-service-since-yesterday-tried-everything/
It seems a radio problem. Try to flash the stock ROM from Google.
tigajr said:
It seems a radio problem. Try to flash the stock ROM from Google.
Click to expand...
Click to collapse
Well I did go back to many random earlier, more stock custom ROMs in hopes of a fix, but nothing so far. I am currently back on the stock 4.0.2 ROM that is rooted and deodexed by Bigxie, but I guess I can go all the way back to stock 4.0.1 or 0.2. Will try now.
Went to Verizon and it looks like the sim card swap did it. The girl there was nice and did it without hesitation for me.
She showed me in her computer how under my family account, it wasn't even fully showing my device or something like that. Not sure if it wasn't there at all or if it just didn't show that I had a 4g phone activated on the account...but I'm sure it was related.
Sucks to have to get a swap and still don't know what caused it or if its related to flashing roms, but at least it works! No issues since...
It is possible, but unlikely and no reasonable explanation, that your sim somehow got affected doing all the flashing and stuff.
Sent from my Nexus in Texas.
Hey everyone, just came over here from the HTC One X ( AT&T ) forums, smashed the screen on it and used an upgrade to get an AT&T SGS3, loving it so far. Had it rooted and custom recovery, and was on a custom ROM not even an hour after getting home. Anyway, onto the main part of this post.
I tried CM10 ( the 11/01 and 11/02 nightlies), both of the AOKP, and LiquidSmooth, and on all of them, my WiFi stability is not there. It seems to disconnect at random, if connect at all, and when i walk out of range of the router, and then come back, it will not automatically reconnect until i go into airplane mode. Trying to turn WiFi itself off and back on does not work - it won't turn off/back on, it sticks at what it was at.
TouchWiz ROMs, everything works just fine. I'm pretty sure it was working on MIUI as well, but i didnt have MIUI on there long enough to properly test it.
I am using the UCLH9 radio, since AFTER searching the forums pretty in-depth, i found that all radios prior to UCLH9 had wifi driver issues. Flashing this new radio did NOT fix the issue.
I have tried both stock CM10 kernel AND Ktoonsez's kernel (which is pretty freakin awesome, btw! :good: ) and still have WiFi problems.
I have tried flashing ROMs through both TWRP and CWM Recoveries, and have done a full wip of /system /data /cache and /dalvik-cache 3 times each before flashing a ROM.
I'm a pretty competent at flashing ROMs and troubleshooting problems, I am a pretty well-known beta-tester for multiple Sense and AOSP ROMs over at the One X forums, and I have a very good knowledge of how to work ADB and Fastboot. I've been around XDA for a little while, and I know the way of things around here. (don't want you guys thinking im just another a$$hole that threw a post up the second a problem occurred without doing some research first!)
If anyone has ANY ideas as to what may be causing the wifi drivers to crash, PLEASE fill me in.
I've tried all the same things you have and have had no success. The best wifi stability I got was the AOKP_d2att milestone1 w/ lean kernel combination, but wifi would stay connected for 3-5 minutes as opposed to 30 seconds.
I briefly tried CM9, but that still had wifi issues. I might try a few other ICS roms
I came across these threads that documented the problem across other phones:
code.google.com/p/android/issues/detail?id=34942
code.google.com/p/android/issues/detail?id=36993
I've decided that I'm stuck with ICS until the official JB comes out.
Avram
awalts said:
I've tried all the same things you have and have had no success. The best wifi stability I got was the AOKP_d2att milestone1 w/ lean kernel combination, but wifi would stay connected for 3-5 minutes as opposed to 30 seconds.
I briefly tried CM9, but that still had wifi issues. I might try a few other ICS roms
I came across these threads that documented the problem across other phones:
code.google.com/p/android/issues/detail?id=34942
code.google.com/p/android/issues/detail?id=36993
I've decided that I'm stuck with ICS until the official JB comes out.
Avram
Click to expand...
Click to collapse
Well, I flashed Intergalactic, which is a modded Stock ICS TW ROM based on the AT&T firmware. Shortly after, I reinstalled TWRP recovery and flashed task's AOKP with ktoonsez's kernel, and WiFi works!
This is similar to an issue we had several weeks back with CM10 based ROMs on the HTC One X, you couldn't get LTE unless you flashed a ROM based on Android 4.0.3, it was something with CM10 obviously, because it was fixed in one of the October nightlies iirc.
Try flashing intergalactic and then task and ktoonsez aokp and see if your WiFi is working and let me know
Sent from my SGH-I747 using Tapatalk 2
Nope, no luck this way either.
Wifi under Intergalactic works fine.
TWRP flash AOKP milestone 1 alone, with the ktoonsez kernel, or with lean kernal and my wifi still hangs after ~1 minute of inactivity. The phone grinds to a halt. If you can get to the settings, it says that I am connected to my router, but shows no signal bars. If you can then turn wifi off, the phone un-freezes, and (except for no wifi access), the phone is back to normal. If you now turn wifi back on, it stays up for another minute or two and goes down again.
I'm open to any other suggestions.
Thanks though
Avram
i am using task and ktoonsez rom....when i first installed it, i noticed wifi dropping, it was annoying.
kinda dont happen anymore. The only 2 things i can think of that might have helped me is; i flashed a new modem i747MVLLE8(I'm with rogers), and under Wi-fi(menu/advanced), i unchecked poor connections.
also my router is 2.4ghz and 5ghz band, but i am connected to the 2.4ghz band.
hope it helps somehow.
I had horrible dropouts and speed with my last WiFi router. I forget the name/model but it was a new model (released this year) that had great reviews.
I went back to my old router and all my wifi problems disappeared.
I do get dropouts once in awhile still. But I haven't done a clean ROM install in awhile.
When I'm running an AOSP Rom, my Wifi only scans for networks after a fresh boot. Once it has connected to a network, no more scanning happens, no matter how often I tell it to. It's quite an annoyance when I have to reboot my phone every time I leave home and want to connect to a coffeeshop Wifi outside.
Once it is connected, there are not further issues - signal is good, no random disconnects or anything. Just no scanning.
Everything works fine on stock, and I've successfully tried ViperX with Sense 5, but all AOSP Roms I've been trying recently had this behavior - I have no idea what's causing it. Maybe it's an issue with the CM kernel (most Roms use some form or other of it)?
I really have no idea. Thought I'll post a question here while I go do some more troubleshooting of my own.
I also just grabbed a snippet of what I hope is the relevant part of the logs: https://paste.xinu.at/WO9zZ/
On second thought, maybe it's not AOSP based, but rather 4.3. I haven't spent much time on 4.2 with this phone, so I don't remember if the problem existed back then. If I don't find a solution, I will downgrade later to make sure.
Solved Somewhat... Not really. Worked-around maybe.
I rolled back to CM 10.1.2, and the problem went away. Seems like it wasn't AOSP causing the problem, but the new always-on feature in 4.3, which allows scanning for networks even though Wifi is switched off. I've done some searching, and other people on all kinds of devices have had problems with Wifi since this change was implemented.
Once I disabled this feature and toggled Wifi off/on once, the problem seems to be gone on CM 10.2. Not quite a proper solution, but I guess I can live with that for now, I don't really have the time, energy or experience to look into this further. Maybe somebody more enlightened than I has a proper solution.
Hi, I have a problem with O-Click and Cyanogenmod. I have the 32GB Oppo N1 and while the O-Click works fine with ColorOS I haven't managed to make it work successfully with Cyanogenmod. I have upgraded the O-Click firmware via ColorOS.
Has anyone else encountered this problem?
Sent from my N1 using Tapatalk
aeacus said:
Hi, I have a problem with O-Click and Cyanogenmod. I have the 32GB Oppo N1 and while the O-Click works fine with ColorOS I haven't managed to make it work successfully with Cyanogenmod. I have upgraded the O-Click firmware via ColorOS.
Has anyone else encountered this problem?
Click to expand...
Click to collapse
If I remember correctly, it should be able to work the same way. Ensure Bluetooth is on, go into the O-Click settings, then search. After you do that, just click the O-Click one time so it starts searching for the phone. It should be able to pair.
I did run into a problem once where I had to go to the Bluetooth settings and forget the O-Click because it wouldn't connect. It was paired, but it never actually connected. Once I did that, I just paired them again and it worked. You could give that a shot if it shows as paired in the Bluetooth settings. Just delete it out of there and try again.
I've deleted it from bluetooth settings but it didn't help.
Also after I tried connecting to it via Buttons>O-Click settings I can't connect to it from Bluetooth menu either. Only if I disable and enable Bluetooth again I'm able to pair via Bluetooth menu only. But to get it to work I have to connect to it via button settings.
Does anyone know of a way to hard reset the O-Click device; When I opened it for the first time I remember it was blinking a green light. Is there anyway to put the device to that mode again? I tried to long press the button but nothing happens.
Sent from my N1 using Tapatalk
After searching in oppoforums I've found out that O-Click has problem with CyanogenMod. Original thread here http://www.oppoforums.com/index.php?threads/8100/
Has anyone managed to get it working in CyanogenMod?
Sent from my N1 using Tapatalk
aeacus said:
After searching in oppoforums I've found out that O-Click has problem with CyanogenMod. Original thread here http://www.oppoforums.com/index.php?threads/8100/
Has anyone managed to get it working in CyanogenMod?
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
There is an open Bug-Report about it: https://jira.cyanogenmod.org/browse/CMN-1
No one working on it as of now (at least no one has assigned to the task).
It seems like the O-Click connectivity issue only occurs with regular users. Every review site that talks about the CM edition of the N1 doesn't bring up any connectivity issue. in fact in review videos they show that it's working... What are they doing differently that everyone else seems to be failing at.. :S
Espada04 said:
It seems like the O-Click connectivity issue only occurs with regular users. Every review site that talks about the CM edition of the N1 doesn't bring up any connectivity issue. in fact in review videos they show that it's working... What are they doing differently that everyone else seems to be failing at.. :S
Click to expand...
Click to collapse
A user is A user...
No difference...
((developer options and rooting is different.))
But what they're having is the earlier version of the CM edition before the "update" that "broke" the O-Click functionality...
Silence in the woods...
And still no reaction from CM about this issue. Looks like we got screwed. The N1 is not tight to CM at all. There is not even a Forum for it on their Pages and the N1 is not in the List of Supported (or unsupported) Devices.
Guess, I'll flash the Color-OS, install Apex or Nova and wait for a fully working Omni Release.
Goodbye CM...
schauol1 said:
And still no reaction from CM about this issue. Looks like we got screwed. The N1 is not tight to CM at all. There is not even a Forum for it on their Pages and the N1 is not in the List of Supported (or unsupported) Devices.
Guess, I'll flash the Color-OS, install Apex or Nova and wait for a fully working Omni Release.
Goodbye CM...
Click to expand...
Click to collapse
I tried running ColorOS and sure O-Clicked kinda worked. I found the battery life to be pretty bad and the phone ended up using more RAM than compared to CM10.2 :S
When O-Click was connected to the phone in ColorOS, it worked like it should. It's when it gets disconnected when you try to reconnect it. I was forced to use both the device and the phone to reconnect which kind of defeats the purpose of the "locate" phone feature. I'd get the usual red blink when it's disconnected. lol
Maybe OmniROM will be better when it's complete. Or hopefully the CyanogenMod team still cares about their first official CM backed phone. lol.
Espada04 said:
Maybe OmniROM will be better when it's complete. Or hopefully the CyanogenMod team still cares about their first official CM backed phone. lol.
Click to expand...
Click to collapse
started working on it again just yesterday
Hope to have som app to test by end of the week
New announcement from CM team is pretty discouraging.
http://www.cyanogenmod.org/blog/a-case-study
So what this basically means is that N1, the first Cyanogenmod phone ever is actually not for "regular" CM users.
A user selecting any phone supported by CM team (i.e. Samsung Galaxy S3) will always be updated with the latest versions while N1 users will be on the waiting list. Too bad as I bought the N1 to support the team but if I want the updates rolling in I have to go with Omnirom.
Well i guess this is what they call "The end of an era!"
All People Update CM. there is the cm-11-20140724-NIGHTLY
First update to the latest nightly in CM page, after that you can update via OTA in your phone, there is Daily updates!!
O-Click, Works, meaby a second lag (while focusing?)
O-Touch Works, not as the touchpad of your lap but works, And for some reason changing the VM to ART works better for me.
3G works
Battery last very good, and its suposed to las more in stand-by if you use ART instead of Dalvik
ART works well by the way.
I have been using a galaxy note 8.0 from over seas as my phone in the states for some time. calling was in and out on older cm11 builds, but i wasnt really concerned.
however, just recently, it has decided not to receive data from att. I can still send text messsages, bluetooth is up, wifi works fine, but data just wont connect. now, ive recent reflashed my modem, like the last time it did this, and after an apn reset and reboot, it picked up. I only stayed connected for about 4 hours, and its back down again. Im currently on the latest nightly from cm 12.1 (i was on one from a little while back, data went down on that build, so i figured an update couldnt really hurt)
now, i seem to be the only human with this problem. no threads directly relate, but some threads have tossed me some directions. so far, i need to figure out if my modem build is even the right one. from there- im lost. sorry. ive been way out of this game for so long. anyone have a direction to point me or need any information from me?
mods: i figure posts on this are sparse enough i might be okay to ask. I did search, and if theres a thread covering this, i must really suck at looking