cm10.1 install and it works all right, except the wassap, I did not arrive until I turn on the screen.
Related
After installing Hashcode's CM 10.1 build on my KFHD 8.9 I'm not getting any bluetooth, after you attempt to turn it on it will hang in the on position greyed out then return to the off position. When I flash the stock ROM, I get nluetooth, and I'm able to pair my bluetooth keyboard. It's just on CM that I can't use it. Am I doing something wrong? Does the ROM just not have bluetooth working yet?
I nede hjelp!!!!
I have a Galaxy TAB 10.1 2 wifi, rooted. First i flashed it whit Cm 10.1 stable, and it worked fine, then i tried JellyBam and that is when the problems started. The statusbar and the soft buttons disapered, i flashed back to Cm, but now it is impossible to install apps, the apps is just blinking a
Second on the screen and thats it. Any ideas?
hmlorentz
Hi,
I've flashed PA many times before on my Nexus 4, and I was using PA 3.99 before I decided to try using CM11 (cause kitkat). Well, CM11 worked fine, but I wanted to go back to PA, however, when I tried flashing the rom, it took much longer than usual, and then when my phone finally booted up, neither the sound nor the wifi would work. I first noticed this when the phone was setting up, as the second thing a new android phone asks you to do is to turn on your wifi. My phone just said "turing on wifi" for a good five minutes until I skipped it. Once I finally finished setting the phone up, I tried turing up the sound but it wouldn't work. Of course, I can't really use my phone if the sound won't work at all, so I decided to flash CM11 again, and then everything was working properly. Since then I've tried PA and CM again, AOKP, and PAC rom, but CM is the only one that worked for my phone. The sound and wifi didn't work on any of the other three roms. If anybody could help, that'd be great!! Otherwise I'll have to stick to CM11 even though I'd like to go back to PA.
SOLUTION FOUND
For anyone with a similar issue: My problem was that I was running CM11, which uses android 4.4, so it seemed that the issue was caused by flashing to a rom that used an earlier version of android. I solved the problem by unrooting my phone and reverting back to 4.2. Then I rooted the device again and flashed PA 3.99, then everything was fine.
noahajohnson said:
Hi,
I've flashed PA many times before on my Nexus 4, and I was using PA 3.99 before I decided to try using CM11 (cause kitkat). Well, CM11 worked fine, but I wanted to go back to PA, however, when I tried flashing the rom, it took much longer than usual, and then when my phone finally booted up, neither the sound nor the wifi would work. I first noticed this when the phone was setting up, as the second thing a new android phone asks you to do is to turn on your wifi. My phone just said "turing on wifi" for a good five minutes until I skipped it. Once I finally finished setting the phone up, I tried turing up the sound but it wouldn't work. Of course, I can't really use my phone if the sound won't work at all, so I decided to flash CM11 again, and then everything was working properly. Since then I've tried PA and CM again, AOKP, and PAC rom, but CM is the only one that worked for my phone. The sound and wifi didn't work on any of the other three roms. If anybody could help, that'd be great!! Otherwise I'll have to stick to CM11 even though I'd like to go back to PA.
SOLUTION FOUND
For anyone with a similar issue: My problem was that I was running CM11, which uses android 4.4, so it seemed that the issue was caused by flashing to a rom that used an earlier version of android. I solved the problem by unrooting my phone and reverting back to 4.2. Then I rooted the device again and flashed PA 3.99, then everything was fine.
Click to expand...
Click to collapse
Thank you !!!
it's Work !
Hi Guys,
Did anyone successfully flashed latest CM12 nightly on your SM-T320 ?
I've tried a few times (wiping everything I could, except exteral sd), but everytime I gave up after waiting about 20-30mins on the first boot. The boot animation was showing properly (sometimes the fps went down, but I think that's because the tab was working).
Is there any secret to making CM12 work on this device ?
Installed cm-12-20150131-NIGHTLY-mondrianwifi.zip and gapps-lp-20141212-signed.zip using openrecovery-twrp-2.8.4.0-mondrianwifiue over rooted T320XXU1BNI1 (stock XEO).
szafran81 said:
Is there any secret to making CM12 work on this device ?
Click to expand...
Click to collapse
Try the 1-30 nightly, also this gapps is much newer http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
CM12 works excellent on this tablet.
szafran81 said:
Hi Guys,
Did anyone successfully flashed latest CM12 nightly on your SM-T320 ?
I've tried a few times (wiping everything I could, except exteral sd), but everytime I gave up after waiting about 20-30mins on the first boot. The boot animation was showing properly (sometimes the fps went down, but I think that's because the tab was working).
Is there any secret to making CM12 work on this device ?
Installed cm-12-20150131-NIGHTLY-mondrianwifi.zip and gapps-lp-20141212-signed.zip using openrecovery-twrp-2.8.4.0-mondrianwifiue over rooted T320XXU1BNI1 (stock XEO).
Click to expand...
Click to collapse
Try a different version. I'm on 20150130 and it is very smooth!
Thank you guys.
1-30 works fine now.
The SM600 works well and has had various version of CM and now Lineage on. The last version to work was the nightly 20170302, which if i install works fine.
Both nightlys since cause the tablet to sit there on a black screen (after you tell TWRP to reboot), with nothing ever appearing. If you turn the tablet off after about 30 minutes , it goes in to a boot loop with a black screen then the samsung logo , then the black screen etc.
Whats changed in the nightlys after 20170302?
I have even tried an advanced wipe, clearing all file systems. Lost for new thing to try , and think it i a fault with the build
many thanks
Any one able to help, Is this the right location to post a question like this , or is the a more appropriate location?