Related
*** This thread is now outdated ***
Please follow this link for a much better solution - Also, be sure to hit the Thanks! button to show your support for DizzyDen's excellent work!
********************************************************************************
I have removed all the files from this post and I encourage everyone to migrate to DizzyDen's superior solution. If for some reason you are unable to use Dizzy's tool you can PM DizzyDen or myself (Martian21) and one of us should be able to get you want you need.
********************************************************************************
[Original Thread]
I have seen several threads regarding this topic and thought I'd try to consolidate as much as I can in one place.
Credit for the original IMEI work goes to mthe0ry His original thread is here.
Because the NOOK Color is not a phone it does not have an IMEI number. This is why some apps that check for an IMEI number do not work on the NOOK.
Thanks to the work of mthe0ry and now DizzyDen it is possible to modify the framework.jar file in order to create a fake IMEI number on the NOOK Color. Doing so will allow programs such as Swype Beta, the free version of the XDA app, HBO GO, and the Xfinity app to work on the NOOK Color.
Unfortunately you need to have a framework.jar file that matches the ROM you are running as changes to the framework between ROMs can (and probably will) cause problems.
[See DizzyDen's thread for the IMEI generator tool]
*** This is mostly obsolete now that Dizzy's tool handles replacing the framework.jar file and backs up your original file - but I will leave it here just in case it is still useful to someone. ***
Installation:
You will need a file manager with Root access such as Root Explorer.
Download the framework.jar file for your Rom.
Unzip the file and transfer the framework.jar file to your NOOK Color.
Navigate to /System/framework using Root Explorer.
Mount the /System/framework folder R/W.
Rename the original framework.jar to framework.jar.bak.
Using Root Explorer, copy the new framwork.jar file.
Paste the modified framework.jar into /System/framework.
Long press the newly copied framework.jar and select "Permissions".
Change the permissions to match framework.jar.bak [rw-r--r--].
Mount the /System/framework folder R/O.
I recommend you reboot your NOOK although resetting the launcher may be enough.
For those that used my original files or the ones from mthe0ry, the original IMEI used in those files is "12-34567-89012-45". If you wish to continue using this IMEI number [NOT RECOMMENDED] you can manually enter it into Dizzy's tool.
Martian21
Request pls
I know that nightly 78 was the last nightly that runs on .29 kernel all the new nightlys 80,82,83 and 84 need uboot 1.2 and .32 kernel. I have read that some people have been experiencing problems on these builts. Also being that .32 kernel is still label beta i would like to ask you if you could please make a framework for nightly 78. I have attached the framework file from my nightly 78. Thank you
Finally was able to reboot after copying framework82. Was able to sign in but have yet to play a movie. I get stuck in the spinning circle.
Sent from my Vision using XDA Premium App
MACLUIS1 said:
Finally was able to reboot after copying framework82. Was able to sign in but have yet to play a movie. I get stuck in the spinning circle.
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
I did a total wipe, stock 1.2 install, then a second total wipe before n82. I then added the modded framework and HBO GO worked really well! But, after adding Dal's 5/13 OC, I then got the spinning circle problem you describe.
I tried re-flashing just n83 to fix it (without Dal's OC), and re-installing the modded framework, but the spinning circle problem remains.
I can't say for sure that the OC kernel broke it -- it could be one of a dozen apps I installed? -- but it's certainly the leading culprit in my case. The 5/13 OC kernel also appeared to break a few of my other apps as well (360 Live failed too, but started working again after I returned to vanilla n83).
I'm going to start the entire process over again tonight to try and narrow down the problem...
I have the 5/13 OC installed but HBO GO is now working on my Nook. Just need to uninstall and reinstall HBO GO. Worked like a charm for me.
Sent from my Vision using XDA Premium App
MACLUIS1 said:
I have the 5/13 OC installed but HBO GO is now working on my Nook. Just need to uninstall and reinstall HBO GO. Worked like a charm for me.
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
Didn't work for me -- still stuck on spinning circle after intro clip plays.
I used TiBu to wipe data, uninstall, then install app. Did you reboot in between, or take any other steps?
martian21 said:
I am using the same IMEI of "12-34567-89012-45" that mthe0ry used.
Click to expand...
Click to collapse
So every one gets the same IMEI?
We are going to fix this in CM soon. Please don't break every other program that uses IMEI to identify a UNIQUE device! I suggestion that no-one uses this. You are really playing with fire here.
nemith said:
So every one gets the same IMEI?
We are going to fix this in CM soon. Please don't break every other program that uses IMEI to identify a UNIQUE device! I suggestion that no-one uses this. You are really playing with fire here.
Click to expand...
Click to collapse
I do appreciate your warning (and, as always, all your hard work), but Dal came out and stated plainly that an IMEI solution would not get added to cm7 builds, so the rest of us took his word for it and had to solve the problem some other way.
Now, if you're saying that the solution WILL be built into one of the next few nightlies -- with unique IMEI's -- then that's fantastic!!
However, without it, there's currently no other way to run HBO GO, Swype, etc -- unless we compile our own framework.jar... which isn't an option for some of us noobs.
Has work already begun on a better solution?
paleh0rse said:
I do appreciate your warning (and, as always, all your hard work), but Dal came out and stated plainly that an IMEI solution would not get added to cm7 builds, so the rest of us took his word for it and had to solve the problem some other way.
Now, if you're saying that the solution WILL be built into one of the next few nightlies -- with unique IMEI's -- then that's fantastic!!
However, without it, there's currently no other way to run HBO GO, Swype, etc -- unless we compile our own framework.jar... which isn't an option for some of us noobs.
Has work already begun on a better solution?
Click to expand...
Click to collapse
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
dalingrin said:
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
Click to expand...
Click to collapse
You're a good man, thank you!
dalingrin said:
I meant the static IMEI hack as presented in this thread. This hack will not be added to CM7.
We are working on a real solution as we speak.
Click to expand...
Click to collapse
This is great news!!!
I will cease and desist as soon as it it completed. Obviously the best thing would be for people to follow mthe0ry's instructions and do this themselves (it's really not that hard) using their own unique IMEI number. That said I'm happy to continue the "hack" method for those who don't wish to do it themselves.
Yes, having multiple devices with the same IMEI could become problematic but so far it's worked for the apps people want. I do appreciate the warning as I probably wasn't as clear about the "hack" nature of this in the OP as I should have been.
Martian21
jzibit17 said:
I know that nightly 78 was the last nightly that runs on .29 kernel all the new nightlys 80,82,83 and 84 need uboot 1.2 and .32 kernel. I have read that some people have been experiencing problems on these builts. Also being that .32 kernel is still label beta i would like to ask you if you could please make a framework for nightly 78. I have attached the framework file from my nightly 78. Thank you
Click to expand...
Click to collapse
Attached:
enjoy
slide it
please disregard below. in reading the thread better I can see it's not for swype at all but for setting the nook up with an IMEI.
I don't mean to be rude, but why not just use slide-it? I'm cognisant of the simplicity of swype as I use it daily on my Galaxy S, but slide-it is nearly as good and works without fault on the nook (rooted stock and CM7) without any mods.
smiley1960 said:
please disregard below. in reading the thread better I can see it's not for swype at all but for setting the nook up with an IMEI.
I don't mean to be rude, but why not just use slide-it? I'm cognisant of the simplicity of swype as I use it daily on my Galaxy S, but slide-it is nearly as good and works without fault on the nook (rooted stock and CM7) without any mods.
Click to expand...
Click to collapse
Many of us use this hack for HBO GO, not just Swype...
First zip file is for which Rom?
Sent from my NookColor using Tapatalk
RASTAVIPER said:
First zip file is for which Rom?
Click to expand...
Click to collapse
Opps - Typo. It is for CM7 Stable 7.03
I added a note to the first post. I'll try to fix the file name when I get home tonight. I'm sure there will be 1 or two more nightly builds as well.
paleh0rse said:
Many of us use this hack for HBO GO, not just Swype...
Click to expand...
Click to collapse
It's also needed for a number of Gameloft titles.
Rodney
Concerns about unique devices make me wonder... I have a broken HTC Kaiser sitting on a shelf above my desk. It will never again be a functional device, but yet it has it's own unique IMEI.
Does the IMEI alone tell apps anything about what sort of device belongs to the number? If not, then it seems that I could use the IMEI from that Kaiser or the broken G1 I have.
It doesn't seem like these apps know anything about the device from the IMEI alone, given that people have been implementing this fix with no repercussions. That means apps probably don't check any hypothetical IMEI-device info against what's recorded in the build.prop, so this seems like a safe, workable solution for those of us with defective devices on our shelves.
Is there a way to make this work on a ManualNootered nook with 1.2, or does it only work if you have a custom rom.
Thanks
integrate in CM7
could you not ask the maintainers of CyanogenMod to integrate this in the future nightlies?
they would probably welcome the added functionality
I haven been looking all over but I can't seem to find an answer: youtube app always fc on me on the miui room. I have tried many apks but non work. The app just doesn't open. I can't find youtube in the market, I can however find it on the web market but cannot overall since I have no compatible device...
although it its installed on my desire, galaxy tab and archos tab
But no way to get it working on my sgs II.
Anybody an idea?
Swyped from another Galaxy, in the Miui dimension
MisterSosa said:
I haven been looking all over but I can't seem to find an answer: youtube app always fc on me on the miui room. I have tried many apks but non work. The app just doesn't open. I can't find youtube in the market, I can however find it on the web market but cannot overall since I have no compatible device...
although it its installed on my desire, galaxy tab and archos tab
But no way to get it working on my sgs II.
Anybody an idea?
Swyped from another Galaxy, in the Miui dimension
Click to expand...
Click to collapse
Did you search the miui ROM thread? And have you asked in there?
That would be the best (and correct) place to start.
Well it is a release thread, so I prefer to keep that one clean. Therefore I chose the QnA. I have searched there but there are only reports about green videos not about the app itself.
Swyped from another Galaxy, in the Miui dimension
MisterSosa said:
Well it is a release thread, so I prefer to keep that one clean. Therefore I chose the QnA.
Click to expand...
Click to collapse
You may get an answer in here, but that thread is the correct place to ask. As per forum rules you shouldn't start a new thread to ask questions relating to another thread. You're not supposed to start development threads unless you're releasing, but discussion in them is correct.
Anyway, have you tried taking the youtube app off your Galaxy Tab? That should work with it, unless there's something incompatible with the miui ROM, in which case you're back to the ROM thread again.
I suppose one of your other devices is rooted?
On the rooted device go to /data/app and copy com.google.androi.youtube-2.apk to your pc. You can do this with either root explorer or a similar app, or with adb.
Then copy it to the internal storage of your galaxy s 2 and place it in /data/app and overwrite everything, use root explorer, or similar, and remember to activate r/w. You can also use adb push for this.
Please tell me if this works. Otherwise I would recommend, as always, backup, not youtube ofcourse , wipe everything and install again.
Oh, and don't mind the thread, as you can see it already is a horrible mess over there...
Use the MIUI backup, wipe everything, redownload (could be a bad download) and reflash MIUI, check market for youtube, if it isn't there tell me and I'll grab the youtube apk from my phone running MIUI.
Thanks for the help guys I will give it a try this evening and will report back with the result
EDIT: will be for this evening, couldn't find the time yesterday
Swyped from another Galaxy, in the Miui dimension
The full wipe didn't work nor did the root explorer way. Keep getting FC's. Had this problem on miui for the desire as well...
Could this be country specific my mate had the same problem on his desire with miui...
Only thing left to try is seshmaru's way
Swyped from another Galaxy, in the Miui dimension
Anyone willing to pull a working youtube apk from their miui rom?
Swyped from another Galaxy, in the Miui dimension
MisterSosa said:
Anyone willing to pull a working youtube apk from their miui rom?
Swyped from another Galaxy, in the Miui dimension
Click to expand...
Click to collapse
Unzip youtube.7z to /data/app, give it the correct permissions and reboot the phone.
Cheers
Try and use galnetmiui. YouTube will work with galnetmiui. No offence to the other miui's but they ain't no where near as good and stable as galnet's
Sent from my GT-I9100 using Tapatalk
Big thanks geert! Worked like a charm!
Swyped from another Galaxy, in the Miui dimension
MisterSosa said:
Big thanks geert! Worked like a charm!
Swyped from another Galaxy, in the Miui dimension
Click to expand...
Click to collapse
Here you have version 2.2.16
thank you
geertmeersman said:
Unzip youtube.7z to /data/app, give it the correct permissions and reboot the phone.
Cheers
Click to expand...
Click to collapse
Thank you for the idea helped me very
I am the proud owner of a SGS3
But I'm not the biggest fan of touchwiz and I love everything about 4.2!
So like many others, I flash a 4.2 custom ROM. AOKP 4.2 build 2, to be exact.
After flashing, I loved it. Everything about it was just perfect. It was fast, light, easy to use, and FAST! But then I go to take a picture. And boom.
"Can't Connect to Camera"
I had no idea what to do, so I did the first thing that comes to mind. reboot. But sadly, this solved nothing. So of course I re-flash my touchwiz ROM to see if the ROM was the problem. And the Touchwiz camera worked perfectly. Later on when I had time, I tested it out again, and had the same problem. So I downloaded a camera app, and same thing. I even flashed a different Camera.zip for God's sake! I've searched for the past week for fixes and every one I tried just failed! So now I'm really done with Touchwiz and want to customize the look and feel of my phone (which is one of the reasons I like AOKP!)
It seems that my camera only works on Touchwiz ROMs! :crying:
I also tried another ROM this time running 4.1.2 thinking maybe it was just a bug in 4.2! But sadly, the same error message.
I am open to ANY ideas right now and would be very thankful for some replys.
I NEED TO GET OFF OF TOUCHWIZ AND BACK TO 4.2!
Thank you as always!
EDIT: So I think I figured out the problem. I was flashing a 4.2 camera .zip file and i guess it was messing up the permissions. So I disabled it. Now it is working perfectly so far. Yesterday i switched over to a 4.1.2 ROM hoping it would fix it and so then i flashed this 4.2 camera and then after about a day of use, it messed up the permissions.
So to fix it if anyone is have that problem, disable the camera app you flashed, reboot into recovery, ADVANCED - FIX PERMISSIONS
all done.
joshuagalipeau said:
I am the proud owner of a SGS3
But I'm not the biggest fan of touchwiz and I love everything about 4.2!
So like many others, I flash a 4.2 custom ROM. AOKP 4.2 build 2, to be exact.
After flashing, I loved it. Everything about it was just perfect. It was fast, light, easy to use, and FAST! But then I go to take a picture. And boom.
"Can't Connect to Camera"
I had no idea what to do, so I did the first thing that comes to mind. reboot. But sadly, this solved nothing. So of course I re-flash my touchwiz ROM to see if the ROM was the problem. And the Touchwiz camera worked perfectly. Later on when I had time, I tested it out again, and had the same problem. So I downloaded a camera app, and same thing. I even flashed a different Camera.zip for God's sake! I've searched for the past week for fixes and every one I tried just failed! So now I'm really done with Touchwiz and want to customize the look and feel of my phone (which is one of the reasons I like AOKP!)
It seems that my camera only works on Touchwiz ROMs! :crying:
I also tried another ROM this time running 4.1.2 thinking maybe it was just a bug in 4.2! But sadly, the same error message.
I am open to ANY ideas right now and would be very thankful for some replys.
I NEED TO GET OFF OF TOUCHWIZ AND BACK TO 4.2!
Thank you as always!
EDIT: So I think I figured out the problem. I was flashing a 4.2 camera .zip file and i guess it was messing up the permissions. So I disabled it. Now it is working perfectly so far. Yesterday i switched over to a 4.1.2 ROM hoping it would fix it and so then i flashed this 4.2 camera and then after about a day of use, it messed up the permissions.
So to fix it if anyone is have that problem, disable the camera app you flashed, reboot into recovery, ADVANCED - FIX PERMISSIONS
all done.
Click to expand...
Click to collapse
Hi this solution seems preety interesting i'll try it and come back with some results. Thanks man
Edy0706 said:
Hi this solution seems preety interesting i'll try it and come back with some results. Thanks man
Click to expand...
Click to collapse
Not a problem, happy to help!
joshuagalipeau said:
Not a problem, happy to help!
Click to expand...
Click to collapse
Could you please clarify for me what does it means: "disable the camera app " ?
Thanks
andr0077 said:
Could you please clarify for me what does it means: "disable the camera app " ?
Thanks
Click to expand...
Click to collapse
download Titanium Backup, go to the gallery apk, back it up then uninstall
joshuagalipeau said:
download Titanium Backup, go to the gallery apk, back it up then uninstall
Click to expand...
Click to collapse
If I uninstall gallery apk which is including camera aaplication, how I will make a shoot ?
hye
actually,what application did you dissable?from the touchwiz or the custom rom? :laugh:
well, it works for me, thanks a lot dude.
This is a file permissions problem, between the camera and the gallery apps. It is fixable, I had the ability to force a 'fix permissions on boot' in init.d, but are various ways to do it.
kaibosh99 said:
This is a file permissions problem, between the camera and the gallery apps. It is fixable, I had the ability to force a 'fix permissions on boot' in init.d, but are various ways to do it.
Click to expand...
Click to collapse
how?
andr0077 said:
If I uninstall gallery apk which is including camera aaplication, how I will make a shoot ?
Click to expand...
Click to collapse
Same question
Hey guys, my question is essentially what the title says. I find that in CM10 based roms, that whenever I use the stock cyanogen mod browser, it automatically goes into desktop mode (and is stuck there. The desktop mode checkbox, however, is unchecked.) I'm fairly sure it worked before I used the touch pad fix here - http://forum.xda-developers.com/showthread.php?t=1893343 - So I think it might be a framework/build.prop issue, but I'm not sure. I've been looking to fix this problem everywhere but haven't really been able to find a solution. Do you guys have any idea what the fix might be?
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
smokerman said:
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
Click to expand...
Click to collapse
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
fishvtt said:
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
Click to expand...
Click to collapse
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Hey, smokerman, would you know how to mess with .jar files. I kinda want to go exploring to see if I can do anything.
you have here a simple guide by @CriGiu
http://forum.xda-developers.com/showthread.php?t=2322231
could help you.:good:
fishvtt said:
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
Click to expand...
Click to collapse
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
Oh ok, I'll try testing that out.
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
All right, well that seems to do the trick. When I try to use the touchpad activator app, it gives me the "error 5 expected reciever of type android.view.ViewRoot, but got android.view.ViewRootImpl". But, Dead Trigger works perfectly how it's supposed to, and the stock browser is using the mobile version now. Just remember to make the necessary build.prop changes as outlined in Fahrenheit's guide.
Hello everyone,
I'm new on the forum, i just started using my i9100 with custom ROMs, i tried CM10 once but i didn't like it so i went back to stock JB.
Now when i saw that KitKat was available i just said "why don't i give it a try", so i installed omniROM 4.4.2. So far so good, but what i really miss from the stock samsung ROM is the peak/off-peak schedule for default email application.
I use my corporate email account with the default email app (company policy), but in omniROM there is no schedule option like in the latest stock rom for my phone.
So i thought, well lets look for another stock rom for a samsung phone that has 4.4.2 and take the Email.apk and move it to mine. So i downloaded the stock S4 ROM 4.4.2 and i see that there is no Email.apk but SecEmail.apk, i tried to use that file but it doesn't work (copied on recovery mode), i know that i'm doing it right because i tried before with other versions trying to fix that exchange "cannot connect" bug of kitkat.
So my question is this: is there a way to get "peak/off-peak schedule" feature? where i can get the Email.apk that will do that? or what is different with that secEmail.apk that it doesn't work?
Thanks, and sorry if someone asked this before, i searched everywere but didn't find an answer, i don't know why people doesn't ask "where that feature go? or how can i get it back in non stock roms", i find it one of the most useful features, in fact the first time i went back to stock from CM10, that was the reason why.
fedehrv said:
Hello everyone,
I'm new on the forum, i just started using my i9100 with custom ROMs, i tried CM10 once but i didn't like it so i went back to stock JB.
Now when i saw that KitKat was available i just said "why don't i give it a try", so i installed omniROM 4.4.2. So far so good, but what i really miss from the stock samsung ROM is the peak/off-peak schedule for default email application.
I use my corporate email account with the default email app (company policy), but in omniROM there is no schedule option like in the latest stock rom for my phone.
So i thought, well lets look for another stock rom for a samsung phone that has 4.4.2 and take the Email.apk and move it to mine. So i downloaded the stock S4 ROM 4.4.2 and i see that there is no Email.apk but SecEmail.apk, i tried to use that file but it doesn't work (copied on recovery mode), i know that i'm doing it right because i tried before with other versions trying to fix that exchange "cannot connect" bug of kitkat.
So my question is this: is there a way to get "peak/off-peak schedule" feature? where i can get the Email.apk that will do that? or what is different with that secEmail.apk that it doesn't work?
Thanks, and sorry if someone asked this before, i searched everywere but didn't find an answer, i don't know why people doesn't ask "where that feature go? or how can i get it back in non stock roms", i find it one of the most useful features, in fact the first time i went back to stock from CM10, that was the reason why.
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...om-revolution-rom-ux-2014-build-1-12-t2607749 you can get it from here
bhavstech said:
http://forum.xda-developers.com/gal...om-revolution-rom-ux-2014-build-1-12-t2607749 you can get it from here
Click to expand...
Click to collapse
Is that a kitkat rom? looks like JB
fedehrv said:
Is that a kitkat rom? looks like JB
Click to expand...
Click to collapse
yeah its jb rom there is a link for the stock email app in it ,will work kitkat roms!dont use the rom use app
bhavstech said:
yeah its jb rom there is a link for the stock email app in it ,will work kitkat roms!dont use the rom use app
Click to expand...
Click to collapse
I tried this (installed via CWM on CM11), no luck.I found SecEmail.apk and SecExchange.apk in /system/app but Email do not appear in app tray. Should I remove standard CM Email.apk and Exchange2.apk ?
janumix said:
I tried this (installed via CWM on CM11), no luck.I found SecEmail.apk and SecExchange.apk in /system/app but Email do not appear in app tray. Should I remove standard CM Email.apk and Exchange2.apk ?
Click to expand...
Click to collapse
y#eah thre are many apps on playstore for email try them
^+1....the above is good advice, there are loads of email apps on playstore......
But as for installing the stock email app on a CM rom.....it ain't ever gonna work.......
This is because the stock email app is a 'system' app, and sysrem apps need the touchwiz framework to function. This framework is (obviously) excluded from CM roms........
My wife says I'm a phone geek....She's probably right
keithross39 said:
^+1....the above is good advice, there are loads of email apps on playstore......
But as for installing the stock email app on a CM rom.....it ain't ever gonna work.......
This is because the stock email app is a 'system' app, and sysrem apps need the touchwiz framework to function. This framework is (obviously) excluded from CM roms........
My wife says I'm a phone geek....She's probably right
Click to expand...
Click to collapse
Indeed but not so many that correctly works in corporate environment (M$ Exchange). In fact Samsung did quite good job extending his Email.apk with some features that others miss like:
- S/MIME support
- setup of Exchange auto responder (server side)
- folders browser
etc.
BTW can you advice one with such features ?
@bhavstech
so, your first answer gave me point worth to check ...
janumix said:
Indeed but not so many that correctly works in corporate environment (M$ Exchange). In fact Samsung did quite good job extending his Email.apk with some features that others miss like:
- S/MIME support
- setup of Exchange auto responder (server side)
- folders browser
etc.
BTW can you advice one with such features ?
@bhavstech
so, your first answer gave me point worth to check ...
Click to expand...
Click to collapse
actuaaly idk wy i told you to do that actually i was a noob at that time stock appk dont work on cm you need to be on stock rom for that, i dont mail much i dont know about email apps on playstore.