https://wiki.ubuntu.com/Touch/Porting
Any Devs wanna start? I don't have the experience to even know where to begin
I hope someone does try, this could be really cool.
I can probably make this work, considering it's based of CyanogenMod 10.1. Now I just need to hope repo sync works with this, because it always breaks in the middle when I try to sync with paranoid 3.
I'm not at a computer right now, but I will let you know how it goes once I can get on one.
Sent from my NookColor using xda app-developers app
thejrcrafter2 said:
I can probably make this work, considering it's based of CyanogenMod 10.1. Now I just need to hope repo sync works with this, because it always breaks in the middle when I try to sync with paranoid 3.
I'm not at a computer right now, but I will let you know how it goes once I can get on one.
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
They have a switch to continue if failed in the middle.
Downloading repo now.
You guys probably know this...but just in case.
I installed this on my Nexus 7 yesterday. There are no apps, just screenshots of what the apps will be when they are ready. You can supposedly still make phone calls but that won't matter here. The UI was beautiful (I thought) but that is all they have done at this point.
Just saying, it is not even close to functioning as even a media device. I actually couldn't even get wireless up, although I think that is technically supposed to work. I never used it, but I would expect the NookBuntu to be way more functional at this point.
Not to rain on anyone's parade, porting new OS is a great way to learn new things, no matter your skill level. But don't expect much return on your investment at this point.
(Also, just because, make sure that there is a kernel and ramdisk and uboot and not a boot.img in whatever you build. The device tree should take care of that for you, but it didn't on AOSP for me, and I suffered as a result.)
mateorod said:
You guys probably know this...but just in case.
I installed this on my Nexus 7 yesterday. There are no apps, just screenshots of what the apps will be when they are ready. You can supposedly still make phone calls but that won't matter here. The UI was beautiful (I thought) but that is all they have done at this point.
Just saying, it is not even close to functioning as even a media device. I actually couldn't even get wireless up, although I think that is technically supposed to work. I never used it, but I would expect the NookBuntu to be way more functional at this point.
Not to rain on anyone's parade, porting new OS is a great way to learn new things, no matter your skill level. But don't expect much return on your investment at this point.
(Also, just because, make sure that there is a kernel and ramdisk and uboot and not a boot.img in whatever you build. The device tree should take care of that for you, but it didn't on AOSP for me, and I suffered as a result.)
Click to expand...
Click to collapse
What are the app extentions?
Gonna see what I can do to get it running anyway, since I have the entire repo.
moocow1452 said:
Gonna see what I can do to get it running anyway, since I have the entire repo.
Click to expand...
Click to collapse
That's awesome Moocow, let me know if you need any help testing.
I'm not terribly educated in the art of Android OS compiling, but if there's anything I can do to help, let me know.
tsukisan said:
That's awesome Moocow, let me know if you need any help testing.
I'm not terribly educated in the art of Android OS compiling, but if there's anything I can do to help, let me know.
Click to expand...
Click to collapse
And now I got to finish it, don't I? Get into XDA's Ubuntu Touch section, and start rooting around for porting tools, walkthroughs, and whatnot and we'll compare notes if one of us finds something the other doesn't.
I worked on building the phablet for the nook. I stopped because all reports were it works very badly with only 500 mb ram. Hashcode has ported it to the kindle fire and found he could only open a couple apps before it froze up. However, he did good work on porting and put the changes on github at https://github.com/KFire-Android . You can look for phablet branches on the otter branches. The kernel changes are also present in some of his repos. Look around those repos for good hints on getting started.The kindle fire is also an omap processor, albeit omap4, so it is close to ours. The changes should be similar.
Good luck.
drmarble said:
I worked on building the phablet for the nook. I stopped because all reports were it works very badly with only 500 mb ram. Hashcode has ported it to the kindle fire and found he could only open a couple apps before it froze up. However, he did good work on porting and put the changes on github at https://github.com/KFire-Android . You can look for phablet branches on the otter branches. The kernel changes are also present in some of his repos. Look around those repos for good hints on getting started.The kindle fire is also an omap processor, albeit omap4, so it is close to ours. The changes should be similar.
Good luck.
Click to expand...
Click to collapse
So the thing that's supposed to work better with lower grade hardware doesn't work better with lower grade hardware? Ain't that hysterical? :good:
It works somehow... on samsug 9003
voit said:
It works somehow... on samsug 9003
Click to expand...
Click to collapse
Well that's good. Right now, I'm trying to incorperate NookieDev source into the Manifest.xml to get it to properly build. It doesn't seem to be as easy as the fill in the blank I thought it was, but, progress is being made, I think.
Any progress on this?
Sent from my Nexus 4 using xda premium
Good news, I've gotten it to the point where I can brunch encore to try and make a new build.
Bad news, Brunch chokes up on mkimage, for reasons unknown to me. Seems like a problem for building an Android like image, but it escaped me thus far, and the irc on freenode is... of varying quality help to say the least.
Code:
make: *** No rule to make target `/home/user/Nook/out/host/linux-x86/bin/mkimage', needed by `/home/user/Nook/out/target/product/encore/ramdisk.ub'. Stop.
make: *** Waiting for unfinished jobs....
EDIT: Just figured out that I needed to patch the main.mk in build/core to specify a mkimage, now the compiler seems to be churning. Will update once something happens.
Well, it's something.
Anyway, have not had a chance to test this out on my own Nook yet, since it picked an excellent time to flake out on me. You do need to backup and completely wipe the device, assuming it even installs. (Did not work on just a Data/Cache wipe, anyway, and I need to recover my Nook after wiping emmc along with everything else, whoops.)
Anyway, it's like radioactive juice at this point, might kill your Nook, give it superpowers, or not really much of anything. YMMV.
https://docs.google.com/file/d/0B0iHVj8OqCAmMmhvMTY2d2cwbFk/edit
EDIT: It does install, but power on goes from Cyanoboot -> Backlight on -> Backlight off -> Device Off within a couple seconds, so more work is required. le sigh
EDIT2: Turns out that was because I only had the bootstrap on the device, no phablet-flash-preinstall that actually makes it work. :silly:
With both of them flashed, I get to Cyanoboot -> persistent black screen until I cut power. Common error, so I've heard and adb works, so there may be hope yet.
Ladies and Gentlemen, Children of All Ages. I give you Ubuntu Touch for the Nook Color!!
Conditionals:
1. I had to flash my homemade bootloader first (https://www.dropbox.com/s/q5g7mnadvkdmy8k/cm-10.1-20130511-UNOFFICIAL-encore.zip), then the Mobile World Congress Build of Ubuntu Touch. http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/ (quantal-preinstalled-phablet-armhf.zip)
2. Rotation is mismatched, so that it cannot recognize that it's trying to use the portrait setup in landscape, should be an easy enough fix. Jossed, as this is the MWC build, it's not really built for tablets, and the Nook gets confused on how to display thing
3. The big one. TOUCH SCREEN IS BROKEN. Granted, it makes it more of a clock than anything useful, but Ubuntu has been built and runs on the Nook Color. Built a new bootstrap based on CM 10.1 RC2, works like a glove. Still not all that much more useful compared to a clock, but that's by design.
Super duper special thanks for the guys in the Ubuntu-Touch mailing list and irc.freenode.net #ubuntu-touch and #nookcolor, who I could not have done this without.
moocow1452 said:
Ladies and Gentlemen, Children of All Ages. I give you Ubuntu Touch for the Nook Color!!
Conditionals:
1. I had to flash my homemade bootloader first (https://www.dropbox.com/s/eaxcz91x7rm36tg/cm-10.1-20130508-UNOFFICIAL-encore.zip), then the Mobile World Congress Build of Ubuntu Touch. http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/ (quantal-preinstalled-phablet-armhf.zip)
2. Rotation is mismatched, so that it cannot recognize that it's trying to use the portrait setup in landscape, should be an easy enough fix.
3. The big one. TOUCH SCREEN IS BROKEN. Granted, it makes it more of a clock than anything useful, but Ubuntu has been built and runs on the Nook Color.
So, what next?
Click to expand...
Click to collapse
Looks cool. What's next? fixing touchscreen and fix rotation.. the rotation bit, depending on what the issue is, might be fixed by a change to the kernel config or drivers-- see https://github.com/NookieDevs/andro...mmit/7894401f916eb90b08f113a0cedf4f4d12a1ed77 and https://github.com/NookieDevs/andro...mmit/297a7593c56a75691eb7a7ea4aabab4a052273c3
that's a kernel config flag sluo added. You can also play with the peripheral board file for more control... https://github.com/NookieDevs/andro...rch/arm/mach-omap2/board-encore-peripherals.c
Sweet Tiitties!
Sent from my NookColor using xda app-developers app
AgentCherryColla said:
Sweet Tiitties!
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
Indeed. Especially now that with the latest get of CM for Encore, I got touch screen working for the MWC demo. (Somehow) Turns out that rotation isn't so much the issue as is resolution, everything being too big to properly fit on the Nook Screen, and it looking more like a phone than anything, but it effing works like the half assed demo it's supposed to be.
https://www.dropbox.com/s/q5g7mnadvkdmy8k/cm-10.1-20130511-UNOFFICIAL-encore.zip
EDIT: Do any of you guys want me to do a write up or a Youtube video on how to patch and build your own version of encore for your Nook machine?
Related
I think I may have read it requires dual core, but if not...what are the odds of us getting this bad boy (Google Body) on NC. I also wonder if any of the Galaxy S devices would run it?
Sent from my SPH-D700 using XDA App
abowlby said:
I think I may have read it requires dual core, but if not...what are the odds of us getting this bad boy (Google Body) on NC. I also wonder if any of the Galaxy S devices would run it?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
http://dl.dropbox.com/u/15218297/Body_1.0.apk
Tried but failed, but it looks like it requires HC sadly.
I'm sure it'll run once we have HC set up. The NC has a powerful (for an android device) GPU.
gallahad2000 said:
I'm sure it'll run once we have HC set up. The NC has a powerful (for an android device) GPU.
Click to expand...
Click to collapse
I wouldn't go as far as to say it's "powerful"
It's got the same GPU as the Moto Droid, which benchmarks just a tad bit below the Nexus One. Considering the Nexus One is significantly below the Galaxy S/Tegra 2 phones, we're basically at the low end of the GPU spectrum.
Which isn't too bad considering this is an E-reader
MrOtsKrad said:
http://dl.dropbox.com/u/15218297/Body_1.0.apk
Tried but failed, but it looks like it requires HC sadly.
Click to expand...
Click to collapse
mirror please. that poor dropbox account is a top hit in google and has been temporarily shut down LoL
Link3737 said:
I wouldn't go as far as to say it's "powerful"
It's got the same GPU as the Moto Droid, which benchmarks just a tad bit below the Nexus One. Considering the Nexus One is significantly below the Galaxy S/Tegra 2 phones, we're basically at the low end of the GPU spectrum.
Which isn't too bad considering this is an E-reader
Click to expand...
Click to collapse
try owning a hero if you want low end. nook blows it away. not nearly as high performance as my galaxy tab mind you, but nook color is definitely sufficient for most 3d operations.
I too have been wondering WHY body needs honeycomb... will be interesting to see if it can possibly run on something other than the xoom.
Please ... where exactly do I put that xoom fingerprint in my android os to make it appear as a legit honeycomb device in the market?
"ro.build.fingerprint=verizon/trygon/stingray:3.0/HRI39/101999:user/release-keys
xoom market fingerprint"
edit: oh nevermind - I'm going to assume it goes into build.prop. let me play wtih that a minute...
edit2: still can't see the body app on the market with that fingerprint in build.prop.
dkelley said:
edit: oh nevermind - I'm going to assume it goes into build.prop. let me play wtih that a minute...
Click to expand...
Click to collapse
I'm also wondering can those of us on the Honeycomb preview change our SDK version to 11 in the build.prop to allow us to install some of the Xoom apps? Might have issues I know but worth a shot.
I'll try it on my NC when I get home. Just curious if anyone else has tried it.
Link3737 said:
I wouldn't go as far as to say it's "powerful"
It's got the same GPU as the Moto Droid, which benchmarks just a tad bit below the Nexus One. Considering the Nexus One is significantly below the Galaxy S/Tegra 2 phones, we're basically at the low end of the GPU spectrum.
Which isn't too bad considering this is an E-reader
Click to expand...
Click to collapse
It's run every game I've thrown at it (other than ones with compatibility issues, e.g. Mystique). I'm sure there will eventually be apps it's not powerful enough to run but I don't think there's any currently.
I have the apk i can shoot someone to mirror
Post Removed.
Any chance you can email it to me? I'd like to try it out also....
dan
at
lantzer
dot
org
Thanks!
I have a modified HC sdk image that it shows up as a XOOM to Google. It's more than just a simple fingerprint change but nothing too complicated either. I actually have a Market ID too so I can see my NC's HC device when logged into the web based market. I also modified things so that it appears to apps that I've API level 11 installed since that's why the Google Body app was failing to install (parsing error). So now it installed and I've got the Google Body app icon showing in my launcher. However, it just force closes when run. I'm think it's the difference in the APIs, etc between the SDK preview and the final build that might be holding it back. Perhaps updating some of the "Lib SOs" would improve things, I don't know. If not that, then it's might be because it only supports the Tegra platform. In that case, it's probably hopeless unless Google to expand on that?
epakrat75 said:
I have a modified HC sdk image that it shows up as a XOOM to Google. It's more than just a simple fingerprint change but nothing too complicated either. I actually have a Market ID too so I can see my NC's HC device when logged into the web based market. I also modified things so that it appears to apps that I've API level 11 installed since that's why the Google Body app was failing to install (parsing error). So now it installed and I've got the Google Body app icon showing in my launcher. However, it just force closes when run. I'm think it's the difference in the APIs, etc between the SDK preview and the final build that might be holding it back. Perhaps updating some of the "Lib SOs" would improve things, I don't know. If not that, then it's might be because it only supports the Tegra platform. In that case, it's probably hopeless unless Google to expand on that?
Click to expand...
Click to collapse
Can you please post the details of what you did for other changes to your NC, besides the fingerprint. I downloaded the 'build.prop' for the Xoom already, but only changed a couple of lines in my NC's .prop file. However, I do not see Google Body in the Market.
I would like to get my NC to look as much like a Honeycomb device as possible.
Thanks!
360Razir said:
However, I do not see Google Body in the Market.
Click to expand...
Click to collapse
Sorry, I wasn't clear. Google Body still doesn't show. I expect that's because the Market may be looking at the fact the NC's build.prop doesn't say "Tegra" like the XOOM does. Can't change this since the device won't boot that way. However, pushing the APK via ADB worked. It previously failed to even do that with the stock HC v4. If it would help several others out, perhaps I should create a new thread offering a mod, etc to automate some of the changes since I had to do more than the modify build.prop itself. There will likely still be some manual steps and the patch will require working adb (even though many commands already run automatically).
epakrat75 said:
Sorry, I wasn't clear. Google Body still doesn't show. I expect that's because the Market may be looking at the fact the NC's build.prop doesn't say "Tegra" like the XOOM does. Can't change this since the device won't boot that way. However, pushing the APK via ADB worked. It previously failed to even do that with the stock HC v4. If it would help several others out, perhaps I should create a new thread offering a mod, etc to automate some of the changes since I had to do more than the modify build.prop itself. There will likely still be some manual steps and the patch will require working adb (even though many commands already run automatically).
Click to expand...
Click to collapse
can you post what steps you did? doesn't have to be automated, but I would like to know how to get google body on my NC, right now i'm running Honeycomb off of the SD card.
Also for people wanting the link to google body, tinpusher posted a link here http://forum.xda-developers.com/showpost.php?p=11788921&postcount=50
it's multiupload.com/PFJZDK11I0
we need real sdk level 11, with the honeycomb APIs either from aosp, the final SDK, or reversed engineered from the xoom.
Sent from my Nexus One using XDA App
hey guys... ok im a complete noob and have no idea what all this Xoom and Honeycomb and bla bla is... bottom line tho is i was wondering if there is anyway to run google body on my Galaxy S... Currently im running darkys v9.2...
any light on the topic will be highly appreciated as i really need such an app professionally...
thanks!
Any progress on this? Not being able to run Google Body is the one thing holding me back from purchasing a Nook Color.
I am starting to think that we will never have a fully funtional device.
Are there any examples of xdandroid having an almost perfect port?
Sent from my MSM using Tapatalk
bijan588 said:
I am starting to think that we will never have a fully funtional device.
Are there any examples of xdandroid having an almost perfect port?
Click to expand...
Click to collapse
Devs are making leaps and bounds recently... the list of bugs is just so high, there's a lot of little things to squash - with the addition of pieces of hardware still not being functional.
So have a little patience, and show a little respect. We'll get there eventually - and as always, patches welcome - if you think you've got the talent to fix things fix them and give us patches! Don't sit on the sidelines and ***** about how stuff doesn't work. Doesn't do anyone a damned bit of good.
bijan588 said:
I am starting to think that we will never have a fully funtional device.
Are there any examples of xdandroid having an almost perfect port?
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
we are "stable" look at Arrrghs post below
BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes
Originally Posted By: arrrghhh
I was running this bundle for a while and in the begining I did have some issues but that's cause I didnt know crap. but now that I have learned a litle about each bundle and how they work and how to make it run better, I said good bye to windows and hello droid.
I'm testing another bundle and so far its prettty good.
THANKS TO ALL DEVS, ARRRGH PLEASE EXCUSE THOSE WHO COMPLAIN BUT DONT DO ANYTHING TO FIX THINGS. THANKS ARRGH FOR ALL YOUR WORK AND I AM SCREAMING DAMN IT!!!!!
bijan588 said:
I am starting to think that we will never have a fully funtional device.
Are there any examples of xdandroid having an almost perfect port?
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
It really depends, partially on usage scenarios. xdandroid FRX05/06 on RHOD300 is close to what many WinMo ROMs achieved in terms of general stability. It's actually better than the old version of Energy I was using (which hung on boot 50% of the time, but would be fine after that.) I'm using the xdandroid source tree myself as my daily phone with lots of success.
Power management issues are getting knocked down pretty fast (major focus right now for the devs, primarily being worked by WisTilt2)
RIL issues are on the way to resolution, thanks to independent efforts by highlandsun and WisTilt2. I'm personally hoping to maybe see WisTilt2 hand off his work to highlandsun so WisTilt2 can resume working the kernel PM stuff
Bluetooth is in progress - sounds like we're close, but it's lower priority. Unfortunately the Bluetooth commits and WisTilt2's latest PM work are conflicting, so there isn't a kernel that includes both the improved PM and the improved BT support. I suspect this will change in a week or two.
GPS - It's functional enough for most people, so currently is very low priority. I've done a little work here since I'm not really qualified to work some of the other stuff. Ideally the GPS will get cleaned up so it doesn't wakelock us (we have an easy workaround for that), and time/loc injection can be implemented for faster locking (This requires a significant reverse engineering effort though - Qualcomm changed the interface enough with newer gpsOne solutions that I don't think we can use the code/documentation from the cyanogenMod and AOSP GIT trees.). Lack of XTRA isn't a priority at all for those running from SD, it's a big issue for NAND though.
The progress made in the last several months has been significant. Back near the beginning of the year I was having to delete my data.img and restore from backups every few days. The latest kernels and system releases have solved a ton of issues.
Bluetooth and ril fixes are all that's needed to make me completely forget about Windows mobile on this phone.
toadlife said:
The progress made in the last several months has been significant. Back near the beginning of the year I was having to delete my data.img and restore from backups every few days. The latest kernels and system releases have solved a ton of issues.
Bluetooth and ril fixes are all that's needed to make me completely forget about Windows mobile on this phone.
Click to expand...
Click to collapse
I already forgot about windows. I use droid daily. it's stable enough for me
arrrghhh said:
Devs are making leaps and bounds recently... the list of bugs is just so high, there's a lot of little things to squash - with the addition of pieces of hardware still not being functional.
So have a little patience, and show a little respect. We'll get there eventually - and as always, patches welcome - if you think you've got the talent to fix things fix them and give us patches! Don't sit on the sidelines and ***** about how stuff doesn't work. Doesn't do anyone a damned bit of good.
Click to expand...
Click to collapse
Sorry, I'm not tryin to complain.
I was just thinking "has ther ever been a 100% port of android to a windowss phone"
I dident intend to sound like a spoiled brat, and I understand a ton of work goes into this project.
Sadly I only know java and am of no use to you guys, if I tried to help I would end up being anotheeeeeeeeeeeeeeeeer tiad 8.
Oh look! The famus key stuck bug
Sent from my MSM using Tapatalk
bijan588 said:
Sorry, I'm not tryin to complain.
I was just thinking "has ther ever been a 100% port of android to a windowss phone"
I dident intend to sound like a spoiled brat, and I understand a ton of work goes into this project.
Sadly I only know java and am of no use to you guys, if I tried to help I would end up being anotheeeeeeeeeeeeeeeeer tiad 8.
Oh look! The famus key stuck bug
Click to expand...
Click to collapse
Yes, there are still bugs out there.
There are two WinMo phones that I'd say have a 'complete' port - HD2 and Vogue. Now I don't think every single feature has been matched, but they're considered stable and almost every feature has been ported over to Android.
I'm on FRX05 with the 3/11 wistilt2 kernal and this thing is heaven. I don't get any lagging unless I run a crap ton of apps at once or try and download a ton of programs off the market at once (that would slow down any phone). I get through the day with about 40% battery still left. Bluetooth isn't completely working but I don't use that. What more are you looking for in terms of stability? Android can be even less buggy/laggy than some Winmo Cookie 2.0 ROMs in my opinion.
Wow, this is pretty impressive.
I'm an old TP2 (VZW) user, got a Droid X in October as a replacement.
I saw a video for the HD2 and figured I'd check out my old phone and see how Android development is going. I've kept my TP2 in case I ever did any world travel, so this is definitely something I'm going to start watching.
Just a few questions.
1) How does touching work as opposed to the stylus? I know WinMo was VERY stylus heavy and often finger presses would miss because they weren't exact enough. I was always under the impression that was hardware config. Since Android is working on these WinMo devices, I'll presume the stylus is useless now. Confirm / Deny?
2) What's not working exactly? I've gathered BT and GPS (but not sure exactly what doesn't work with GPS), but I'm sure there is more.
3) Can this be flashed as the default OS, or does it need to be launched as an EXE from the SD card?
4) Can someone guide me to the best install guide? I'm considering popping this on to my TP2 and playing around with it (via WiFi).
5) How well does WiFi hotspot work?
6) Are all builds rooted by default?
7) Recommendations for which ROM to use?
arrrghhh said:
Yes, there are still bugs out there.
There are two WinMo phones that I'd say have a 'complete' port - HD2 and Vogue. Now I don't think every single feature has been matched, but they're considered stable and almost every feature has been ported over to Android.
Click to expand...
Click to collapse
Yeah, my wife has the HD2 and *everything* (that I know of) works.
EtherBoo said:
Wow, this is pretty impressive.
I'm an old TP2 (VZW) user, got a Droid X in October as a replacement.
I saw a video for the HD2 and figured I'd check out my old phone and see how Android development is going. I've kept my TP2 in case I ever did any world travel, so this is definitely something I'm going to start watching.
Just a few questions.
1) How does touching work as opposed to the stylus? I know WinMo was VERY stylus heavy and often finger presses would miss because they weren't exact enough. I was always under the impression that was hardware config. Since Android is working on these WinMo devices, I'll presume the stylus is useless now. Confirm / Deny?
2) What's not working exactly? I've gathered BT and GPS (but not sure exactly what doesn't work with GPS), but I'm sure there is more.
3) Can this be flashed as the default OS, or does it need to be launched as an EXE from the SD card?
4) Can someone guide me to the best install guide? I'm considering popping this on to my TP2 and playing around with it (via WiFi).
5) How well does WiFi hotspot work?
6) Are all builds rooted by default?
7) Recommendations for which ROM to use?
Click to expand...
Click to collapse
1) All UI elements are large enough that I've never had a need for the stylus in Android. However, since it is a resistive touchscreen, often "fingertip" dragging isn't so hot (single-presses OK, dragging less so) - Fingernails are great for this. I'd say it's about on par with my Huawei S7 in terms of touchability.
2) 3.5mm jack is completely nonfunctional on devices that have it
Headset via ExtUSB is flaky - few people use it so it doesn't get much testing/dev attention
BT is nonfunctional right now, I'd say it's the biggest "missing" item
GPS is usable but has performance issues in terms of initial lock times. Once locked it works great. There are two issues - Ephemeride preloading (XTRA, or in terminology more familiar on the WinMo side, QuickGPS) is not implemented. Fortunately XTRA loading can be done from WinMo prior to booting Android. There's also GPS time/location injection used to "warm start" the GPS - also not implemented.
Camera is a little flaky, but there have been major strides in that in the past month
Power management is still a little flaky, but I think WisTilt2's kernel work is nearly complete
Our RIL has definite known issues, esp. on CDMA phones. WisTilt2 was working it a bit, and highlandsun has made MAJOR improvements in just the past week
bijan588 said:
Sorry, I'm not tryin to complain.
I was just thinking "has ther ever been a 100% port of android to a windowss phone"
I dident intend to sound like a spoiled brat, and I understand a ton of work goes into this project.
Sadly I only know java and am of no use to you guys, if I tried to help I would end up being anotheeeeeeeeeeeeeeeeer tiad 8.
Oh look! The famus key stuck bug
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
The HD2 has a pretty close to 100% port of android... the HD2 is even starting to get it's own CM7 build... not a port, a build made specifically for it. I think it was easier porting android to the HD2, though, because there are many similar android devices that use similar hardware. Also the HD2 seemed to have a lot more devs working on the project.
I love my HD2... it's my main phone and will be for at least another 6 months. Currently running WP7 on NAND and running a CM7 build from my SD card, and even running from SD card, it runs about as well as a native android device. It's going to be hard to move on to a new phone when I'm used to being able to run both WP7 and Android.
Anyways, sorry for the HD2 talk in the Rhodium forum. I'm new in this section... just got myself a T-Mobile Touch Pro 2 to play with and use as spare phone, so I'll be around these parts more from now on.
Is cotulla still working on magldr for the rhodium? Any recent news on that. Having magldr can make the rhodium much more like a native android phone, especially if he has recovery support.
absolutely, magldr 113 is phenominal on my hd2, i'd never go back to windows again, i've been using frx06 with different highlandsun's ril and arrrghhh's kernel for a few days with verrry few problems. i can't wait to get it on nand and have a clockwork mod system
As to the HD2 - As I understand it, there seems to be far fewer variations between Snapdragon configurations as there were for MSM7k configurations.
As a result, it's a lot easier to target one of the rare non-Android Snapdragons when so many Snapdragons ran Android.
EtherBoo said:
1) How does touching work as opposed to the stylus? I know WinMo was VERY stylus heavy and often finger presses would miss because they weren't exact enough. I was always under the impression that was hardware config. Since Android is working on these WinMo devices, I'll presume the stylus is useless now. Confirm / Deny?
7) Recommendations for which ROM to use?
Click to expand...
Click to collapse
1 Winmo is much better for fingers. I can not use fingers for soft keyboard on Android. Seem to me that WM has a lot of filtering, that is missing in Android. Using my nails work pretty well though.
7 I recommend you try them all. All of them have issues. Find one you can live with
Many people has had success with Huawei, its pretty easy to install, so I would start with that. Does not work for me though.
FRX05/06 are easy ready-to-go-bundles as well.
EtherBoo said:
Just a few questions.
1) How does touching work as opposed to the stylus? I know WinMo was VERY stylus heavy and often finger presses would miss because they weren't exact enough. I was always under the impression that was hardware config. Since Android is working on these WinMo devices, I'll presume the stylus is useless now. Confirm / Deny?
2) What's not working exactly? I've gathered BT and GPS (but not sure exactly what doesn't work with GPS), but I'm sure there is more.
3) Can this be flashed as the default OS, or does it need to be launched as an EXE from the SD card?
6) Are all builds rooted by default?
7) Recommendations for which ROM to use?
Click to expand...
Click to collapse
1.) I much prefer androids UI to that of winmo, stylus is needed less but I still use it occasionly . But I didn't use it much in winmo eithar as iv grown good at precise use of the touchscreen But android is still a lot less fiddly
2.)Most of these have already been pointed out but as usual I'm adding in my own personally annoyance Idv3 tags in mp3s are not being read. So you can listen to your music, but album/artist/album art/ and da rest of it won't be seen in most mp3s.
3.) Great progress is being made. . . . .but atm its still reccomended to boot using HARET on sd
6.) Yes afaik the builds are rooted because root is access to /system . . .which seeing as its on the sd card it can be accesed/edited. (Btw can only onfirm for certain that root apps and exploring of root in android in neopeek builds . . . Havnt tried on an xda build as of yet)
7.)well first of all you need to decide wether you want to run a partition(neopeek) build , or a system.ext2 file (xda) build . . . . .you being new id recommend a build here on xda as setup is easier, that does leav you with less choices though but The latest FRX0- build should satify your craving for android . Arrrghhh has made a thread with the build and instructions.
Jandyman said:
2.)Most of these have already been pointed out but as usual I'm adding in my own personally annoyance Idv3 tags in mp3s are not being read. So you can listen to your music, but album/artist/album art/ and da rest of it won't be seen in most mp3s.
Click to expand...
Click to collapse
I'd like to address this issue.
I think this is simply an issue with ID3v1 and v2 tags. Have you made sure both tags are populated on your music?
If it's not this issue, then I'm not sure. I've only tried streaming music, haven't tried playing it locally yet...
teemo said:
1 Winmo is much better for fingers. I can not use fingers for soft keyboard on Android. Seem to me that WM has a lot of filtering, that is missing in Android. Using my nails work pretty well though.
Click to expand...
Click to collapse
I had this problem too but you can simply fix it by downloading a keyboard app from the market (like 'Gingerbread Keyboard' or 'SwiftKey').
I am using Gingerbread Keyboard and that is working much more exactly than the standard keyboard for me.
One more questi.
Is it possibe to make the browser scroll faster. And less choppy?
Sent from my MSM using Tapatalk
Hi there, it's me again!
After being away for quite some time due to a lot of issues with my netbook, and being busy with school, I recently checked the progress on the Flyer. As expected, Dexter did an excellent job already on Jelly Bean.
I tried the ROM, and I gotta say I'm quite satisfied with it. FWIW, I am thinking about getting the 3.0 kernel from the DHD to run on the Flyer. But, I have another project I'm thinking about which sounds more interesting.
So, is anyone interested in Open WebOS on the HTC Flyer? I am considering to give it a try this week, but only if there is some potential interest from the community. It would pretty much be an effort where I try to combine various challenges: getting WebOS to boot, and getting the Raspberry Pi to compile Android kernels, since my netbook does a horrible job at this.
Please report if it sounds interesting for you, and if I get positive answers, I'll do some research on the structure of OWOS.
Although WebOS seems nice I'd rather see you beat the crap out of JB and try to get it fully working until you say "I can't take this any further".
antis said:
Although WebOS seems nice I'd rather see you beat the crap out of JB and try to get it fully working until you say "I can't take this any further".
Click to expand...
Click to collapse
I'm not sure, I actually think JB has 1 major dev working on it. Sometimes it's better to have multiple, good, mostly stable options too chose from than 1 completely perfect one.
That aside, I don't use bluetooth headset so some people who do really want the devs to pool their work into that.
I'm all for web os though. And dual boot (don't push yourself ) would be awesome.
AidenM said:
I'm not sure, I actually think JB has 1 major dev working on it. Sometimes it's better to have multiple, good, mostly stable options too chose from than 1 completely perfect one.
That aside, I don't use bluetooth headset so some people who do really want the devs to pool their work into that.
I'm all for web os though. And dual boot (don't push yourself ) would be awesome.
Click to expand...
Click to collapse
I am using the latest JB ROM atm., and I'm wondering (since I haven't followed the development the last 2 months): what is really broken atm? Aside from bluetooth.
Mine VM with Ubunto is stil there for u if u decide to give Flyer some more of your time. Am I interested? I am interested in Flyer with as much hardware working posible; working BT for voice calls, music and movei playback. As long as those work well i dont care even if it is Win 3.11EE if it runs nice and smooth. However Geting camera and hw movie playback suport on JB would be very nice and would get the ROM to TOP level. U cracked those nuts on ICS; any way u give it a try on JB?
Welcome Back CHAOS I agree with Antis (even though I don't really Know the advantage of WebOs) i was hoping that You could do something like get the front camera working for Skype
Chaosz-X said:
I am using the latest JB ROM atm., and I'm wondering (since I haven't followed the development the last 2 months): what is really broken atm? Aside from bluetooth.
Click to expand...
Click to collapse
No HW playback support, no cammera and videorecorde, some flickering i belive,... rest is nearlly all there! So close to top BUT BT is FIXED (no report if for calls as well but rest been tested and reported 100% working BT functionalities)
I am not sure dual boot would be neat but i know thats asking alot. but like every one else don't matter to me if it JB OR ICS as long as we can get a nice and smooth working rom that has BT good HW for movies ect and cameras working i will be as happy as a puppy with to peckers ....
Chaosz-X said:
I am using the latest JB ROM atm., and I'm wondering (since I haven't followed the development the last 2 months): what is really broken atm? Aside from bluetooth.
Click to expand...
Click to collapse
Hardware Acceleration for video playback. WebOS would be interesting.
Chaosz-X said:
Hi there, it's me again!
After being away for quite some time due to a lot of issues with my netbook, and being busy with school, I recently checked the progress on the Flyer. As expected, Dexter did an excellent job already on Jelly Bean.
I tried the ROM, and I gotta say I'm quite satisfied with it. FWIW, I am thinking about getting the 3.0 kernel from the DHD to run on the Flyer. But, I have another project I'm thinking about which sounds more interesting.
So, is anyone interested in Open WebOS on the HTC Flyer? I am considering to give it a try this week, but only if there is some potential interest from the community. It would pretty much be an effort where I try to combine various challenges: getting WebOS to boot, and getting the Raspberry Pi to compile Android kernels, since my netbook does a horrible job at this.
Please report if it sounds interesting for you, and if I get positive answers, I'll do some research on the structure of OWOS.
Click to expand...
Click to collapse
Wow..it would definitely be very interesting! WebOS still will be a cool OS to try out.
By the way, thanks for coming back & welcome!
WebOS would be so slick.
Sent from my shooter using xda premium
I'm def interested!
Sent from my LT28i using XDA Premium HD app
@Chaos-X u been asked for Kernel source on :
http://forum.xda-developers.com/showthread.php?t=1724246&page=54
i belive to help with video decoding fix wich is missing in latest JB... U think u can help with this?
I personally would prefer a fully working JB ROM (we're sooooo close now), but WebOS would be a cool OS to fiddle with.
Sent from my ADR6350 using Tapatalks
Chaosz-X said:
I am using the latest JB ROM atm., and I'm wondering (since I haven't followed the development the last 2 months): what is really broken atm? Aside from bluetooth.
Click to expand...
Click to collapse
-Camera (front\back)
-Cant change CPU clock
-Some bugs with graphics
-External SD on AOKP is bad
-Boot animation
If you help him do it, it will be best ROM. Please.
yes, or maybe no...
while I'm a huge fan of webOS and would love to see it on the flyer I think your time may be better utilized by teaming with Dexter to finish ironing out the wrinkles in his JB build first, then perhaps a dual-boot option?
thewadegeek said:
Hardware Acceleration for video playback. WebOS would be interesting.
Click to expand...
Click to collapse
+1
I loved web os on my palm pre, just didn't like the hardware. I would love to have it on my view. Especially if we could dual boot it.
Sent from my JellyBean Evo View running CG Rom
rydehard86 said:
I loved web os on my palm pre, just didn't like the hardware. I would love to have it on my view. Especially if we could dual boot it.
Sent from my JellyBean Evo View running CG Rom
Click to expand...
Click to collapse
Never seen Palm Pre in russia. Is it good device?
kayoma said:
Never seen Palm Pre in russia. Is it good device?
Click to expand...
Click to collapse
Slide out keyboard had very small keys and the slider mechanism was very poor. Screen was also very small compared to today's phones. The only nice thing was wireless charging. That was awesome.
WebOS ran very well on it though.
Sent from my PC36100 using xda premium
While cleaning the garage, I found my wife's old nook BNTV250. She said I could have it. So, I've been trying to get a custom rom on there.
I have experience with custom roms. I have a Samsung Galaxy Note 2 running Philz and Lollipop as well as a Note 10.1 running TWRP and Kitkat. So, I have experience with successfully installing recoveries and flashing custom roms to devices.
This one isn't as easy for some reason.
I can get a rooted stock rom by following the directions here...
https://www.youtube.com/watch?v=hZyfWpBJpiE
but no matter what I try, I can't get any further than that.
When I tried to sign in with the google play store, I am told my password is bad (which it isn't). Then I get an email from google in my gmail account telling me that someone (which was me) has tried to sign in to my account but was denied because the device they were using is way too old. So, getting anything on to my device via the play store that I need, such as a terminal emulator, TWRP install, etc, is apparently out of the questions.
gapps won't flash without errors, so that is out of the question, too.
the included es file explorer won't see the internal SD card for a reason I haven't been able to figure out (yes, it has root access), so copying apk files over and installing them from there is out.
When I boot off of ann sd card, and attempt to flash custom recoveries from the internal storage, I am also unsuccessful. With TWRP, I get errors. With CWM, it says it was successful, but it isn't.
So, every road I go down to get CM on this thing is blocked.
Am I missing something, or did I just miss my window by not doing this two years ago?
xflbret said:
While cleaning the garage, I found my wife's old nook BNTV250. She said I could have it. So, I've been trying to get a custom rom on there.
Am I missing something, or did I just miss my window by not doing this two years ago?
Click to expand...
Click to collapse
Try:
1. A factory reset
2. The instructions here---they worked for me as a noob.
That could leave you with CM 10.2. If you'd like something higher, this post might send you in the right direction after you succeed with CM 10.x, but it does become more complicated. Or you can just try to get there directly.
It can't be too late:fingers-crossed: There's life in that tablet yet!
Edit: I see that the CM 10.2 build is no longer posted over at Cyanogenmod. If you want to try it, let me know. I have the zip file.
Sorry, I haven't posted my update yet. I managed to find a solution to the problem with the included es file explorer. That allowed me to install some apk's like terminal emulator which allowed me to get TWRP on, and then the figurative flood gates were open from there.
I am disappointed. I flashed both liquid smooth kitkat, and a lollipop build. Neither are very responsive, and both seem to have great difficulties awakening from a sleeping state (the lollipop one was worse). I looked around, but couldn't find a kernel to flash. Is there a kernel we should be using to speed up these roms? If not, I think I will give up because I stand stand the slowness.
xflbret said:
Sorry, I haven't posted my update yet. I managed to find a solution to the problem with the included es file explorer. That allowed me to install some apk's like terminal emulator which allowed me to get TWRP on, and then the figurative flood gates were open from there.
I am disappointed. I flashed both liquid smooth kitkat, and a lollipop build. Neither are very responsive, and both seem to have great difficulties awakening from a sleeping state (the lollipop one was worse). I looked around, but couldn't find a kernel to flash. Is there a kernel we should be using to speed up these roms? If not, I think I will give up because I stand stand the slowness.
Click to expand...
Click to collapse
I read through some CM11 threads and was amazed at the different experiences people had, ranging from "works great" to "really sluggish". Speaking only from a logical perspective it seems to me that the more advanced OS you try to shoe-horn into an older device, the more likely you will exhaust (or at least severely task) its hardware resources. Like trying to install Windows 10 on a machine designed for XP with hardware that just barely meets the minimum requirements of Win 10.
All I can say is that CM 10.2 works "great" on my NT. I've yet to encounter an app that I wanted which would not run (of course, my wants may not match yours). I can read the newspaper, listen to music, Kodi runs great--I can even stream a video from the NT to my TV (which has an old laptop connected) using VLCDirect. So lots of life in the thing from my perspective. CM 10.2 does get cranky once in awhile, but a reboot sorts that out. I expect many newer tablets are the same in that respect.
Let me know if you change your mind and want to try CM10.2
nmyshkin said:
I read through some CM11 threads and was amazed at the different experiences people had, ranging from "works great" to "really sluggish". Speaking only from a logical perspective it seems to me that the more advanced OS you try to shoe-horn into an older device, the more likely you will exhaust (or at least severely task) its hardware resources. Like trying to install Windows 10 on a machine designed for XP with hardware that just barely meets the minimum requirements of Win 10.
All I can say is that CM 10.2 works "great" on my NT. I've yet to encounter an app that I wanted which would not run (of course, my wants may not match yours). I can read the newspaper, listen to music, Kodi runs great--I can even stream a video from the NT to my TV (which has an old laptop connected) using VLCDirect. So lots of life in the thing from my perspective. CM 10.2 does get cranky once in awhile, but a reboot sorts that out. I expect many newer tablets are the same in that respect.
Let me know if you change your mind and want to try CM10.2
Click to expand...
Click to collapse
You talked me into it. I'll give 10.2 a shot. I'm assuming that's based on Jellybean. I think every app I want to use will still work on Jellybean.
Any recommended builds? Any recommended gapps?
xflbret said:
You talked me into it. I'll give 10.2 a shot. I'm assuming that's based on Jellybean. I think every app I want to use will still work on Jellybean.
Any recommended builds? Any recommended gapps?
Click to expand...
Click to collapse
I finally located the 10.x downloads here. I'm using the last stable build, 10.2.1 (Android equivalent 4.3.1). You should use the gapps package that is listed for 10.2 build here.
Like I said in an earlier post, I followed the excellent directions from digixmax here and while the initial boot was kind of confusing, things did sort themselves out. But that method assumes you are starting from stock. If you can't get back to there you'll need to try something else.
Once in a blue moon some app in the PlayStore will be listed as incompatible, I guess because Google can't quite figure out what to make of these modded tablets, even though the Android version is well within reach of CM 10.2. That happened recently to me with my local newspaper app. I just used this site to download the app outside the PlayStore and then side-loaded it. It installed and works just fine.
Good luck! I hope this all works to your satisfaction
Well, I installed CM 10.2. Everything works, albiet VERY slowly. I'm going to go google for a kernel now so I can do some overclocking. If I can't find one, then I'm afraid I'll have to let this go. It is just too slow and unresponsive the way it is to be productive.
xflbret said:
Well, I installed CM 10.2. Everything works, albiet VERY slowly. I'm going to go google for a kernel now so I can do some overclocking. If I can't find one, then I'm afraid I'll have to let this go. It is just too slow and unresponsive the way it is to be productive.
Click to expand...
Click to collapse
Sorry it didn't work out well for you. It's obvious to say, but either there is a hardware issue or something did not go right in the flashing. Otherwise no one would bother with these things.
You've probably already looked at this, but just in case, under Settings/Performance/Processor I show a resting CPU freq. of 300 MHz, the governor set at "interactive, and a max. CPU freq. of 1008 MHz. Theoretically you could try playing with those if you have the same figures, but I'm not sure where that would take you.
The only custom kernel I could find for this was for KitKat, so I reflashed with that. I clocked both the minimum and the maximum to 1200 MHz. Even at that, my Antutu benchmarks score was just under 14k, or less than half of the score for my Samsung Galaxy Note 2. I never got "great" results with this device so far, but the KK with the custom kernel is the best I have got so far. I'm tempted to try this KK kernel with the lollipop build to see what happens. If I do that, I'll report my results.
This device is over four years old now. Add to this that, at the time, it wasn't exactly designed to break any speed records. All it was intended to do is read ebooks, and play a few other select apps. No GPS, no bluetooth. I guess asking it to run today's resource intense apps like Facebook may be asking too much of it. But, for some weird reason, I can't let this go now. It is kind of like an electronic pet to me. I keep it by my easy chair, and I pick it up and start doing something with it quite often.
Yeah, I was just getting ready to point you toward the kernal for CM 11 but you got there without my direction.
It's really puzzling to me that your system seems so slow. Maybe mine is too! I've never owned a tablet before (I don't count my much-modded NST e-ink reader!) and this one running CM 10.2 seems just fine to me, certainly no worse than laptops I often work with. I have an inexpensive LG smartphone I just bought to use as an mp3 player after my much-loved Insignia Pilot finally died. It runs KitKat and seems about as responsive as my Nook Tablet, maybe slightly better, so I guess a lot is what we are used to.
BIG UPDATE, POSSIBLE FINAL BUILD!!!
Code:
I shouldn't have to say it, but when you hit/swipe the install button,
everythings on you. This was made for a J727perx/POPLTESPR, using a boost
mobile phone for testing. If your phone isn't from the suppliers listed in this
post, or you're not using something labeled perx, or are unfamiliar with the
term popltespr, don't try to use it. I won't be crying for anyone. That said, this
should be about as stable a ROM as you get when dealing with ROMs.
The new
J727PVPU3ARC2_MULTI_CERT_LIBERATE_X7s
New Video demonstration below
I wasn't able to make the YouTube link embed, but I hid the video like a good dude.
The video is of the actual zip that I uploaded for the download, you will start with a blue/purpleish light theme, changeable/disable in the theme center. No need to worry, but I always keep an backup of my EFS on the card, just in case.
Zero bloat, fully intact/tweaked system, with no knox.
If you discover some earth shattering problem, let me know, if not, I don't have anymore plans on taking this further. I'm flashing my personal build as of this post, if you want anything faster...I don't even know where to point you. With the right launcher(see my video of my personal build), and system setup, its scary fast.
Enjoy
Features"
-Highly tweaked stock rom-
-Fully debloated-
-Deodexed-
-Deknoxed-
-Aligned-
-Rooted-
-Xposed-
-ADB installed/remounted in the root-
-SQLITE-
-SYSRW-SYSRO-
-ext4 tweaks-
-INIT.D enabled, and fully tweaked-
-Fully built up build prop-
-RAM/battery optimization-
-Working system media player/FX(most noticeable with headphones)-
-DM-verity removed-
-Stock/light/dark themes built in-
-Custom boot/shutdown animation- (Are Back, you can still find more in my sig)
-Quicktiles for anything you could want-
-All stock features-
-Increased net/download speed-
-SEANDROID enforcing out of the box-
-Speed-
-SEPOLICY patched-
It's the fastest I've had my phone, very beautiful build.
Multi_Cert
This ROM should be ready for multiple service providers. It covers Sprint, Boost Mobil, and Virgin Mobil customers, and has built in boot animations for all 3 stock to prove it, along with vendor options. This is what I made the original ROMs with, ARA1 and ARC2. Until I recently reset my PC, and got a bunk Boost AP. All should be as good as everything was in the past builds, before the .3/.4 gen.
Hope you guys enjoy.
Love and Peace, and all that junk.
If you want to make use of my project, then read my sig, I got you covered.
Just downloaded ty bro. I'll let you know how it works out. Heading home now.
Nice, hope you enjoy, I'm posting one more, and have a 4 that goes further that I could send you. All features are working, service should be stable down to the 4th build...eh, I'll post them both.
J727P
TomeGJ7p said:
Nice, hope you enjoy, I'm posting one more, and have a 4 that goes further that I could send you. All features are working, service should be stable down to the 4th build...eh, I'll post them both.
Click to expand...
Click to collapse
Cool great work your x2 liking it very much ! Thank you !!
peter couniaz said:
Cool great work your x2 liking it very much ! Thank you !!
Click to expand...
Click to collapse
We have a gathering of our phones most active members here, lol. Glad you liked it, I was super proud of how these came out.
Updates in the OP. Not that it's that far away from this post.
Man it's phenominal. Flashed this morning, and it's kicking ass and taking names. I can really tell a difference on internet too. Thanks man.
Pc isn't picking up my phone with usb. Do you know what would be the cause? I know adb tether wasn't working already but I need to connect my phone so I can transfer music, pictures ect. I don't have micro/sd slot in pc or I'd just do that.
Also Xposed says it's incompatible and won't let me install. Says it's not compatible with processor ect. This one isn't a deal breaker, just wondering if something might be corrupt on my end somehow..
Turn off USB debugging when you want to use the usb with another device, should link instantly when you turn it off, and break when on. Not that it should, but does lol. I'm going to try something differen't with the xposed, if I make it work, I'll do my planned update with it fixed.
Was going to post an update with my android boot animation, and game over shutdown....could mix a few others, but didn't know if you guys were interested.
Peter had xposed working on our old firmware, so I had it working of course. On the new frimware, for whatever reason, it really hates anything starting with the letter X, I've been on this all day. My solution would be to completely pull xposed, keep the build quality/speed up, and offer custom qmp boot images out of the box. Let me know what you think, or, if you nail xposed, let know about that. I currently have the Android ULHD boot animation, swirling dots into flashing android, and pacman gameover shutdown on mine. I have a bit of a collection I could share, or you can find them on the forms I'm sure, but most don't flash right. Mine work lol. Let me know what you would like.
Probably have to pull xposed from the project, but I can at least add some flare to the roms. I was adding boot animations, and a built in EQ presets built for small speakers. Currently in testing.
Bootanimations are always nice
How about?
n00b-xda-disciple said:
Bootanimations are always nice
Click to expand...
Click to collapse
I could preinstall them, or I might be able to provide animations, and shutdown as seperate flashables, and let you guys do your own? I've been preping all of them for a go, just want to take a look at what I have. I don't have them in zips yet, but I don't thing it'll be too hard. So far I have Android_L_UHD(A/S), Amiga (A/S), Badman (S), PacMan game over(S), NexusBeam(A/S), Matrix(A/S), SamDisco(A), and a few others. There's a post on the forms with them, but they don't work on our phone in there current format.
I might find some videos, or make a little montage, or just get zips together.
In the meantime, I need to update 2.2, at the very least, and my op.
Looks like someone made a video on the thread, and also has the link there. If you flash them, it only affects the shundown, if anything.
UPDATE
Despite my best efforts, xposed did not work out. I pulled it, added more speed(everywhere), and a musicplayer/system FX EQ that work together, but don't like the phone speaker. It's a combination chosen after much testing, and with a decent pair of headphones, makes a very noticeable difference from preset, to bass, reverb, and virtualization. Like most additions, totally free, no adds, and worth adding.
2.2 is the only update, the rest will happen over the next few days, and all will be getting custom boot animations, along with the other mentioned changes.
J727P
TomeGJ7p said:
Despite my best efforts, xposed did not work out. I pulled it, added more speed(everywhere), and a musicplayer/system FX EQ that work together, but don't like the phone speaker. It's a combination chosen after much testing, and with a decent pair of headphones, makes a very noticeable difference from preset, to bass, reverb, and virtualization. Like most additions, totally free, no adds, and worth adding.
2.2 is the only update, the rest will happen over the next few days, and all will be getting custom boot animations, along with the other mentioned changes.
Click to expand...
Click to collapse
Ok use this apk an the ZIP you are using an it will work !!!!!
https://mega.nz/#!TEcxmAgQ!bCkqQBVxahScyk_jdWDirL9eRPOmBna787td3pOQClc
On the install of you Rom the framework is in it is the apk you are using !!!
all download links down for full updating. I'll post when they're back. if it's not a link for X#.3, it wont work. really good stuff coming.
All ROMs have new working boot/shutdown animations, new speed tweaks for almost everything, tested music player/system EQ(not working with system speaker, great with headphones), and, of course thank you peter couniaz for informing me of the importance of the installer, and linking it.
2.3 is up, the rest are syncing, and will be up in the morning, when I get up again.
All ROMs updated to the latest versions. Idon't believe I have anything more for quality or speed, everything is close to perfect while keeping the ROM technically stock. Lineage is still faster, but not by much, for our phone at least, and this looks so much better. Anyway, everyone enjoy the updated ROM, let me know what you think, and if you find any problems.
TomeGJ7p said:
All ROMs updated to the latest versions. Idon't believe I have anything more for quality or speed, everything is close to perfect while keeping the ROM technically stock. Lineage is still faster, but not by much, for our phone at least, and this looks so much better. Anyway, everyone enjoy the updated ROM, let me know what you think, and if you find any problems.
Click to expand...
Click to collapse
I will check it out tonight, ty for your hard work. You and Peter are awesome for working on the J7Perx. Much appreciated
Finally a dev who knows his works?good work bruh...will try it today
I flashed the X2.3 rom. Nice work, but there are a couple problems. The first thing I noticed was that the Xposed framework was installed during rom installation. The app is removed, but the framework is still installed. The next problem that I ran into was that a secured lockscreen takes a really long time to unlock (approximately 10 seconds).
jonny30bass said:
I flashed the X2.3 rom. Nice work, but there are a couple problems. The first thing I noticed was that the Xposed framework was installed during rom installation. The app is removed, but the framework is still installed. The next problem that I ran into was that a secured lockscreen takes a really long time to unlock (approximately 10 seconds).
Click to expand...
Click to collapse
I'm uploading 2.3 with the proper installer, I don't know how 2.3 was the only one to not get it. All others are fine, probably because 2.3 was the first updated. I'm working on figuring out the lock screen issue. I've checked so much that I'm running out of ideas. I'll update the download in the op with the new link once it's synced. Which will be like 10 minutes lol. Sorry about the lock screen, it permeates through to my final build it seems.
TomeGJ7p said:
I'm uploading 2.3 with the proper installer, I don't know how 2.3 was the only one to not get it. All others are fine, probably because 2.3 was the first updated. I'm working on figuring out the lock screen issue. I've checked so much that I'm running out of ideas. I'll update the download in the op with the new link once it's synced. Which will be like 10 minutes lol. Sorry about the lock screen, it permeates through to my final build it seems.
Click to expand...
Click to collapse
I just installed the latest version of 2.3. This one had the framework and the installer. However I have no data because it is recognizing it as a Sprint device instead of a virgin mobile device.
now that's interesting. I'm going to make another 2.3, in like 30ish minutes, and pm you a link to see if its fixed, sorry. The rom backs up efs at least. Brb