Anyone tried the package metioned in this post http://www.xda-developers.com/android/core-android-4-2-apps-and-gapps-on-any-jelly-bean-device/?
Flashing the mentioned package that includes system apps, gapps, services and libraries causes any trouble?
Persechini said:
Anyone tried the package metioned in this post http://www.xda-developers.com/android/core-android-4-2-apps-and-gapps-on-any-jelly-bean-device/?
Flashing the mentioned package that includes system apps, gapps, services and libraries causes any trouble?
Click to expand...
Click to collapse
If by 'trouble' you mean 'it does not work' then the answer is 'yes it will cause trouble'. Some apps work, some work only in part, others won't work at all. I've tried the keyboard, that works. The related dictionary manager does not, it wants to have a higher API level (#16 = JB4.2). This means you can only use the predictive gesture typing feature in English since that is the only dictionary the thing comes with. There might be other ways of installing missing dictionaries (and no, these are not the standard dictionaries as they also contain information about word sequence frequencies etc) it might be possible to start gesturing in Swahili, who knows? The clock/alarm/timer works as long as you don't use the timer. Once you've used the timer the alarms won't go off anymore - this seems to be a genuine bug in the app. The camera works, but photosphere does not because the Defy does not have a gyroscope.
In other words, don't flash the whole zip. Pick it apart, and try only those bits you're interested in. Look at logcat for any missing libraries or API level mismatches. If you get something working, tell us. If it does not work, tell us as well.
Thanks, guess I'll go with only the few that make a difference. I can swipe in portuguese with the first leaked keyboard, but I already had the dictionary installed
Persechini said:
Thanks, guess I'll go with only the few that make a difference. I can swipe in portuguese with the first leaked keyboard, but I already had the dictionary installed
Click to expand...
Click to collapse
Where did you get the dictionary?
I can't swipe in portuguese...
Related
https://opensource.motorola.com/sf/projects/flipout
particular
https://opensource.motorola.com/sf/sfmain/do/go/rel1490?returnUrlKey=1294483663414
Wow! Cool!
It seems the china release is the latest. (That's what you link to). What I'd really like to fix is the x-y-z axis mapping of the accelerometer. So many apps don't work....
How do we use the files? Is it easy to pack roms, create Update.zip files, or just copy them to the right place?
ghostwheel said:
Wow! Cool!
It seems the china release is the latest. (That's what you link to). What I'd really like to fix is the x-y-z axis mapping of the accelerometer. So many apps don't work....
How do we use the files? Is it easy to pack roms, create Update.zip files, or just copy them to the right place?
Click to expand...
Click to collapse
Full ack with the accelerometer. But I fear it's not possible to install a custom rom without signing it with the Motorola key (at least that's what I heard).
/edit: After reading this, and this, its clear that the problem lies with Android 2.1: "FLIPOUT runs Android 2.1, or API level 7. The Display.getRotation() method is available as of Android 2.2, or API level 8. To handle this, you can detect the API version and on version 7 or below, use Display.getOrientation(), like this."
Nobody will use the workaround, so we will be stuck with a broken orientation sensor until (and only if) 2.2 is released for the Flipout.
zerghase said:
/edit: After reading this, and this, its clear that the problem lies with Android 2.1: "FLIPOUT runs Android 2.1, or API level 7. The Display.getRotation() method is available as of Android 2.2, or API level 8. To handle this, you can detect the API version and on version 7 or below, use Display.getOrientation(), like this."
Nobody will use the workaround, so we will be stuck with a broken orientation sensor until (and only if) 2.2 is released for the Flipout.
Click to expand...
Click to collapse
Interesting.
But I don't think this is the problem with the Flipout. Many apps actually adjust for screen orientation. Just the wrong way. No matter which way you hold the screen, orientation is off (e.g. Layar, wikitude).
And, the problem is old. It was around before 2.2 came out, or maybe when 2.2 was very young. So, I think most apps weren't written for 2.2 at that stage.
But to a question:
To produce a custom firmware we need to be able to sign stuff. (How was this found for droid?). But with root, we can overwrite anything on the phone, probably except for the init.rd, where the kernel is stored. Is that true? Could we patch by overwriting some files in, for example, /system/lib ?
Yes, with root you can change everything in the running system, but I don't know how far the kernel is protected. It could be possible that the kernel is signed and the system refuses to boot if it has been altered (but you should ask that a Motorola-pro, I'm new to that).
I think it's easier to modify the apps themselves. When they're open-source just apply the fix and recompile, if not...
maybe the developers will be grateful for some hints on bugs in their apps (I would be). And if they are not, it still appears easier to make a change to the bytecode of the erroneous apps than hacking something into the system to make some apps work (and maybe breaking others...).
If I have time, I'll read into the dalvik system and play around a bit with some apps.
Good morning all!
I've tried to search both on this forum and on google in general, but I'm having trouble finding a good answare to my question.
I recently changed from a SD ROM to Pongsters great NAND build. Had to use DFT, due to problems with the CWM. I'm now on Gingerbread - excellent!
Unfortunately I live in this weird country called Norway and we use an alphabet with three more letters (Æ, Ø and Å). Is there anyway I could get these three letters into my gingerbread keyboard, any language pack?
I found this link by searching, but I'm not sure how to install it. It seems like i need CWM.
My temporary solution was to download a 2.3 modification of the "Scandinavian keyboard". It works, but I'm loosing the famous gingerbread keyboard.
A dictionary would too, almost be overkill, awesome.
All help would be greatly appreciated.
Hi mate, maybe this package can help you:
http://forum.xda-developers.com/showthread.php?t=875202
the above is an add on keyboard, you will need to switch to it through keyboard selection.
Otherwise you can push the content of your CMW zip with adb (i suggest to pull the original files before).
adb remount
(optional, gets the original file from your phone) adb pull /system/app/LatinIME.apk "local Location" (ex. c: or /home/user/desktop)
adb push "replacement APK file location" /system/app/
(optional, gets the original file from your phone) adb pull /system/lib/libjni_latinime.so "HDD Location" (ex. c: or /home/user/desktop)
adb push "replacement lib file location" /system/lib/
then reboot and you will use the new KB.
Cheers.
The keyboard looks nice, but as far as I can see there are no Norwegian (NO) alternate.
Anyhow, the ADB-way seems interesting. Never tried, or even heard, about ADB before, but that's why we have tutorials and forums, right?
Downloading the SDK at this very moment.
bluescan said:
The keyboard looks nice, but as far as I can see there are no Norwegian (NO) alternate.
Anyhow, the ADB-way seems interesting. Never tried, or even heard, about ADB before, but that's why we have tutorials and forums, right?
Downloading the SDK at this very moment.
Click to expand...
Click to collapse
Once you go ADB you won't back.
It's not that difficult, if you have some nerd past it will be very easy, otherwise it's plenty of tutorials, just follow them and you won't do it wrong.
Just a small hint,
with CWM always backup before.
w/out CWM always titanum backup.
Cheers.
Maybe a long shot, but have u tried SwiftKey? It supports the Norwegian language, u can set it to two language packages so it shows suggestions in both languages and no need to switch anymore.
I use it German/English and it is IMO just awesome. In particular after a few days using it it is predicting almost whole sentences by it's own.
Just a suggestion without messing with pushing commands ect. ;-)
Sent from my Nexus One using Tapatalk
My tablet was runnin dexter mod 1.4 with all the patches, buy always had problems with the sd card and the usb thumb and I also had problems running some applications. Right now my A7 is running [mod] update04-19 patched market + google apps and my tablet is working almost perfect. I think this mod is better that dexter mode.
I hope everybody use this mode in their tablets.
Thanks Bestialbub for your great job.
i jus got my elocity a7
i tried to mod mine with the dexter mod 1.41 and mines wont work,
1st- i download the file didn't unzip it then i sent it to the SD card and rename it "update.zip".
2nd- i did the factory wipe/reset then i select to wipe all data
3rd- i select update.zip but i notice an message saying( E. can't read from SD card). i dont know if that is apart of the mod or what.
4th- when it is finish then i select reboot option and when it is done rebooting i get nothing new. can you help me out are do you know something that i might be doing wrong. i also did do the 1.42 patch aswell didn't work. are is there another mod that you can tell me how to get it.
hasn't been tested for application on dexter's rom, though i don't know of reason they shouldn't work. gapps can be flakey like that; actually, the files are all stock as they come from cyanogen, minus my patched market, which doesn't have any reason not to work on dexter's rom and has nothing to to with the installation of the rest of google applications, including the calendar and text messaging services; i introduced no signature issues else it wouldn't install on stock firmware.
what i can suggest, is that if you're doing this under wiped conditions; is that you need to do a "factory reset" in recovery AFTER applying my gapps update.
if you don't do the factory reset, there will be settings put in place by the provision.apk in dexter's rom (not sure if this has changed in 1.42) that may conflict with the setup of google-apps. it didn't w/ the gapps in v1 i ported from dexters rom in previous tests, but i was going for a vanilla install w/out mixed signatures/versions/dates. provision.apk is generally suggested to be removed when google-apps is intended to be installed, and it is by my installer, but not the changes done in the data folders, which is why the wipe is suggested. i think its role is replaced by the googlepartnersetup.apk, but i could be wrong.
theres also some build prop differences; some unnecessary (gsm provider info), some improved (fingerprint for added apps in addition to patched market and added permissions), and the same ones necessary for apps like skype to run.
sorry if that was too much info. i do that.
EDIT: i reviewed my original post, its step *2B*. i did update it to underline it, and provide explanation for its probable necessity.
bestialbub said:
provision.apk is generally suggested to be removed when google-apps is intended to be installed, and it is by my installer, but not the changes done in the data folders, which is why the wipe is suggested. i think its role is replaced by the googlepartnersetup.apk, but i could be wrong.
Click to expand...
Click to collapse
SetupWizard.apk replaces "provision.apk".
bestialbub said:
theres also some build prop differences; some unnecessary (gsm provider info), some improved (fingerprint for added apps in addition to patched market and added permissions), and the same ones necessary for apps like skype to run.
Click to expand...
Click to collapse
Audio fix, which enhances EQUlizer and probably a 10% audio increase, and rotation support for games is another one..
the gsm props were actually very much needed, as Google for a period enabled provider checking, so if no gsm provider was there, you could not activate a google account, so instead of ppl getting lost without MarketEnabler on a clean device, i included it for safety reasons so next time, we're prepared for such checks.. so it all serves a purpose, if you like to know more, XDA has excellent information on those topics.
SetupWizard.apk replaces "provision.apk".
Click to expand...
Click to collapse
thanks for the tip. i did concede i could be wrong, and you're right, i could find that small detail that setupwizard is known to replace functions for provision.apk. the same posts i'm finding on xda and cyanogenmod don't say anything about googlepartnersetup, however, yet its provided with gapps packages..
i also learn from demonstrated and practiced examples..
demonstrated examples i learned from, including your 1.2 rom shows your remove provision.apk and provide googlepartnersetup.apk, then reverse the decision in 1.4, i ASSUME based on signiture issues you had stated (i generally don't have those as i know i can re-use existing containers without having signature issues).
i also learned/ported from various sdk's, including google's sdk for gapp imports, and neither is required, but what is provided is sdksetup.apk.. me seeing a relation from sdksetup for an sdk/emu android device kinda indicates one might want googlepartnersetup as a counterpart on a physical device. (your 1.4 example does prove that doesn't have to be true).. but the google sdk shows that i don't need setupwizard.apk for google services either.
thought i'd relate, since most the general posted information i've seen on xda and cyanogenmod seem like vague gueses at best. though i suspect the people posting this information aren't necessarily the devs working closely with the files. just hobbists and modders making educated guesses like me.
Audio fix, which enhances EQUlizer and probably a 10% audio increase, and rotation support for games is another one..
the gsm props were actually very much needed, as Google for a period enabled provider checking, so if no gsm provider was there, you could not activate a google account, so instead of ppl getting lost without MarketEnabler on a clean device, i included it for safety reasons so next time, we're prepared for such checks.. so it all serves a purpose, if you like to know more, XDA has excellent information on those topics.
Click to expand...
Click to collapse
i was refering to MY gsm provided build prop information, i wasn't ragging on your build prop or rom addons. i followed suit to the gtab tnt modrom and added DIFFERENT gsm provider information than yourself (service provider id, not google client information). but it made no difference in gapps present demonstrated performance as this information DOES NOT (the stuff i provided/borrowed from tntlite) get passed into the android system or database files, as no service provider id is listed when opening marketaccess.apk, as it does on a phone device that does genuinely have this information.
i do concede to the thread discussion, tho, DEXTERS ROM IS THE BEST AND ONLY FULL ROM MOD FOR THE A7 TABLET!!!
my gapps mod is only intended to provide google applications ommitted by the manufacture. nothing more.
thanks for the indirect market patching instructions!
thanks am going to retry and see what happends
bestialbub said:
but it made no difference in gapps present demonstrated performance as this information DOES NOT (the stuff i provided/borrowed from tntlite) get passed into the android system or database files, as no service provider id is listed when opening marketaccess.apk, as it does on a phone device that does genuinely have this information.
Click to expand...
Click to collapse
Had the same issues, so i found the trick to be adding it in the boot.img using the default.prop, and it is added during bootup.. but now we're OT! so let's leave it at that.
a7 installation problem
these are the exat message i got (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
these are the exat message i got was (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
why post the same thing every 10 minutes?
.............................
demamalu said:
My tablet was runnin dexter mod 1.4 with all the patches, buy always had problems with the sd card and the usb thumb and I also had problems running some applications. Right now my A7 is running [mod] update04-19 patched market + google apps and my tablet is working almost perfect. I think this mod is better that dexter mode.
I hope everybody use this mode in their tablets.
Thanks Bestialbub for your great job.
Click to expand...
Click to collapse
That is not a mod it's the factory firmware with a patch to get market, I don't see in what way it is better than Dexter mod.
kevinppk said:
these are the exat message i got was (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
Click to expand...
Click to collapse
When this happen I remove the .zip from file name or just rename the file but most time removing. .zip does the job...
This giude was made as i found a method to enable google assistant in your phone..
Requirements:-
A phone with custom recovery
Three files provided below
Android 7.0 or higher (as for now)
All google apps must be either force closed or uninstalled before flashing the files
For this,you have to download the 3 files from this MOD EDIT: REMOVED.
->After downloading puth these files in your phones storage.
->Then,Reboot into recovery..
-> In recovery mode you will not be able to see the third file(tweak.prop)
First,flash GoogleAssistantVelvet.zip
Then,flash GoogleAssistantBuildProp
->After installing Wipe Cache
You Are done..Enjoy The new Google Assistant in your phone,,
F.A.Q
Supported languages by Assistant?
-> English and German as for now.
Will I get OTA Updates?
->Nope,As phones build.prop will be changed to PIXEl
Will it work on Marshmallow??
->i dont know,But i found this thread..You can try and tell me.. Visit this thread.
Working Devices
Almost all Phones.. Tested on Arm64(Redmi Note 3) Arm(Moto X2) x86(zenfone2)..All working fine..
Good Luck:highfive:
Tell Me if i helped...
Who created these files, where are they from? Are these for 32bit or 64bit? I am not sure I would call this a guide. How about some additional information, like what device you have a working version running on. Also, brief as it may have been, upon a little looking around it would appear there is not a one-size-fits-all solution as different devices require different parts of certain apk's. Have you resolved this?
Are all functions of assistant working?
Is OK Google working?
Not tryingto come off harsh, but this seems off somehow. Maybe I shouldn't have looked at your "How to build a custom ROM beginners guide", not exactly building a ROM, more like a coloring book, everything is already there you just slip a picture into the back and now it's 'Your Custom coloring book".
StevetotheH said:
Who created these files, where are they from? Are these for 32bit or 64bit? I am not sure I would call this a guide. How about some additional information, like what device you have a working version running on. Also, brief as it may have been, upon a little looking around it would appear there is not a one-size-fits-all solution as different devices require different parts of certain apk's. Have you resolved this?
Are all functions of assistant working?
Is OK Google working?
Not tryingto come off harsh, but this seems off somehow. Maybe I shouldn't have looked at your "How to build a custom ROM beginners guide", not exactly building a ROM, more like a coloring book, everything is already there you just slip a picture into the back and now it's 'Your Custom coloring book".
Click to expand...
Click to collapse
yeah sure,iwill
Thread closed as this is a copy of this guide: http://forum.xda-developers.com/showpost.php?p=69074667&postcount=112"
The Flash
Forum Moderator
I have a rooted Nook Simple Touch running the 1.2.1 firmware since ~2015 and it has been a while since I had not need to use the internet/wifi and because of that I missed all the news about the firmware update to support the secure TLS stuff.
Today, I tried to install additional dictionaries from the settings menu, but it stays at "connecting" forever and I think it is because of the outdated firmware.
I read the post on this forum and noticed that the update method doesn't work for rooted devices and the only alternative is to restore a stock image, update the firmware and then root it again. (https://forum.xda-developers.com/nook-touch/general/nst-nstg-fw-1-2-2-update-t3785566)
But, since I don't remember how I rooted it and the other customization I did, I think I'll probably miss something and then it is not worth doing it.
Then, I wanted to ask if someone has the stock files for the dictionaries to share (preferably the German and Spanish ones), and if just copying them to `/system/media/reference` will be enough to make the Nook think they were installed or would I need to do something else?
Similar to this thread (https://forum.xda-developers.com/nook-touch/general/nst-reader-stock-dictionary-oxford-gb-t3942496)
ETA:
If you have a NST with 1.2.2 firmware (the newest one (2018) that can access the internet) , can you check if Settings > Reader > Dictionaries is available and if you can download the other dictionaries.
And If it is not too much trouble, can you download them and then extract the files and upload them.
Thank you.
renatogoes said:
Today, I tried to install additional dictionaries from the settings menu, but it stays at "connecting" forever and I think it is because of the outdated firmware.
Click to expand...
Click to collapse
Wait, how does that work?! I've never seen that option in Settings. Are we really talking about the NST? I know the Glowlight model (as opposed to the NST Glowlight) has the option to download other dictionaries, but I don't think the NST versions of the hardware ever did.
nmyshkin said:
Wait, how does that work?! I've never seen that option in Settings. Are we really talking about the NST? I know the Glowlight model (as opposed to the NST Glowlight) has the option to download other dictionaries, but I don't think the NST versions of the hardware ever did.
Click to expand...
Click to collapse
I confirmed that mine is indeed a Simple Touch and its model number is BNRV300, but I don't know if there is more than one NST model.
I have a NST *without* the glowlight, and I can see it on Settings > Reader > Manage Dictionaries, and I can also access it when I search a word while reading by clicking on a button labelled "Change Dictionaries."
Someone (Renate NST???) mentioned that the extra dictionaries are stored in a different folder, but I'm not sure if she is talking about the official dictionaries or some custom ones that use some extra software.
@nmyshkin, I hadn't thought that most users wouldn't know about the other dictionaries, and after thinking about, I noticed that I only found them by chance.
I edited the original message to provide more details on that.
renatogoes said:
@nmyshkin, I hadn't thought that most users wouldn't know about the other dictionaries, and after thinking about, I noticed that I only found them by chance.
I edited the original message to provide more details on that.
Click to expand...
Click to collapse
OK, but there is still much to be sorted out. I have attached a screenshot of the stock 1.2.2 Settings>Reader (no dictionary sub-level) below. It is all I have ever seen in many years of using the NST on FW 1.2.1 and 1.2.2. If I had seen what you are describing I would have tried to include it in my expanded Nook Settings app. But there is nothing else. No way to go to another screen, etc.
So....what does your device display in the "About Your Nook" section? It doesn't seem possible that it's US firmware. I can understand dictionary options in the UK firmware because maybe some would cross the Channel, but not the US firmware.
Curiouser and curiouser.
Edith, another thought. If, back in the day, you installed a custom ROM like the one cooked up by @pinguy1982, that may be the difference. I believe that ROM was based on UK firmware. If that's it, you're out of luck unless you can find someone who actually installed these dictionaries because with FW 1.2.1 the difference between the UK and US firmware was eliminated, and you can't do anything vis-a-vis B&N with FW 1.2.1 any longer.
OK, but there is still much to be sorted out. I have attached a screenshot of the stock 1.2.2 Settings>Reader (no dictionary sub-level) below. It is all I have ever seen in many years of using the NST on FW 1.2.1 and 1.2.2. If I had seen what you are describing I would have tried to include it in my expanded Nook Settings app. But there is nothing else. No way to go to another screen, etc.
Click to expand...
Click to collapse
Mine has two entries inside Reader, the first one to configure the buttons as in your screenshot, and the one to manage the dictionaries.
So....what does your device display in the "About Your Nook" section? It doesn't seem possible that it's US firmware. I can understand dictionary options in the UK firmware because maybe some would cross the Channel, but not the US firmware.
Click to expand...
Click to collapse
It has some info about the account registered, the MAC address and Serial number, and the info about the model/firmware only have:
Software version -> 1.2.1
Model Number -> BNRV300
But it doesn't say anything about it being the US or UK version.
I think it is the UK since I have the Oxford dictionary named as `ox_en_GB.db` inside the dictionary folder.
When I checked the update zip on B&N site it had different files, which I think refer to the Merriam-Webster for the US version.
Edith, another thought. If, back in the day, you installed a custom ROM like the one cooked up by @pinguy1982, that may be the difference. I believe that ROM was based on UK firmware. If that's it, you're out of luck unless you can find someone who actually installed these dictionaries because with FW 1.2.1 the difference between the UK and US firmware was eliminated, and you can't do anything vis-a-vis B&N with FW 1.2.1 any longer.
Click to expand...
Click to collapse
It has been too long for me to remember exactly what I did, but I think I hadn't flashed a custom ROM because I only wanted to root it to install some random apk to read manga and I hadn't modified the ones for epubs.
renatogoes said:
I think it is the UK since I have the Oxford dictionary named as `ox_en_GB.db` inside the dictionary folder.
When I checked the update zip on B&N site it had different files, which I think refer to the Merriam-Webster for the US version.
Click to expand...
Click to collapse
I think so, too, but I want to check the 1.2.1 UK update zip (the final UK only version) and see what's inside. If that's where the difference is, then those dictionaries are probably long gone. Even if one were to install the Settings app from the UK version, the URLs for fetching the dictionaries would likely point to non-existent UK servers that B&N shut down long ago.
It would be interesting to know if the dictionary format changed from the NST to the "Glowlight" model (still not sure where in the lineup that one is...they really should have been more careful with their model naming). A Google search on Nooks and dictionaries yields a few hits that show something similar to what you are describing (I guess) but for the "Glowlight" model, not the NST. Since there would be some of those still out there, those would be the people to find--IF the dictionary format is the same.
Edit: yes, it's UK firmware. I took a look at the UserGuide from the 1.2.1 UK update zip. When the dictionary is in use (i.e., when you look up a word while reading) it shows an option to "change dictionaries". That is not present in the US firmware. Also, although there is no picture shown, it does mention the "Manage Dictionaries" option from Settings>Reader. It sounds a lot like what I read about the "Glowlight" model, probably looks the same too. So some non-English dictionaries still exist and are available to "Glowlight" owners. Whether their format is compatible with the NST is another question. You need to find an owner of the correct (rooted) model to find out, or get really lucky and find someone who kept their UK NST intact and downloaded a whole bunch of dictionaries in the past before B&N killed the servers there.
The old NST dictionaries were in the format of an SQLite database where the entries were zip files of HTML for each word.
This (overblown) implementation would have allowed images in addition to text for an entry.
I made a separate implementation that used dictionaries that were an SQLite database with deflate of HTML for each word.
That reduced size and complexity a bit.
I don't use the stock reader and I've given up on any usage that requires selecting text with your finger in a reader.
I have a separate application (Lookup.apk) that accesses dictionaries.
(Hmm, looking at this, I realize it needs some more attention.)
I also have a few dictionaries in the new format.
I'm not even sure if the new stock 5.0 even has dictionaries anymore.
If someone knows and can find the actual dictionary, please post it. Erm, it does.