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.
Now that I have the update to 2.3.4 I expected to be able to install the demokit and start controlling an arduino board.
The error message is "com.android.future.usb.accessory" shared library is missing. Did HTC leave out the ADK stuff from their 2.3.4?
Is there any way to enable it? Put a jar in the correct place or something?
Shared library missing
jonwa said:
Now that I have the update to 2.3.4 I expected to be able to install the demokit and start controlling an arduino board.
The error message is "com.android.future.usb.accessory" shared library is missing. Did HTC leave out the ADK stuff from their 2.3.4?
Is there any way to enable it? Put a jar in the correct place or something?
Click to expand...
Click to collapse
I kind of have the same problem, but on the Bravo, some apps install fine, others are giving exactly your error.
I read somewhere you need to reflash the gapps.zip, since it contains this famous Maps API.
Also the app dowloader which you get when you do a full wipe doesn't come up. (you know the one that let's you choose which google bloatware ;-) needs to be installed/downloaded
I tried that, but either do not have the proper gapps file or it fails to install.
I have the coolbliss rom right now with the sense 3.5 port to android 2.3.4.
(don't really like sense, but I wanted to know where it's at)
Does anybody have any pointers other then reflashing the gapps.zip.
Mayby some terminal command that rebuilds this Maps API I keep reading about?
It seems to be limited to apps that somehow keep track of your location I think.
Before I also had a package error, but that one mysteriously went away...(for now at least)
The cm7 never had this, I am missing something here?
jonwa said:
Now that I have the update to 2.3.4 I expected to be able to install the demokit and start controlling an arduino board.
The error message is "com.android.future.usb.accessory" shared library is missing. Did HTC leave out the ADK stuff from their 2.3.4?
Is there any way to enable it? Put a jar in the correct place or something?
Click to expand...
Click to collapse
Please, follow this thread:
github.com/ezterry/manifest-gingerbread-DS/issues/32
You can get the jar and xml from here:
forum.cyanogenmod.com/topic/26339-usb-accessory-mode-is-adk-supported-in-cm-7/
Hope it helps ya.
Greetings,
I started a project with Eclipse, and have mostly been running against a Galaxy S3. However, I wanted to test my program against a Droid 3 that I also have.
Well, I ran into a snag after installing the 2.3.3 SDK.
Basically this error in my AndroidManifest.xml:
error: Error: String types not allowed (at 'configChanges' with value 'keyboard|keyboardHidden|orientation|screenSize'). AndroidManifest.xml
I did some reading, and discovered there was an API change and I was able to get this working by removing the "screenSize" attribute.
My question is: Is this the correct way to support older phone versions? It seems like I am removing something, potentially, from newer versions.
Input welcome! Thanks!
jagauthier said:
Greetings,
I started a project with Eclipse, and have mostly been running against a Galaxy S3. However, I wanted to test my program against a Droid 3 that I also have.
Well, I ran into a snag after installing the 2.3.3 SDK.
Basically this error in my AndroidManifest.xml:
error: Error: String types not allowed (at 'configChanges' with value 'keyboard|keyboardHidden|orientation|screenSize'). AndroidManifest.xml
I did some reading, and discovered there was an API change and I was able to get this working by removing the "screenSize" attribute.
My question is: Is this the correct way to support older phone versions? It seems like I am removing something, potentially, from newer versions.
Input welcome! Thanks!
Click to expand...
Click to collapse
Try building with the latest SDK, then use android:minSdkVersion to control which devices are supported.
You should find (I think) that your old device just ignores 'screenSize' in the manifest.
PicomatStudios said:
Try building with the latest SDK, then use android:minSdkVersion to control which devices are supported.
You should find (I think) that your old device just ignores 'screenSize' in the manifest.
Click to expand...
Click to collapse
Thanks, that makes perfect sense. This seemed to work okay. I had to select the physical device in the Android manager, but otherwise worked fine!
jagauthier said:
Thanks, that makes perfect sense. This seemed to work okay. I had to select the physical device in the Android manager, but otherwise worked fine!
Click to expand...
Click to collapse
No problem. Generally you should set android:targetSdkVersion="nn" and target=android-nn (project.properties) to the latest number (e.g. 18), test on a device/emulator with the latest build and then generally speaking it'll degrade fairly gracefully to older devices.
I'm not sure if anyone will find this of use, but I did so I figured I'd post it for everyone to use:
I recently ran into issues running a few binaries on my V10. After doing a bit of research I found that non-PIE (position independent executables) will not run on newer devices (5.0+). Given I needed to run non-PIE binary, I looked further into a fix. This lead me to a thread posted here on XDA about bypassing the PIE check on Android L for the Nexus 5. Unfortunately the linker included in this fix is not usable by our device. Thankfully the linked thread goes into some detail about how to patch /system/bin/linker to allow non-PIE binaries. After reading into the provided information, I was able to patch our own linker and get my non-PIE binary to run just fine.
I've thrown together a flashable ZIP that simply replaces /system/bin/linker with a patched version that will allow non-PIE binaries. :good:
As a note:
Code:
[I]
[B][COLOR="Red"]
I HAVE ONLY TESTED THIS ON MY OWN LG V10 H901 ON MARSHMALLOW (6.0).
I CANNOT VOUCH FOR ANY OTHER MODEL, VERISION, OR DEVICE. AS ALWAYS
BE SURE TO PERFORM A BACKUP BEFORE FLASHING![/COLOR][/B]
I am, by no means, a developer. I simply dabble in Android for fun. I am not
responsible for any issue(s) caused by using this patch and you are doing
so at your own risk.
[/I]
So what this does is allow older non 6.0+ compatible apps to work?
Swizzle82 said:
So what this does is allow older non 6.0+ compatible apps to work?
Click to expand...
Click to collapse
It's helpful for any app with binaries that don't support position independent execution. In my case it allowed me to use my debugging server (which wouldn't run otherwise).
this works on the latest cm build for the htc one m8
but im a little confused as to which byte was modified can you please explain how you found which byte to replace i am using hex editor on my phone and cannot find the hex allocation mentioned in the forum
well i thought it worked until i went to restart my phone and it woudnt boot... thankfully tho i didnt delete the old linker file i just renamed it to linker.old so i was able to boot into my recovery and use its file manager to fix the issue
for now i guess i will create a script to automatically switch the file when i shutdown my phone and switch it back when it starts
Hi Guys!
I would be happy if someone could post a tutorial on how to Bypass PIE on Android 6.0.1
I have some experience in disassembling ELF files, but do not know where to look for disabling PIE in linker file. I would like to learn how to do it on my own, so i am not asking someone to patch my linker file.
Using G928F with Android 6.0.1
Thank you in advance!
Please help me to patch my linker
Works on Samsung J710MM (Marshmallow 6.0.1) perfectly. Thanx a lot!!!
Could anyone help me bypass PIE On marshmallow Touchwiz 6.0.1 would greatly appreciate your help?
Deleted
Hey guys, a new version of Phoenix OS (v2.0.7) is out and I have created rooted images for you guys to use.
Instructions:
Download the correct system rooted.7z file provided in the Download section and extract it
Install Phoenix OS and restart your computer.
Boot into Phoenix OS and finish the system initialization wizard. Restart the computer and boot into your main OS.
Go to C:\Phoenix OS (or wherever your Phoenix OS installation is) and replace the system.img file that's already there with the one you just downloaded
Reboot your computer now and boot into Phoenix OS.
Install the latest version of SuperSU. Sign in to Play Store using your Google account and update SuperSU that way. If you for some reason cannot use the Play Store, you can find SuperSU on the official thread. Download the flashable zip, extract Superuser.apk from the common folder, and install it in Phoenix OS by opening the .apk file with the default file manager that comes with the OS.
Update the binary by choosing Normal and your Phoenix OS should now be fully rooted
Download:
Phoenix OS x86 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.151.32bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNVGpBZmxQS0dhRjg
Phoenix OS x64 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.150.64bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNclN5SGdFUGlTRGs
Download Phoenix OS v2.0.7 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6186
History:
Uploaded v2.0.7 system images
Oooh... now I can test this to see if it fixes my G+ compatibility issue
The Wrath of Kahn said:
Oooh... now I can test this to see if it fixes my G+ compatibility issue
Click to expand...
Click to collapse
Sure! Let us know if it works out well for you
meanhacker said:
Sure! Let us know if it works out well for you
Click to expand...
Click to collapse
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
The Wrath of Kahn said:
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
Click to expand...
Click to collapse
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
meanhacker said:
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
Click to expand...
Click to collapse
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
The Wrath of Kahn said:
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
Click to expand...
Click to collapse
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
If anyone get's "grub minimal bash like line editing issue" when trying to boot
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
meanhacker said:
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
Click to expand...
Click to collapse
I tried editing the build.prop before with no luck, but I'm not experienced in doing it so I may have missed the fields that I needed.
irex102 said:
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
Click to expand...
Click to collapse
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
irex102 said:
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
Click to expand...
Click to collapse
Hey I found some readied kernels that fixes all the issues on baytrail tablets for android x86 7.1: https://drive.google.com/drive/folders/0B1HDhURlGNctY045UWFhalo5MW8 All that's left is to patch a rom for these devices. More info found here: https://github.com/burzumishi/linux-baytrail-flexx10/issues/12#issuecomment-309275211
#Quest
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Nicojoy said:
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Click to expand...
Click to collapse
What version of Phoenix OS do you have installed? If you have v2.0.7, you're in the right thread, so go ahead and download either a 32 or 64-bit version of the rooted image and replace it with your current system.img.
This will work on a Nexus 9 or it only works in pc's?
when i update su binary like you say it says to me installation failed
edit: ifound soulition its to update super su to the latest version with play store or aptoide or arc market or app vn and the install the binary data its soooo easyyyyyyy
Waiting for rooted system.img for Phoenix OS 2.1.0
SU Binary busy?
So I followed the instructions (although the step 6 is kind of confusing, English is not my native language so...) booted with the rooted sys image, installed superSU from the Play Store and when I open it it says "SU binary busy" and send me to a FAQ where it says that
"The SU files are already occupied by other software, such as Kingroot."
So I need to install the binary somehow? or something went wrong?
Oh BTW, used Root checker and it says it's not propely installed
Thanks for the image, buddy
MrSlenderman said:
"The SU files are already occupied by other software, such as Kingroot."
Click to expand...
Click to collapse
I also ran into this problem using the newest version from the play store, I could avoid this though by installing version 2.79 through an apk.
But now it won't let me update the binary, since everytime I select "Normal" the installation fails after a minute or so.
Any ideas?
Guys, when to expect a rooted image for V 2.1.0 x86
thank you, but i bit confused about when i update the os,
so when i update the os, the rooted image will gone ? and i need to wait for another rooted image ?