The only rom i have been able to get working somewhat right is CM 7.03 and
that just means it plays and sound is synced .the double layout seems to break
the links and descriptions of the movies on the main page.
So what rom are you suing for this?
Cm7 nightly 83 runs just fine. Just had to edit my build.prop file to say HTC vision instead of gtab.
Layout fix for descriptions/episode selection on CM7.0.3 can be found here:
http://forum.xda-developers.com/showthread.php?t=1113201
Thanks again to scubasteve85.
I used the version of the Neflix apk that has the device check disabled in CyanogenMod 7.0.3 without any changes to any files. It streamed just fine without any weird issues like the chipmunk effect some folks are reporting with using different apks.
Also, Robeet has posted a link to a hack he created to make it work in VEGAn 5.1.1 which you can find in the ROMs section in the VEGAn 5.1.1 thread. It works fine for me as well.
I have the original APK that was posted here awhile ago, and it's running fine w just the change to build.prop, on stock TNT.
Jim
sjmoreno said:
I used the version of the Neflix apk that has the device check disabled in CyanogenMod 7.0.3 without any changes to any files. It streamed just fine without any weird issues like the chipmunk effect some folks are reporting with using different apks.
Click to expand...
Click to collapse
On mine, it is working perfectly with CM 7.0.3.1 without modifying any files, just like above.
However, it didn't work well on CM Nightly (I think it was 83 or 87...I'm not near my gTablet right now)...I got the "chipmunk" effect (video was playing at twice the speed).
tkirton said:
On mine, it is working perfectly with CM 7.0.3.1 without modifying any files, just like above.
However, it didn't work well on CM Nightly (I think it was 83 or 87...I'm not near my gTablet right now)...I got the "chipmunk" effect (video was playing at twice the speed).
Click to expand...
Click to collapse
There is a fix for the chipmunk effect, you have to modify the build.prop file but it worked for me.
Good news, I've been able to get Netflix working on vegan-tab GE by using some of the libs from the latest CM 7 stable version. This evening, I will work on creating a flashable patch with those libs for anyone interested.
Sent from my HERO200 using XDA App
I'm having some issues creating an updater-script that actually works. I've never had to create on before, so if anyone has any experience with this please tell me where the errors are
Essentially, all I need to do is add to, and copy over, some files in system/lib/ and set permissions. I haven't started working on the permissions part because I can't even get the files to copy! The .zip runs with no errors, I just don't have any files actually copied.
Code:
mount("yaffs2", "MTD", "system", "/system");
ui_print("Updating libraries...");
package_extract_dir("system", "/system");
ui_print("Update complete");
unmount("/system");
Hope you get it figued out... I'm looking forward to it.
Please get it working vegan ginger is what im on and this is all its missing ,wishing u success in your en-devours !!!!
Can you elaborate on the libraries involved? I assume we could use Root Explorer to update them manually.
Sure, if you don't mind doing the legwork. The libs that I have replaced from CM 7.0.3 stable (sorry, can't post links yet) are:
libhwmediaplugin.so
libhwmediarecorder.so
libopencorehw.so
libstagefright.so
libstagefrighthw.so
libsurfaceflinger_client.so
libwebcore.so
omxplayer.so
Copy/replace as necessary. Don't forget to set permissions.
Enjoy Netflix!
-okthr- said:
Sure, if you don't mind doing the legwork. The libs that I have replaced from CM 7.0.3 stable (sorry, can't post links yet) are:
libhwmediaplugin.so
libhwmediarecorder.so
libopencorehw.so
libstagefright.so
libstagefrighthw.so
libsurfaceflinger_client.so
libwebcore.so
omxplayer.so
Copy/replace as necessary. Don't forget to set permissions.
Enjoy Netflix!
Click to expand...
Click to collapse
Which version of the netflix apk did you use? I transfered all of the libs and fixed permissions but when I run Netflix it says my device is unsupported.
Awesome. Works like a charm. You are the man. I was never a big fan of CM7 and love Vegan Ginger. Thanks.
-okthr- said:
Sure, if you don't mind doing the legwork. The libs that I have replaced from CM 7.0.3 stable (sorry, can't post links yet) are:
libhwmediaplugin.so
libhwmediarecorder.so
libopencorehw.so
libstagefright.so
libstagefrighthw.so
libsurfaceflinger_client.so
libwebcore.so
omxplayer.so
Copy/replace as necessary. Don't forget to set permissions.
Enjoy Netflix!
Click to expand...
Click to collapse
Thank you!! This worked flawlessly. This is what I've been waiting for on Vegan Ginger. For those having problems be sure to update your build.prop file to set the manufacturer to HTC and the model to HTC Vision
What version of Netflix are you using?
What version of Netflix are those of you who have this working on Vegan GE using? It's working for me on version 1.2.1, but the continuous prompting to update the app is a slight nuisance. Is anyone using 1.2.2 successfully with this fix of Vegan GE?
I've never gotten a prompt for device unsupported. Are you using the stock build.prop?
I'm using the latest Netflix apk. 1.2.2 I believe.
Sent from my HERO200 using XDA App
If you look in the apps section there is a link to the new Netflix version, thinks its 1.2.2.
Thanks a lot guys. I appreciate the help. Getting Netflix to work on Vegan GE (along with all its other niceties) makes this ROM pretty much perfect for my interests.
btw -okthr-, I posted a reply to the Vegan GE thread under the Development forum with a link to your post about the Netflix fix and your plea for help on creating an update script. Hopefully, some of the DEVs will take a look and offer some feedback on the script errors you were seeing. Thanks Again!!!
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
Apparently there's an app that does this in a much cleaner manner: HERE do not use the remaining instructions below.
Remainder of post for archive purposes only
This is a modified version of CM7 MOD - Chisleu's CM7 Mod
This thread contains links for CM7 nightly to update build.prop in the nightly releases, the file used for this is the build.prop from Chisleu's MOD, updated to match the current nightly build's build number. I did not actually make the build.prop, only pilfered it from Chisleu! I made this because I didn't want to modify my keymaps and wanted to run the latest nightly. If you want the modified keymaps go to the link above.
What this mod changes:
1. build.prop has fix for chipmunk audio in netflix app
THIS IS NOT CM7, ONLY A MOD! (one stolen from another dev at that!)
Instructions:
1. Install CM7
2. (optional) Install kernel of your choice
3. Flash the following using ROM Manager/CWM
4. Enjoy
I will do my best to keep these up to date each day until the next stable build.
Current: Nightly 101
Previous:
Reserved for future use
Much easier to just use this.
http://forum.xda-developers.com/showthread.php?p=14683956#post14683956
I don't mean to sound cynical, but is this really necessary? For those who can't or don't want to manually edit the one line in build.prop, there is already an app posted here on the forums that makes the edit. Since the app edits the existing build.prop, it should be compatible with all past and future nightlies.
Edit: I was referencing the app that Nburnes linked to.
Sent from my ThunderBolt using XDA App
Mistar Muffin said:
I don't mean to sound cynical, but is this really necessary? For those who can't or don't want to manually edit the one line in build.prop, there is already an app posted here on the forums that makes the edit. Since the app edits the existing build.prop, it should be compatible with all past and future nightlies.
Edit: I was referencing the app that Nburnes linked to.
Sent from my ThunderBolt using XDA App
Click to expand...
Click to collapse
Had been awhile since I had been on and hadn't seen that app myself, I'm going to have to agree, will edit the original and lock the thread based on said new (to me) info.
Hi,
I just flashed the new simply honey rc1 that eb just uploaded tonight & I seem to be missing polaris office and the sgs 2 apps. I thought I flashed the full version correctly but the kernel says its from june, is that a possible problem?
Well, I did install the polaris-office.apk that was in the thread but it pretty much just force closes.
Any help would be much appreciated!
disguy03 said:
Hi,
I just flashed the new simply honey rc1 that eb just uploaded tonight & I seem to be missing polaris office and the sgs 2 apps. I thought I flashed the full version correctly but the kernel says its from june, is that a possible problem?
Well, I did install the polaris-office.apk that was in the thread but it pretty much just force closes.
Any help would be much appreciated!
Click to expand...
Click to collapse
try reflash, if that doesnt work just extract the apps your want from system/app in the downloaded zip and install them on push them to system/app on the phone
and the kernel's from june because it still the JVP kernel, still works for JVR but there hasnt been a JVR kernel made but i think people are working on 1
edit: just downloaded 5.0rc1 and polaris office isnt in the zip, so he forgot it or chose not to put it in
View attachment PolarisOffice.apk thats from 4.0, should still work though
kyle51 said:
try reflash, if that doesnt work just extract the apps your want from system/app in the downloaded zip and install them on push them to system/app on the phone
and the kernel's from june because it still the JVP kernel, still works for JVR but there hasnt been a JVR kernel made but i think people are working on 1
edit: just downloaded 5.0rc1 and polaris office isnt in the zip, so he forgot it or chose not to put it in
View attachment 689395 thats from 4.0, should still work though
Click to expand...
Click to collapse
So I reflashed from recovery after doing a wipe and I still only have 2 pages of apps. Is there something I'm doing wrong? Well, I'll try to just install each of them manually, hopefully polaris works. Thanks again.
Has anybody been able to get polaris working on the RC1? I also took the apk from the 5.0 beta 3 and it still force closes. I also tried to fix permissions after install based on some suggestions on other threads. Any ideas?
Polaris also has a lib file. I'll be posting a small package that includes Polaris and a couple other apps I forgot. Probably by 930 eastern time.
Sent from my SGH-T959 using XDA Premium App
explodingboy70 said:
Polaris also has a lib file. I'll be posting a small package that includes Polaris and a couple other apps I forgot. Probably by 930 eastern time.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
You sir have made my day! Much appreciated!
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.
Okay there is plenty of Eleven Music app threads, Eleven Music app basically made by Cyanogenmod which is dramatically cool, fast and simple music app! I tried many version of Eleven on Android 7.1 based roms but ended up with failure so I though to share the apk with you guys which is working perfectly on 7.1 based roms for Moto G 2014, you may give a try to another devices, I dont own anything, I am just sharing the extracted apk Cause I asked may forums for the apk and didnt get the proper response and many stuffs, I dont want that you guys face the same lol Enjoy!
raisul2010.5396 said:
Okay there is plenty of Eleven Music app threads, Eleven Music app basically made by Cyanogenmod which is dramatically cool, fast and simple music app! I tried many version of Eleven on Android 7.1 based roms but ended up with failure so I though to share the apk with you guys which is working perfectly on 7.1 based roms for Moto G 2014, you may give a try to another devices, I dont own anything, I am just sharing the extracted apk Cause I asked may forums for the apk and didnt get the proper response and many stuffs, I dont want that you guys face the same lol Enjoy!
Click to expand...
Click to collapse
Downloaded the app, tried to install it and got "Error parsing package file".
I run AOSP 7.1.1 (not Moto G4).
Nonta72 said:
Downloaded the app, tried to install it and got "Error parsing package file".
I run AOSP 7.1.1 (not Moto G4).
Click to expand...
Click to collapse
There are some issues to run Eleven on AOSP based roms, idk why, but it worked perfectly on LOS14.1 based roms, but still as you are saying parsing related error, try re downloading and give a shot
raisul2010.5396 said:
There are some issues to run Eleven on AOSP based roms, idk why, but it worked perfectly on LOS14.1 based roms, but still as you are saying parsing related error, try re downloading and give a shot
Click to expand...
Click to collapse
I pushed it to system/app/Eleven
Rebooted, and it was in the App Drawer. But it would force close.
Logcat showed that it needed librsjni.so.
I copied that lib from LOS14.1 of my phone and it worked in AOSP 7.1.2 normally!
Thanks!!!
Nonta72 said:
I pushed it to system/app/Eleven
Rebooted, and it was in the App Drawer. But it would force close.
Logcat showed that it needed librsjni.so.
I copied that lib from LOS14.1 of my phone and it worked in AOSP 7.1.2 normally!
Thanks!!!
Click to expand...
Click to collapse
Woah, thats cool, thanks for the suggestion, I will make a flashable zip with that lib then!
Nonta72 said:
I pushed it to system/app/Eleven
Rebooted, and it was in the App Drawer. But it would force close.
Logcat showed that it needed librsjni.so.
I copied that lib from LOS14.1 of my phone and it worked in AOSP 7.1.2 normally!
Thanks!!!
Click to expand...
Click to collapse
can you share the librsjni.so you replaced? mine isnt working at all even after replacing
raisul2010.5396 said:
can you share the librsjni.so you replaced? mine isnt working at all even after replacing
Click to expand...
Click to collapse
I attached the whole package!
(Sorry for late reply)
(Solved)I've installed the app and pasted the libs to their directory... Now app is opening normally but it is not playing songs.... When i tap on a song to listen... Nothing happen on it... Please help
how does work lyrics in this app?
Same thing as anas sami, I'm pressing a song but nothing happens.
If it's not playing the song you have to go into the app. Settings and allow it. To modify system settings and enable. All permissions then restart the app
hey, guys, could you explain how you managed to make it work? I don't see any system/app folders on my device (Meizu 15Lite, 7th version). Even though this seems to work fine, I'd like to make it myself with the original package. Thanks.
ps.
found the folders with root, however still no idea how you've done it. copied 64 lib to lib64 and, just to be sure, the regular arm to lib folder on the system directory.