[XOOM 2/XYBOARD] Development Interest - Xoom Q&A, Help & Troubleshooting

So let me start off by saying, I am by no means a seasoned developer, just somewhat of a power user with a long time love for Motorola devices... Somebody has to root for the under dog, right? In any case, I want to sink my teeth into getting something custom running on the beloved Xoom 2.
To me it seems like it wouldn't be all that difficult now -- after all, we seem to have all the prerequisites for a custom ROM -- we've got root, we have a functioning bootstrap system, there are fastboot files available in case of a stuff up... The only thing we don't have is developer interest. To me that is really disappointing, in my personal opinion the Xoom 2 is a great device that could truly shine with a little bit of attention.
At the very least, I'd like to get CM10 running, after all, the MZ617 got an OTA update to JB, so the majority of the porting work is done... As far as I can tell, the only difference between my device (MZ616) and the 7 is lack of 4G and CDMA radios in the 616. In fact I see no reason that the OTA shouldn't work on a 616, however I don't want to run that risk and would much rather work on something truly custom that can be run in a ROM Slot and worked on, with the stock system there to fall back on in case of disaster.
Given that this hasn't happened already, I would wager that there are very few, if any, developers out there with these devices so I have a feeling I'm going to be undertaking this project on my own. That's fine, but this is mostly new territory for me and I don't even know if I'll succeed. I realise there are most likely threads related to topics like this already, but none that I could find dated past 2012...
I don't want to over hype this or give anybody false hope. Chances are, this won't work... But from what I can see, all the foundations are there for a solid custom build, there's just been nobody with the necessary skills to do the work. Hell, I'm not even sure I have the necessary skills, I've only ever ported a themed ROM which is nowhere near as much work as this.
The reason for my posting this thread is to gauge community interest in something like this. Personally, I'd love to see it done because I tend to not use my Xoom 2 because of it's old and inefficient software (does anybody else find 4.0.4 laggy and horrible?). I would benefit from this and it would breathe new life into my device... However, if there are others interested it might provide some extra motivation to get stuck into it. Alternatively, if anybody feels they have any talents or skills to add to this project then by all means, you're welcome to apply your talents. I'm going to look into using Git for this once I determine the best software to fork and work on.
N.B. Also, if anybody knows of an active mirror with the "Blur_version.0.268.4.MZ616.Retail.en.AU" fastboot file that I could get a hold of, I'd appreciate having some kind of fall back in case I brick my device attempting this!

I'd love to see KitKat on the Xoom2. Currently using the Verizon JB firmware and it's OK but a bit buggy, not sure if its this bad on a genuine Verizon device. If I could help I would but I'm an end user/noon so you might waste more time explaining stuff to me than the time I could save.

http://sbf.droid-developers.org/phone.php?device=23
Here are all the firmwares available but I couldn't find yours.
An Asian modder got the MZ617 to get the jelly bean update from the USA Droid models and I made the guide for the Xoom2/Xyboard 8.2 to get that update.
So we already have Jelly Bean, we have root, and we can use SafeStrap.
All we need is a custom rom.

I have the MZ615 EU and I am very interested in this project. I'm not a dev either but am will to help out in anyway I can, testing, promoting and so on. I am currently desperate for an upgrade from 4.0.4, probably lucky to have even got that from Moto I know but it is quite heavy compared to JB and KK. Delighted I found this thread and best of luck with the project.
Sent from my XOOM 2 using XDA Free mobile app

If there's a version of yours sold in America by Verizon wireless you may be able to put jellybean on it but my advice would be to not bother, it becomes laggy and horrible after a few weeks use so you just end up clearing data and going from scratch rather to often. KitKat with its low memory demands would be spot on.

Yeah, KitKat would be incredible to get if we can. My Xoom2 is in mint condition and still feel relatively new to me, I really don't want to replace it.
Sent from my XOOM 2 using XDA Free mobile app

