Joker
Thanks to all the dev's and you for your hard work on this project.
I have two problems tho, I have a VM notification icon that will not go away, since a clean 4.3 flash
Also, even with a clean flash to 4.4 my camera will not work.
Any help would greatly appreciated.
In regards to the voicemail notification, someone posted a modified phone apk that deals with this in android development. Alternatively, you can clear date I think after each boot and it should go away.
Dunno about your camera issue. Perhaps restore back to a cm9 version with it working and flash the latest build on top of that?
Sent from my NookTablet using Tapatalk
Related
This is the NFC file from April 2012 for the Note. I read it as the GB update. I have tried flashing it a few times on CM10 nightly 10/8 and a few earlier builds and have not had any luck. I am coming to the conclusion that perhaps it is the version of CWM instead? I don't have a tight enough grasp on how to convert this file over to flash correctly. I have tried changing the binary-installer file and didn't have luck with that. Any help is greatly appreciated. Here is a link to the file source.
http://www.xda-developers.com/android/unlock-nfc-on-att-samsung-galaxy-note-stock-rom/
Thanks again.
Anyone?
Sent from my SAMSUNG-SGH-I717 using xda premium
cm10 has nfc built in already. you dont need that file. and it is for stock rom which means touchwiz so not compatable with cm.
s89281b said:
cm10 has nfc built in already. you dont need that file. and it is for stock rom which means touchwiz so not compatable with cm.
Click to expand...
Click to collapse
My NFC has never worked with any JB rom. It works like a champ on stock rom. I'm just trying to cover all my bases. Very hard to trouble shoot when you really don't know where it is going wrong. I have wiped the phone completely, done dirty installs on top of the stock rom. If you can name it, chances are that I've tried it. Even tried EVERY kernel I could find for every version of android for the Note. Very frustrating because it is something simple that not many people use, but I have NFC tags all over that I used all the time.
Thank you for your reply though.
Hi All. Has anyone successfully got the internal storage encryption on AOSP roms to start AND finish? When I have wiped/wiped/changed hboot and flashed either an ICS AOSP rom (CM10 AOKP), my phone will just hang on a black/blank screen. It never shows the encryption progress percentage. I've tried some ICS Sense roms as well and the only that encrypts (i can use exchange mail at work) is Coolexe's Evo3D Cool Sense roms.
Thanks.
Unless anybody is a encryption wiz your best bet is to go to the ROMs perspective threads and direct your question there.
Thanks for the reply. Wasn't really sure if the question belonged in those threads or here. Will ask around.
Sent from my GT-P3110 using Tapatalk 2
McClair672 said:
Hi All. Has anyone successfully got the internal storage encryption on AOSP roms to start AND finish? When I have wiped/wiped/changed hboot and flashed either an ICS AOSP rom (CM10 AOKP), my phone will just hang on a black/blank screen. It never shows the encryption progress percentage. I've tried some ICS Sense roms as well and the only that encrypts (i can use exchange mail at work) is Coolexe's Evo3D Cool Sense roms.
Thanks.
Click to expand...
Click to collapse
Nope.
I was running CM9 on p4wifi with encryption enabled and cwm 5.x. It worked just fine.
I restored to stock, then install cwm again, along with CM10 12/6 & 12/8 nightlies. Neither version has working encryption.
The option to encrypt is available under security. I add a passcode/phrase, start the process, but _no encryption actually happens_.
Are there any changelogs or git/cvs logs or build logs available so that we can see what is going on?
Any cyanogenmod devs here that can shed some light?
Thanks
I've been keeping half an eye on developments with CM9/10 for the Galaxy Tab 10.1 over the last few months and I'd now like to take the plunge and start using the CM10 nightlies on my P7510.
My wifi only Tab is currently running stock ICS 4.0.4 and has NOT been rooted. Looking through the threads in this forum, it looks like I need to first flash a custom recovery (pershoot's CWM?) and then I can use the custom recovery to flash CM10.
Last night, I tried following the instructions on CyanogenMod's wiki page for the P7510 but hit a problem very early on with the Heimdall utility reporting a protocol error during the recovery flashing. It seems a few people are having this problem and it may be a bug in the Heimdall utility.
Other methods I have read about include this super-easy method (but unfortunately that does not work for stock ICS devices) and also using ODIN, which I believe to be Windows only. I'm running Ubuntu on my laptop but do have access to a Windows machine if need be.
Could anyone offer some advice on the simplest way to go about doing this, specifically for taking a stock ICS 4.0.4 P7510 to running CM10 nightlies?
Thanks!
Hi. Recently tried to do exactly the same thing i.e. install CWM and then CM10 (which by default is rooted) and had the same problem.
I used ODIN instead. My guide through the process was s0ckm0nkys '[How-To] Root/Unroot The SGT 10.1 GT-P7510 USA Retail WiFi HoneyComb Only' pinned thread at the top of the android development sub-forum for the galaxy tab, which has some good links to youtube videos which help - just be careful of any files linked to as they are out of date (don't let the title put you off as all you are interested in is installing CWM).
The rest of the process as per the cyanogenmod wiki worked for me.
be aware that although you will have access to OTA updates after this which make this whole process much easier on an ongoing basis, I don't believe this will work for the upcoming CM10.1 which seems to require a reinstall.
I hadn't thought to look in the development sub-forum but that looks like a great thread, thanks!
After my initial post, I actually went ahead and borrowed a Windows PC to use ODIN to flash pershoot's ClockworkMod 5.5.0.5 to my Tab. I'm happy to report all went well! I've just done a nandroid backup so before I go ahead and install CM10, I'm going to check out those videos, just in case there's anything I should make note of.
Cheers mate, and thanks for the heads-up on the CM10.1 reinstall thing. I'll hopefully be posting back here shortly when I'm running CM10.
Now running the latest CM10 nightly (20121217) and all good so far.
For anyone in same boat as I was a couple of hours ago, check out the videos in the thread tomorrowmanuk mentions above and you'll be up and running in no time. The only changes I made were to use a more recent ClockworkMod recovery than shown in the videos. I used 5.5.0.4 which at this time is the latest one provided by pershoot (I think).
monkeyhybrid said:
Now running the latest CM10 nightly (20121217) and all good so far.
For anyone in same boat as I was a couple of hours ago, check out the videos in the thread tomorrowmanuk mentions above and you'll be up and running in no time. The only changes I made were to use a more recent ClockworkMod recovery than shown in the videos. I used 5.5.0.4 which at this time is the latest one provided by pershoot (I think).
Click to expand...
Click to collapse
Congrats I found the CM10 update definitely gives the tab a new lease of life.
tomorrowmanuk said:
Congrats I found the CM10 update definitely gives the tab a new lease of life.
Click to expand...
Click to collapse
Yep, it does that alright. I'm looking forward to CM10.1 too, for Android 4.2's multiple user support so me and my misses can both use it without messing around with each other's settings all the time.
By the way, do you find CM10's default font looks a little less smooth at small sizes than the older stock one?
Does everything on the Tab work with the latest CM10 nightlies (cameras, mic, etc)?
kielby said:
Does everything on the Tab work with the latest CM10 nightlies (cameras, mic, etc)?
Click to expand...
Click to collapse
As far as I can tell, everything is working well so far. Front and rear cameras work although possibly a bit of lag on the front camera's live preview (which I have seen reported elsewhere). I had also read that 720p recording with the rear camera wasn't working on earlier builds but seems to work fine on mine with the latest nightly (20121217). The camera preview for the rear video camera does not fill the screen for some reason but doesn't stop anything working. A quick test just now of the microphone shows that as working too.
I'm only half a day in to testing, reinstalling some apps, etc, but it's been very smooth and pain free. The interface is definately smoother now, both on the homescreen and within apps. I'm happy to say goodbye to TouchWiz too.
I'll post back here if I hit any problems or bugs.
monkeyhybrid said:
Yep, it does that alright. I'm looking forward to CM10.1 too, for Android 4.2's multiple user support so me and my misses can both use it without messing around with each other's settings all the time.
By the way, do you find CM10's default font looks a little less smooth at small sizes than the older stock one?
Click to expand...
Click to collapse
Can't say I'd noticed any major font differences.
With regards 10.1, the earybird version has popped up on pershoot's droidbasement.com/db-log (man deserves a medal for his work on this tab). Will keep an eye on CM10 preview development thread to determine when to jump to 10.1
tomorrowmanuk said:
With regards 10.1, the earybird version has popped up on pershoot's droidbasement.com/db-log (man deserves a medal for his work on this tab). Will keep an eye on CM10 preview development thread to determine when to jump to 10.1
Click to expand...
Click to collapse
Ah, coool! It's great to hear pershoot is on the case. Top man! I'll keep an eye on his blog for developments...
Went ahead and updated my wife's Galaxy Tab last night, everything went smoothly and Tab is working great.
I think I followed pretty much the same instructions as instructions as you:
1) Installed Samsung USB drivers and downloaded Odin 3.0.7
2) Flashed CWM 5.5.0.4 from pershoot using Odin
3) Downloaded latest CM 10.0 nightly from get.cm for Galaxy Tab, and 10.0 gapps to sdcard
3) Booted into recovery, created nandroid backup
4) Factory wiped, wiped cache, wiped dalvik cache
5) Flashed CM, then gapps
6) Reboot
Thanks for the heads up that prompted me to look into this again!
I'd recommended you to use ODIN instead the other things
1. Copy the .zip to /sdcard root
2. Flash ClockWordmod 6.x.x with ODIN 1.85 (You can find this in Development Area/Google it)
3. Apply .zip through ClockWordmod. Don't forget to Wipe Cache&Dalvik Cache
4. You're done, i've been using pershot's build for more than two month. His build are really stable with a minor bugs.
And the CyanogemMod 10.1 Android 4.2.1 is seriously fast. I would recommended this to you
hope this helps!
I'm so frustrated by now, because I have issues with receiving sms since I started to use kitkat. I had this issue with Pound rom, with Sibermod, and now with official cm11 snapshot. All roms that I used are cm11 based, I tried different kernels, personal preference is apolo kernel. Well the problem looks like following :
1. I clean flash rom, gapps, kernel, clean caches, reboot, sms works, I receive the test.
2. Restore apps, using tb or Google backup (tried both) sms still working
3. After night of charging, sms are no longer received.
I can send messages but cannot receive.
The only way to fix it would be to reset the phone, wipe everything and flash rom again.
I don't know if this is related but since flashing cm11 official I keep getting cell broadcast notifications every 5-10 min. I have disabled every possible broadcast notification but it still pops up.
Sent from my GT-I9100 using Tapatalk
Anyone?
Sent from my GT-I9100 using Tapatalk
Same problem
I think this thread needs a bump.
I've been having the same problem. I was running 4.4 on my D2spr for months with only minor bugs. I ran Slimkat up to stable build 4, Gummy 4.4.2, and a few others with no problems. About a week ago I flashed CM11, and after about 30 minutes I couldn't receive sms or mms anymore. I tried to disable Voice+ (didn't work), I tried installing a third part sms app (go sms pro) and that didn't work, I tried flashing a different GApps package (went from PA GApps to Slim's I think) that didn't work either.
Then I happened to buy a bricked S4 L720. I got it up and running and flashed Gummy 4.4.2 onto it at first, I couldn't get texts. So I flashed Liquidsmooth 3.0 (4.4.2) and still cannot receive sms or mms. CM11 doesn't work either and neither do different GApps on this phone.
Obviously I assume Sprint but they are screwing me over with their whole "Oh your phone is rooted and we're gay boys." So I'm attempted to flash the stock firmware in hopes that either that will fix it or Sprint will help me after that.
In the mean time, has anyone found a solid solution to this yet!?
trustinsimpson said:
I think this thread needs a bump.
I've been having the same problem. I was running 4.4 on my D2spr for months with only minor bugs. I ran Slimkat up to stable build 4, Gummy 4.4.2, and a few others with no problems. About a week ago I flashed CM11, and after about 30 minutes I couldn't receive sms or mms anymore. I tried to disable Voice+ (didn't work), I tried installing a third part sms app (go sms pro) and that didn't work, I tried flashing a different GApps package (went from PA GApps to Slim's I think) that didn't work either.
Then I happened to buy a bricked S4 L720. I got it up and running and flashed Gummy 4.4.2 onto it at first, I couldn't get texts. So I flashed Liquidsmooth 3.0 (4.4.2) and still cannot receive sms or mms. CM11 doesn't work either and neither do different GApps on this phone.
Obviously I assume Sprint but they are screwing me over with their whole "Oh your phone is rooted and we're gay boys." So I'm attempted to flash the stock firmware in hopes that either that will fix it or Sprint will help me after that.
In the mean time, has anyone found a solid solution to this yet!?
Click to expand...
Click to collapse
Agreed that thread needs to be bump. I don't know if it's cm11 issue or kitkat before 4.4.3 but I gave up on the issue and flashed neat rom based on stock, works great but as flashaholic I feel sorry to not be able to use the latest version.
brack11 said:
Agreed that thread needs to be bump. I don't know if it's cm11 issue or kitkat before 4.4.3 but I gave up on the issue and flashed neat rom based on stock, works great but as flashaholic I feel sorry to not be able to use the latest version.
Click to expand...
Click to collapse
I know what you mean. Right now I'm enjoying LS 3.0 and there are a couple others I want to try, the thought of going back to touchwiz disgusts me.
One thing though. On my GS3 I wasn't able to receive Hangouts IM on any ROM from a specific person. Now I can receive them from him on my GS4! Definitely worth not being able to receive sms (highly sarcastic.)
I resolved my issue. After all that trouble and even though I disabled voice+ like everyone said I figured out in my regular voice app I had to go to
Sent from my SPH-L720 using XDA Free mobile app I had to go to setting>sync and notifications and turn texts to go to my messaging app.
Worst user error experience of my life haha.
I pulled my old Vibrant out of a box and thought I'd try to run a newer version on android on it, but I haven't been about to make heads or tails of the development forum. After 3+ hours of fiddling and 3 or 4 programs downloaded, I'm at a loss. The phone currently has Bali kernel and Bionix-V FishmanMod which I loaded on it in 2011 or 2012 and have no recollection of what I did. :silly:
I think my questions are:
Do I need to revert to stock? Because odin refuses to recognize my phone in download mode. It sees it fine when it is booted normally.
Otherwise, what do I need to do to update the kernel and put kit kat on the phone?
If there's anybody out there, thanks and I tried really really hard and I'm just really confused.
I think it would be best for you to go back to stock first.
1. Make sure that your drivers are properly installed
2. Try different usb ports, reboot computer/phone, different usb cable if Odin won't recognise the phone.
Honestly, going back to stock won't help much. Install a JB rom and or kernel and from there install a kitkat kernel then rom. In that order. Make sure you wipe data and cache completely to make sure there isn't any problems.
epicboy said:
Honestly, going back to stock won't help much. Install a JB rom and or kernel and from there install a kitkat kernel then rom. In that order. Make sure you wipe data and cache completely to make sure there isn't any problems.
Click to expand...
Click to collapse
Great timing with this thread. I borked the screen repair on my S4 and need to use my Vibrant again for a while.
ICS Kiss 3.1.10 needs an update.
rBGH said:
Great timing with this thread. I borked the screen repair on my S4 and need to use my Vibrant again for a while.
ICS Kiss 3.1.10 needs an update.
Click to expand...
Click to collapse
I was thinking about updating CM7 or CM9. Building with latest sources. I personally had many speed issues with ICZenwich. Is that non-existant on ICS Kiss?
What do you guys think? Should I upload the latest builds of these ancient android versions?
epicboy said:
I was thinking about updating CM7 or CM9. Building with latest sources. I personally had many speed issues with ICZenwich. Is that non-existant on ICS Kiss?
What do you guys think? Should I upload the latest builds of these ancient android versions?
Click to expand...
Click to collapse
ICS Kiss does have speed issues. I very much want to update but don't want to go through the plug and chug of finding one I like. If someone can recommend a stable, vanilla, something or other, I'd appreciate it.
I found what I'm looking for. Yea, CM should fit the bill nicely.
rBGH said:
I found what I'm looking for. Yea, CM should fit the bill nicely.
Click to expand...
Click to collapse
CM 9 ??????
Babloo1989 said:
CM 9 ??????
Click to expand...
Click to collapse
Installing ice cream sandwich will cause the internal sd card to be wiped
I don't think anyone is on cm9 because of that...