I'm thinking about using RAZR kexec and try something on this, tho I don't have time, and my resources are low, will be just a favor I'll try to do to a friend who have one and asked me what can I do to get kk on it. No promises, but I'll see what I can get from other devs I know of around.
Enviado de meu LG-E975 usando Tapatalk

I am also interested in this project. Xoom 2 is a beatiful device, too bad Motorola keeps a locked bootloader, but Safestrap is there.
Also, some of the sources are released online by Motorola.

So, did anyone manage to get anywhere with this?

I would love to see Cyanogenmod brought to the Xoom 2. CM13 runs great on my old Galaxy S3 which is almost the same age as the Xoom 2. It's a real shame nobody seems interested in porting it.
Sent from my XOOM 2 using XDA-Developers mobile app

Related

[Q] Wondering why D2G is ignored by modding community

I went from a Motorola Milestone to a Droid 2 Global. And as much as I am enjoying the Fission ROM from Team DeFuse, I am wondering why there seems to be such low interest in the Droid 2 Global compared to the original Droid 2? Can anyone give me some info as to why this is the case? I realize that with the Droid 2 globals additional radios that that transcribes to more work to get those operational in a custom ROM, I just dont understand why this powerful phone is ignored and left to sit on the curb. Thank you to all in advance.
1. The Global is hard to dev for. There aren't many Global devices to go off of, so the radios are hard to get 100% working on custom roms
2. It was launched silently. No one really knows it exists, so it just didn't receive the initial dev bump that phones usually get when they're first released
3. It didn't sell very well. I can't speak for the whole sales numbers, but my friend who works for Verizon Corporate (or something like that) said the numbers weren't fantastic in New York.
4. Three devices is a lot. Any devs willing to work on the Global probably already work on the Droid X and Droid 2. Adding a third device to the list is just too much for people who do this as a hobby.
That's the best explanation I can give... sorry for how negative it was, lol.
To be fair, the D2G is receiving more support this last month or so. Look on droidforums.net, some good work being done on there (3 or 4 roms available).
I will keep an eye out on droidforums. I was also thinking that with the possibility of 2.3 coming out for it most devs dont (myself included) see a point in making a ROM on froyo when 2.3 is around the corner. Thank you for your input. Its much appreciated
Most of the correct answers were already stated...
Just wated to point out that only people who truly needed global support would buy the D2G.
Droid Pro got play merely because it was targeted at the Crackberry crowd conversion which really didn't work.
Those are the only two GLOBAL phone I know of. Doesn't make sense to make many more with the 4G revolution under way.
Business have bought into the form factor but the Devs they all look at the performance specs and the EASE of development regarding the model.
The biggest issue though is the locked bootloader! Since the boot loader is locked you can not run custom Kernels so any development that could be made is limited to the stock kernel.
All of the Motorola development you see regarding phone with lockd bootloaders are really nothing more than a bunch of stock and AOSP apps and system files that change the look and the startup sequence but the base code that runs the phone pretty much stays the same!
I would love to see more people making ROMs for the unit but what I really want to see is the unlocking of that boot loader.
If we managed to do that then none of us would be worrying how many roms were available or which one updates next.
We would probably all be running Cyanogen at this point and merely wait for the next release of stable! And also be looking for the next great Kernel update to make it even better!
Asphyx said:
Most of the correct answers were already stated...
Just wated to point out that only people who truly needed global support would buy the D2G.
Droid Pro got play merely because it was targeted at the Crackberry crowd conversion which really didn't work.
Those are the only two GLOBAL phone I know of. Doesn't make sense to make many more with the 4G revolution under way.
Business have bought into the form factor but the Devs they all look at the performance specs and the EASE of development regarding the model.
The biggest issue though is the locked bootloader! Since the boot loader is locked you can not run custom Kernels so any development that could be made is limited to the stock kernel.
All of the Motorola development you see regarding phone with lockd bootloaders are really nothing more than a bunch of stock and AOSP apps and system files that change the look and the startup sequence but the base code that runs the phone pretty much stays the same!
I would love to see more people making ROMs for the unit but what I really want to see is the unlocking of that boot loader.
If we managed to do that then none of us would be worrying how many roms were available or which one updates next.
We would probably all be running Cyanogen at this point and merely wait for the next release of stable! And also be looking for the next great Kernel update to make it even better!
Click to expand...
Click to collapse
Won't anyone who wants a keyboard on verizon also get the D2G? I mean it's the only half decent phone with a physical qwerty keyboard on verizon, and the droid 2 itself was phased out months ago, 4 months ago when I got my D2G you couldn't get a new Droid 2 at verizon, though I think Best Buy might have still had them, though they were just clearing out stock.
Also I thought fact that everything has to be signed is the problem with the phone. When you don't know how to sign the kernel and other things the phone has hardware to autobrick which is why no one can get around it. Tons of phones out there have locked bootloaders that are gotten around well before or within a few days of the phone being released. If it was just the locked bootloader then I'd say motorola has found the holy grail of security, because everything else out there has been hacked through.
The problem isn't that the bootloader is signed, its that its encrypted. Newer htc phones have bootloaders that require signed kernels and people have found ways around them already, the encryption prevents us from loading custom software on it.
Sent from my DROID2 GLOBAL using XDA App

(Q)ICS rom

In theory wouldn't we be able to take an ics Rom from the prime, get drivers working for our tegra to achieve hardware acceleration? Not completely sure of the differences between both devices other than the processor.
Sent from my PC36100 using Tapatalk
It would take time in order for developers to translate the drivers.
Put it this way. It would be quicker, and easier, to wait even a month for the TF101 to receive ICS rather than trying to translate from the Prime to the TF101.
Rumor mill has it that the TF101 will be receiving ICS at the end of the month.
I heard a rumor about an ICS rom already out there on the web, but that's just a rumor. You have to ask yourself if it's worth it to risk your tablet's life or just wait a month. Don't do like me...
Fellas, they're already working on porting the Motorola xoom's ICS over to the TF101 as we speak. Working out a few bugs now, could possibly be here before the official ICS build if noobs will quit asking them how to flash the unfinished product and other development-unrelated questions (in other words, have a peek, but don't bug the big guys at work )
BTW TF201 has the Tegra 3, while Xoom has a tegra 2..much easier to port from what I understand..so don't hold your breath on the Prime's ICS coming to roost on your OG TF any time soon..
I saw something from Asus that said we won't be getting it until February. I'll be looking forward to the Xoom port!
brando56894 said:
I saw something from Asus that said we won't be getting it until February. I'll be looking forward to the Xoom port!
Click to expand...
Click to collapse
I personnally think it's stupid to take risks to get what you can get in one month, in a more adapted way. Who knows! Maybe you'll end up bricking your device...
Xoom has most of the same hardware....so they're just taking the items that aren't for our device and replacing them with proper drivers.
Sent from my PC36100 using Tapatalk
Horclok said:
I personnally think it's stupid to take risks to get what you can get in one month, in a more adapted way. Who knows! Maybe you'll end up bricking your device...
Click to expand...
Click to collapse
For one, it isn't a risk once the devs have gotten it right to flash if you know what you are doing, there will have been 100 people who flashed the ROM repeatedly while testing before you ever gt your hands on it.
Second point- the official ICS update will almost surely take some time to Root, if your device wasn't rooted before the update, and no such problem will exist with a dev ICS ROM since it will be rooted in the source.
Final point- ICS is ICS, if the hardware works, and software functions, there isn't much difference between the official build and a ported build, except for the ported build is at the mercy of the devs to put whatever goodies and extras the official ICS build didn't include..
ICS official = wait and get stuck without root
ICS dev ROM = be here soon and have root + extras.
Which one do you prefer now?
Horclok said:
I personnally think it's stupid to take risks to get what you can get in one month, in a more adapted way. Who knows! Maybe you'll end up bricking your device...
Click to expand...
Click to collapse
Outside of proprietary hardware drivers, I have yet to see an OEM ROM exceed performance of a community ROM. OEMs have nowhere near the amount of people working on their ROMs as a community version, and nowhere near the amount of eyes checking for bugs.
Cheers!
-M
Xda member since 2007
luna_c666 said:
For one, it isn't a risk once the devs have gotten it right to flash if you know what you are doing, there will have been 100 people who flashed the ROM repeatedly while testing before you ever gt your hands on it.
Click to expand...
Click to collapse
There is always a risk when you flash a rom, always. Now I had your opinion before I bricked my device, and I knew what I was doing. Then again, you have to choose between security and variety.
dragon_76 said:
Outside of proprietary hardware drivers, I have yet to see an OEM ROM exceed performance of a community ROM. OEMs have nowhere near the amount of people working on their ROMs as a community version, and nowhere near the amount of eyes checking for bugs.
Click to expand...
Click to collapse
This is so true. Even if the OTA ICS update were to be released, I would still wait for a Dev to mess around with it before I updated. Call me crazy, but I'm not a fan of OEM skins and their performance is always lacking.
Horclok said:
There is always a risk when you flash a rom, always. Now I had your opinion before I bricked my device, and I knew what I was doing. Then again, you have to choose between security and variety.
Click to expand...
Click to collapse
How did you get a brick? Flash failed halfway through or something? I've probably flashed 100 ROMs, from xbox to android, the only device I ever bricked was a windows phone, and its just soft bricked now. I didn't know what I was doing with that thing...I've had plenty of close calls don't get me wrong, heck I lifted up a trace on my xbox motherboard and had to repair it on the spot with solder within 10 minutes or the clock-capacitor would have discharged forcing me into clock-loops (death for an xbox)..'know what you're doing' has very different levels of complexity
There is always a risk, to be sure, I should have worded myself better. But the same amount of risk as any ROM, not specific to this one..I've never heard of an OTA update failing and bricking a device, but I'm sure it can happen as well..anytime you are flashing onboard firmware there's always a chance something can go wrong. I was just saying that a Dev rom will have been flashed and booted and reflashed 100 or 1000 times by the devs during the build process before any of us 'outsiders' gets a taste of it. In my opinion, that's about as risk-free as it gets with modding these things..and in the end, who is going to upgrade to ICS without wanting it rooted? At least, who on this site?
I feel much more confident loading an already rooted ICS rom from the community than I do flashing the OTA update and wondering if I'm going to lose root/recovery etc. It is a personal opinion though..
luna_c666 said:
I feel much more confident loading an already rooted ICS rom from the community than I do flashing the OTA update and wondering if I'm going to lose root/recovery etc. It is a personal opinion though..
Click to expand...
Click to collapse
This.
OEM updates of any kind are more known for borking a system than a community version and again, it is because there are many more eyes on a community version. OEM versions are seen as a necessary evil for them. The life cycle of the product is usually over or already over and they do not want to devote any resources to an endeavour that now only costs money instead of makes money.
Asus may be a little different with the TF101 because they still are selling a fair amount of them. Best Buy still keeps restocking the 16GB version and with the TF201 problems they may push the TF101 as a sort of "budget premium" since ICS completely re-invigorates older hardware (my Atrix is running an alpha build without OC and GPU accel and it is just as smooth as full GPU and OC).
I still plan on waiting for Gnufabio's ICS Revolver release.
Cheers!
-M
Xda member since 2007
dragon_76 said:
I still plan on waiting for Gnufabio's ICS Revolver release.7
Click to expand...
Click to collapse
I just tingled at the thought.
ICS does breathe a lot of new life in to old hardware. My old Incredible runs it fairly smoothly, just laggs a bit on transitions. But it did make me more interested in my old phone.

Seriously, why is our phone so neglected?

Honestly, the A2 has great performance, it is not top of the line, but it is certainly pretty high end. It has a decent feel overall, but still know one knows about it. Why is this?!!? I'm not even talking strictly from a development standpoint, as it is just so unheard of. everyone knows about the whole droid line and such, but our great phone is completely neglected. There is no way i'm the only one that is bothered by this, especially because there is so much potential in our phone. I know the locked bootloader, makes things difficult, but a way around that is near, so do y'all think development will take off once we get it bypassed or unlocked? Thanks for listening to my rant and feel free to give your own opinion
Motorola or Att did not push this phone like they did with the original Atrix. Most people are going with samsung (sgs2 or the note). That is why we do not have very many devs. Samsung phone are much easier to work with. I know because i have one. If no one else decides to get this phone that's fine with me. I like the phone as is. Im also happy with the few devs we have. Their work is greatly appreciated.
Sent from my MB865 using xda premium
Once cm9 or a form of ics gets calling and texting going then things will start to kick off. Right now with our limited amount of knowledgeable devs some have lost interest and are just sitting by waiting for Motorola to release ics.
Sent from my I9300 using XDA
you aren't the only one. It pisses me off. I always have service on this phone, for the most part it's fast and smooth, and the ROM support is becoming awesome. Yet still people don't know the name of my phone , they just know it's "big"
tsdeaton said:
Once cm9 or a form of ics gets calling and texting going then things will start to kick off. Right now with our limited amount of knowledgeable devs some have lost interest and are just sitting by waiting for Motorola to release ics.
Sent from my I9300 using XDA
Click to expand...
Click to collapse
Actually, one of the orignal devs for this phone (been on it since it came out) has not lost interest but is working on kexec for our phone which is BY FAR more important than ICS... The possibilities are endless once we have a bootloader bypass.
Motorola did not advertise or really let ANYONE know that the phone was being released. For example, when I walked into the AT&T store with a $100 and a contract renewal, I just browsed/tried all of the phones they had in stock, and happend to like the feature set/performance of the Atrix 2 the best. The funny part is that I had NO idea that the phone actually came out the day before and was just put on display. Luckily the phone is great and the community to go along with it is even greater.
Honestly I'm on Supercharged right now, clocked around 1.25 GHz, and I can go higher, but my battery life sucks. I don't really care about the attention. We're getting ICS, and I'm hoping I don't have a good enough excuse to go back to stock until ICS is out. Then I'm going back to stock for sure. The speed is great, the lagginess and bloat on the stock rom just sucked, but so does my battery life now. It doesn't really take a whole lot to trim down a stock rom, I'm sure someone will do it for ICS if I don't myself.
Douchewithaphone said:
Honestly I'm on Supercharged right now, clocked around 1.25 GHz, and I can go higher, but my battery life sucks. I don't really care about the attention. We're getting ICS, and I'm hoping I don't have a good enough excuse to go back to stock until ICS is out. Then I'm going back to stock for sure. The speed is great, the lagginess and bloat on the stock rom just sucked, but so does my battery life now. It doesn't really take a whole lot to trim down a stock rom, I'm sure someone will do it for ICS if I don't myself.
Click to expand...
Click to collapse
Freezing apps does wonders for performance + battery life. I use Titanium Backup for this. All the "junk apps" that Motorola/AT&T installed (that I don't use) get frozen.
The End.
Some of our roms are great, but there are only 4 or 5 or something, it would be nice to see some of the big ones like cm7. hopefully an unlocked BL and ICS will spark some serious development. I think the biggest problem is the lack of serious developers. Who do we really have? Jimbridgman, lfabor06, and Rdavisct are the only ones I can really think of off the top of my head. We all play a role, but only the true genius' like them do a lot of good towards roms and things
To buy an Atrix 2, I had to special order it from Amazon. The local places didn't sell it because it didn't work with LTE in the area, and were mainly pushing iStuff.
Motorola needs to wake up and start tooting their own horn. The Atrix 2 has been an excellent phone, both in the reception department (better voice and call quality than my HTC and iPhone), CPU department, and in general usage.
Plus, there is an untapped market for these types of phones -- business people who just need a basic laptop where all their data is stored securely at one place, either on the phone with the on device encryption (or SD encryption), or using a Citrix receiver.
farshad525hou said:
Actually, one of the orignal devs for this phone (been on it since it came out) has not lost interest but is working on kexec for our phone which is BY FAR more important than ICS... The possibilities are endless once we have a bootloader bypass.
Click to expand...
Click to collapse
This really is the truth of the matter. Until we can load custom kernels on the A2, the devs are kinda limited on what they can modify. ICS with a locked bootloader is not much better than GB with a locked bootloader.
My wife has a Samsung Galaxy and the A2 is better in almost every area; reception, interface, speaker...

AOSP on Galaxy Tab 3 10.1

So, i opened this therad because there no persons pushing and Developing custom AOSP Roms for the Galaxy Tab 3.
I'm opening it here because the Android Developing forum is a bit AFK.
Also, my first question is,
Why we are not using the Android x86 source, put a little bit from samsung open source and Tab 3 binaries it, and compile it?
Its so hard?
We are the xda-developers, we can do it!
Curious..
superboom said:
Also, my first question is,
Why we are not using the Android x86 source, put a little bit from samsung open source and Tab 3 binaries it, and compile it?
Its so hard?
We are the xda-developers, we can do it!
Click to expand...
Click to collapse
Yes, I'm asking myself the same, the Galaxy Tab 3 is such a famous device and out since July, but still there are nearly no ROMs out. Are there any ROMs planned or will this device soon be moved to the low activity section? CyanogenMod officially supported the Galaxy tab and the galaxy tab 2, but it doesn't seem like they are planning to support the galaxy tab 3?
Is there a special reason for that?, I'm just wondering?
chaoskoch said:
Yes, I'm asking myself the same, the Galaxy Tab 3 is such a famous device and out since July, but still there are nearly no ROMs out. Are there any ROMs planned or will this device soon be moved to the low activity section? CyanogenMod officially supported the Galaxy tab and the galaxy tab 2, but it doesn't seem like they are planning to support the galaxy tab 3?
Is there a special reason for that?, I'm just wondering?
Click to expand...
Click to collapse
you know why we need developers who want to put some time in this device and at the moment we don't have much dev's around here so wait...
Willing to get my hands dirty...
safariking said:
you know why we need developers who want to put some time in this device and at the moment we don't have much dev's around here so wait...
Click to expand...
Click to collapse
The most device development I've done to date has been a simple android app, but I'm willing to get dirty on this one. I just came into possession of one of these devices over xmas, and I never let a good device go to waste. I do have 17 years of programming experience in multiple languages including C++ and Java, and a lot of web-based languages, so I'm hoping to come up to speed relatively quickly.
I'll poke around here and on the net over the next few days and see if I can teach myself, but if someone could point me in the direction of some quick start tutorials for building custom roms, I'll get started.
ush
AnthonyAlmighty said:
The most device development I've done to date has been a simple android app, but I'm willing to get dirty on this one. I just came into possession of one of these devices over xmas, and I never let a good device go to waste. I do have 17 years of programming experience in multiple languages including C++ and Java, and a lot of web-based languages, so I'm hoping to come up to speed relatively quickly.
I'll poke around here and on the net over the next few days and see if I can teach myself, but if someone could point me in the direction of some quick start tutorials for building custom roms, I'll get started.
Click to expand...
Click to collapse
Anthony, I think one thing that is holding people back on this device is a good recovery. The ones available now are painfully slow. I'm guessing there is some power saving mode on the x86 chip that needs to be tweaked to get it performing well. Once that was fixed, it would be a lot easier to experiment with ROMs. -- Bud
Also Interested
Anthony and all, hi and hello. Thinking of shaking the rust off, as I also just came into possession of a GTab3, 10.1 inch, over this holiday season. I haven't built anything in a long time, but anyone who ran a Vibrant a couple years ago around here, should recognize my handle. I maintained a rom for the Vibrant for quite a while, from Froyo to ICS, then life got busy.
Popping into here today, I'm kinda sad to see there's not much if any in the way of development on this device. Happy to have root, thats a start. cduced was right, we do need a better recovery option, at least one that is faster, though what we have now is workable. TWRP may be slow, but it's something. We were always hung up on doing pure aosp source build for the Vibrant, because Sammy is not known for making their kernel source easily and readily available. Working from an existing zip to kang it is easy, but really thats just the same rom, maybe stripped and repackaged. A source build is the desirable outcome.
Though I haven't begun looking into things for this baby yet, and my adb and build tools are far out of date, I am very interested in working towards a better set of options for this device. 4.2.2 still? I can't believe Sammy hasn't released a 4.3 update, that's sad, but goes to show the lack of support they give their devices, to anyone who's been there you know, but you also know, determined devs can make it a better world.
Anthony, and anyone else interested in trying to improve this device, feel free to PM me, I'm thinkin' we should make a Google Hangout or something, make it easier to communicate.
Br1cK'd said:
Anthony and all, hi and hello. Thinking of shaking the rust off, as I also just came into possession of a GTab3, 10.1 inch, over this holiday season. I haven't built anything in a long time, but anyone who ran a Vibrant a couple years ago around here, should recognize my handle. I maintained a rom for the Vibrant for quite a while, from Froyo to ICS, then life got busy.
Popping into here today, I'm kinda sad to see there's not much if any in the way of development on this device. Happy to have root, thats a start. cduced was right, we do need a better recovery option, at least one that is faster, though what we have now is workable. TWRP may be slow, but it's something. We were always hung up on doing pure aosp source build for the Vibrant, because Sammy is not known for making their kernel source easily and readily available. Working from an existing zip to kang it is easy, but really thats just the same rom, maybe stripped and repackaged. A source build is the desirable outcome.
Though I haven't begun looking into things for this baby yet, and my adb and build tools are far out of date, I am very interested in working towards a better set of options for this device. 4.2.2 still? I can't believe Sammy hasn't released a 4.3 update, that's sad, but goes to show the lack of support they give their devices, to anyone who's been there you know, but you also know, determined devs can make it a better world.
Anthony, and anyone else interested in trying to improve this device, feel free to PM me, I'm thinkin' we should make a Google Hangout or something, make it easier to communicate.
Click to expand...
Click to collapse
Hey I want aosp on this device too! At the very least, id like a custom kernel that I can overclock to reduce lag. Ive never created a rom, but I dont think roms are the issue...id be interested in porting roms that already exists...x-note for multiwindow features, or pac-rom for a highly customized device.
Are you still up for the projects? Lets heat these forums up!!!
Ideas4ya said:
Hey I want aosp on this device too! At the very least, id like a custom kernel that I can overclock to reduce lag. Ive never created a rom, but I dont think roms are the issue...id be interested in porting roms that already exists...x-note for multiwindow features, or pac-rom for a highly customized device.
Are you still up for the projects? Lets heat these forums up!!!
Click to expand...
Click to collapse
Thanks guys for give it a try, I'm like the other owner don't understand why there is no interest for this devise didn't check before buy and now start to regret
Meteore said:
Thanks guys for give it a try, I'm like the other owner don't understand why there is no interest for this devise didn't check before buy and now start to regret
Click to expand...
Click to collapse
There are some devs now they just relesed 2 but there tw based there trying it just takes awile because of lack of devs.
mylifeandroid said:
There are some devs now they just relesed 2 but there tw based there trying it just takes awile because of lack of devs.
Click to expand...
Click to collapse
It's ok I have already seen and tried them :laugh:. I understand the concept of work on something new and the lack of dev it's just that I was surprised because I thought tab 3 was like the others tabs so the development was more evolve.no problem.
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Br1cK'd said:
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Click to expand...
Click to collapse
This is true but there is finally a bit of interest and may come up with some new goodies..... the reason they all have the same updater.script is because of the recoveries.... they need a little more work to get them to work with the x86 architecture
Sent from my GT-P5210 using xda app-developers app
Br1cK'd said:
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Click to expand...
Click to collapse
Hey PM me with any test builds of the kernels please.
Sent from my GT-P5210 using XDA Premium 4 mobile app
I think someone has to pm restl3ss!
http://forum.xda-developers.com/showpost.php?p=49126542&postcount=90
Let's see what can we do here!
Calcu said:
I think someone has to pm restl3ss!
http://forum.xda-developers.com/showpost.php?p=49126542&postcount=90
Let's see what can we do here!
Click to expand...
Click to collapse
Dont understand your post.... the link goes to one of his posts
Sent from my GT-P5210 using xda app-developers app
Because in this post (if i'm not wrong) he tells that is making a recovery with 4 guys more.
something needed here xD.
Enviado desde mi Note 2
Calcu said:
Because in this post (if i'm not wrong) he tells that is making a recovery with 4 guys more.
something needed here xD.
Enviado desde mi Note 2
Click to expand...
Click to collapse
Lol.... I see yeah... I am also in the process of building recovery but its a long time coming. Right now im reading a lot of material on how to build from source as that the route of the prob. Its this damb x86 architecture
Sent from my GT-P5210 using xda app-developers app
Maybe.... we can port something from here
http://www.engadget.com/2014/01/06/micromax/
Enviado desde mi Note 2
Push
If anyone have time, pm me and we can discuss about. I'm not a developer, but we can discuss ideas how to bring cm to the device

Vanilla ROMS?

I was thinking about getting an ATT LG G3 and was looking around , but do not see any Vanilla android roms.
Do they exist?
Do you think there will be a Lollipop rom that can be flashed to this device?
Thanks
Sent from my Lenovo U310 using Tapatalk
No and yes. Once the official or leaked android 5.0 drops for either the international g3 or att g3 our devs will pump something out.
Sent from my LG-D850 using XDA Premium HD app
There are aosp roms available. It's just that a few things don't work at the moment (camera has been fixed recently but bluetooth still doesnt work).
The problem is the aosp roms are tethered, meaning you need a pc and adb to boot the rom. As soon as the bump devs release the necessary tools, rom devs will be able to "bump" the kernel and have it ready for flashing. By then you'll be able to download and flash normally.
I think the biggest reason why we don't see more custom ROMs is the fact that the Bump team still has not provided a website or other method for developers to "bump" their work. These guys do this in their spare time (ie they aren't working on this 9-5, 5 days a week). Apparently they are struggling to get their website up and running as it has become a magnet for hacking attempts. Hopefully they will be able to get it all sorted out soon!
Once there is a bump method released to developers, they will be able to really concentrate on the G3 and I think you will see a lot of work released soon after.
sic0048 said:
I think the biggest reason why we don't see more custom ROMs is the fact that the Bump team still has not provided a website or other method for developers to "bump" their work. These guys do this in their spare time (ie they aren't working on this 9-5, 5 days a week). Apparently they are struggling to get their website up and running as it has become a magnet for hacking attempts. Hopefully they will be able to get it all sorted out soon!
Once there is a bump method released to developers, they will be able to really concentrate on the G3 and I think you will see a lot of work released soon after.
Click to expand...
Click to collapse
I ask this out of ignorance and not impatience in any way, but. . . . Why is the site such a rich target for hacking?
czucker said:
I ask this out of ignorance and not impatience in any way, but. . . . Why is the site such a rich target for hacking?
Click to expand...
Click to collapse
Because they found an exploit in the LG bootloader so it basically paints a target on their back? Those same devs have had other successes with rooting other phones and what not. They are in my opinion very popular in the Phone community from their accomplishments. I think this alone makes them a target which is ridiculous. Whether it be jealousy or someone trying to make a name for themself or better yet a foreign country being mad that Americans cracked the code who knows. Actually I don't exactly know why they are being targeted lol. I am just taking guesses. I am sure their is even a possibility that Team Codefire doesn't know. Either ways its a shame that it is happening but it will all get sorted out.
Wish d850 could at least get a tethered aosp ROM
I bet we see some by next week. The tree is out. Should be good to go soon. I bet this thing is a BEAST when its running something slim.
Sent from my LG-D850 using XDA Free mobile app

Categories

Resources