Related
I see a few GT-N8000 options, but no love for us US Wi-Fi Only (N8013) users.... Hopefully that will change soon
ej_424 said:
I see a few GT-N8000 options, but no love for us US Wi-Fi Only (N8013) users.... Hopefully that will change soon
Click to expand...
Click to collapse
The device launched LAST THURSDAY...
Competent developers take time to test and polish their stuff, they don't just throw random crap out into the wild to claim "first".
The only reason the N8000 is ahead right now is because it had about a week headstart in availability.
I can tell you at least two Cyanogenmod device maintainers have purchased or have Note 10.1s on order - Myself (N8013 in my possession) and Espenfjo (N8000 on order), also I think chris41g and at least one other member of the CM team have N8013s.
Same for the Euro N8010 Wifi only version. No dev either...
Entropy512 said:
The device launched LAST THURSDAY...
Competent developers take time to test and polish their stuff, they don't just throw random crap out into the wild to claim "first".
The only reason the N8000 is ahead right now is because it had about a week headstart in availability.
I can tell you at least two Cyanogenmod device maintainers have purchased or have Note 10.1s on order - Myself (N8013 in my possession) and Espenfjo (N8000 on order), also I think chris41g and at least one other member of the CM team have N8013s.
Click to expand...
Click to collapse
Understood and makes sense (wasn't aware they had the headstart). Glad to hear you have a 8013 as I've seen alot of good work from you in the past for current and previously owned devices. One quick question... maybe its too early to say, but do you see porting the S-Pen apps and functionality to CM 10 even as an option? Maybe its not even possible....
Thanks again!
I'm so looking forward to the boost CM will give to this tablet judging from my experience with CM9 giving new life to my old Galaxy S Epic 4G.
This device should be quite popular with Developers due to the s-pen. I am betting we have roms galore in about 30 days,
We have root already at http://forum.xda-developers.com/showthread.php?t=1831152.
It just released, give it time.
ej_424 said:
Understood and makes sense (wasn't aware they had the headstart). Glad to hear you have a 8013 as I've seen alot of good work from you in the past for current and previously owned devices. One quick question... maybe its too early to say, but do you see porting the S-Pen apps and functionality to CM 10 even as an option? Maybe its not even possible....
Thanks again!
Click to expand...
Click to collapse
Apps with the S-Pen SDK - No.
Apps that use the standard ICS Pen APIs - Yes - these are becoming more and more common. PS Touch may even be in this category, I won't know until I've tried. I had a bunch of N7000/I777 stuff to do this past weekend so didn't even start on CM10 bringup.
Built-in features such as stylus gestures and an included note-taking app - There was work started on this, the Note 10.1 will make it more important to get this stuff finished. Google dropping JB kind of put a hold on the "new CM features" stuff as we tried to un-break all the old ones.
Might I just say, it is [email protected] good to see you here, Entropy.
Sent from my SAMSUNG-SGH-I747 using xda premium
One thing, as far as CM on the N80xx:
I probably could have had CM booting and mostly working with only a few hours of work. However, there's the "quick way" and there's the "right way". The "quick way" would've gotten my N8013 working without providing any benefit for N8000, and without leveraging I9300 commonality. The "right way" takes quite a bit more time - but leverages commonality with the I9300. I'm REALLY hoping we can use the same smdk4412 kernel source tree as the I9300 with just some patches, as it makes maintenance MUCH easier, but could take some time to initially pull in all the right patches.
Similarly, getting an N8013 device tree would've been easy. Having a "common" tree takes more time but means all N80xx devices will pretty much all be maintained to the same degree. See P51xx/P31xx...
Think I saw viperboy lurking in the forum
Sent from my SPH-L710 using xda premium
Seeing alot of well known Dev's.. This is great and very encouraging. The hardware on this device is awsome, only complan and minor one at that is the screen resolution. In all honesty though it really doesnt bother me much as there ins't much jaggy endges.
As is usual - Whenever Samsung releases a new device (or even a major upgrade to an old device - See I9100 ICS cpufreq derpage which took multiple kernel developers 2-3 weeks to figure out), there's some really derped-up **** in the source.
Right now, any source-built kernel has massive issues with wifi - The SDIO interface just seems to shut down and the chip drops off the face of the earth. This does not happen in the stock kernel.
This one's gonna be a pain in the ass to figure out.
See attached dmesg for an example of the fun...
ilostmypistons said:
Think I saw viperboy lurking in the forum
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Heh, but I promise you I'm nowhere near as good as the CM guys are. Once I get my tablet, I might do a stock ROM with some tweaks but it won't be anything insane.
Sent from my EVO using Tapatalk 2
-viperboy- said:
Heh, but I promise you I'm nowhere near as good as the CM guys are. Once I get my tablet, I might do a stock ROM with some tweaks but it won't be anything insane.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
So modest
Sent from my SPH-L710 using xda premium
ilostmypistons said:
So modest
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Lol viperboy has no cause for modesty
We look forward to his always excellent work.
I wonder what this will overclock to when they have the kernel figured out?
Sent from my awesome Note 10.1
model name doubt
HI my note 10.1 is the shw-m480w is the wifi version bough tin korea
how does translates to the other code names so i can flash a custom rom?
Thx in adv
This is the unofficial thread to find the list of developers for the Samsung Galaxy Note II.
If you are a developer and or ROM maker/cooker would like to confirm that you are going to dev on this device please send me a pm, and I will add you to the list. In past experiences these types of threads have shown to be very helpful to build dev support for a device, and also to help people decide on a device.
What, actually is the list for?
Basically its for people and devs to see all the dev support the device will have. This sometimes is the deciding factor for getting a phone. If there's huge dev support more people will come. This makes it easier for people to find information on what devs will be supporting the note 2.
To pm me and get added to the list Click Here.
Let's make this Galaxy Note II community awesome!
Confirmed Developers
1.Utacka
2.thering1975
3.DakiX
4.::indie::
5.m3dd0g
6.Crash 1976
7.g.lewarne
8.toxicthunder
9.awesomehacker
10.KashaMalaga
11.-Viperboy-
12.lennyuk
13.Dexter_nlb
14.DocRambone
15.imilka
16.f3w1n
17.kristofpetho
18.mike1986.
19.Stavr0s91i
20.wanam
21.xator91
22.Beukhof1
23.ptmr3
24.Anas M.I
25.cpu999
26.AndreiLux
27.Chainfire
28.Patrics83
29.Chenglu
30.bigbiff
Hi,
Thanks for starting this thread. I just want to ask "Do you think there be a lot of development for this phone?" Particularly for Note II, in general for future Samsung phones.
I just finished watching this video here or here and I just heard about some developers leaving Samsung altogether? Samsung locking bootloaders? Samsung getting too big for their own ego?
I currently own the Int'l N7000 and I found the development to be good for what I want. I didn't check out the i717 thread but I assume they are fair.
I'm not really experienced in rooting but I found Samsung Note to be fairly straight forward. I recently rooted an HTC Amaze 4G and the numerous steps plus the lack of info made me never to buy an HTC phone (even if I do like the HTC One X, my friend has the North American version and he said development is low there).
This is one reason why I'm holding out on the Note II until Feb 2013, maybe even Sept 2013 (in case Note 3) comes out because I want to see how the development plays out.
I know the phone just came out, but I assumed International Note development should be all hunky dory but I never know. Makes me not want to switch devices. I had an Int'l Galaxy S2 previously and development for that is great!
I hear Sony development is awesome. But then, I think I'll just go get a Nexus for ease of development (but the screen is so small!)
What do you guys think?
cincyelite22 said:
Confirmed Developers
1.Utacka
2.thering1975
3.DakiX
4.::indie::
5........
Click to expand...
Click to collapse
thanks leafsacc, I wasn't aware of this until now. I'm still not sure what's going on but I assumed there would be a way around a bootloader, as coders always find a way :highfive:
but reading the below, says it could have been verizon which was the cause of the bootloader, not samsung. so why is xdadevtv directing his video to samsung? is it because no open source was given for the s3? has it still not been released? will it be? anyone care to sum it up for some of us who aren't in the know? :>
Based on Samsung’s track record of always shipping devices with unlocked bootloaders, we can all safely deduce that Verizon is the one to blame here.
Click to expand...
Click to collapse
http://www.xda-developers.com/android/verizon-samsung-galaxy-s-iii-unlocked/
For starters cm will not support n7100 if samsung dont change their ways. atleast the current dev team in cm will not support newer samsung exynos devices. i9300/n80xx was the last. Only way to get n7100 supported is if samsung cooperate or a new dev join cm dev team.
Without cm support i cannot do my paranoidandroid from source as I do with n7000. Time will tell if some new dev join cm samsung team or samsung get their act together. Dont look good though.
Skickat från min GT-N7100 via Tapatalk 2
Utacka said:
For starters cm will not support n7100 if samsung dont change their ways. atleast the current dev team in cm will not support newer samsung exynos devices. i9300/n80xx was the last. Only way to get n7100 supported is if samsung cooperate or a new dev join cm dev team.
Without cm support i cannot do my paranoidandroid from source as I do with n7000. Time will tell if some new dev join cm samsung team or samsung get their act together. Dont look good though.
Skickat från min GT-N7100 via Tapatalk 2
Click to expand...
Click to collapse
Whoops not good news :crying: i need also sources...
Well I don't get it because it is sharing most of the hardware with S3 so the stuff should be at least ported easily.
Now I understand Samsung being a complete ass with their proprietary drivers
Sent from my GT-N7100 using xda premium
jbounours said:
Well I don't get it because it is sharing most of the hardware with S3 so the stuff should be at least ported easily.
Now I understand Samsung being a complete ass with their proprietary drivers
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
You still need one of the dev maintaining exynos devices to buy n7100 and then maintaining it... we can hope for someone to step up but its their freetime and money. Entropy512 told me he would be buying at&t version which is nearly identical if samsung would change their behavior. All we can do for now is to sit and wait...
Skickat från min GT-N7100 via Tapatalk 2
Hi guys, my ROM is finally finished and now uploaded at 89%.
I need a tester! My Note 2 has not arrived yet
Please write via PM.
You forgot chainfire..
Sent from my HTC One X using Tapatalk 2
This is a great thread. I hope more chefs will chime in.
I am considering a Note II but it is absolutely vital that CM is developed for it, together with Paranoid Android. Especially since Key Lime Pie (CM11?) is be around the corner.
I also think it is important with AOSP/AOKP development for it.
So I hope the issue will be sorted during this month. If not, I am afraid that I have to consider a different game plan.
Buying a device without proper developer support is a no go for me.
For everyone woundering about my sources here is a statement from Entropy512:
Entropy512 said:
Not likely to happen. If CM comes to the Note 2, it will only be if a new maintainer steps up.
Most of the current Exynos maintainer team (myself, espenfjo, codeworkx) and others have all decided that our current devices will be our last non-Nexus Exynos devices. I'm not sure about xplodwild, but I have a feeling he's highly unlikely to take up another Haxxinos with the rest of us gone and given his prior experiences with it.
If Samsung changes their attitude towards developers, this might change, but their attitude lately (zero documentation, zero platform source code, a trend towards bootloader locking - Only the Verizon S3 has a locked bootloader now, but Samsung has had the infrastructure in place since the S2 and they are constantly adding more checks) has led to the current Exynos maintainer team deciding that enough is enough. I don't think any of us are going to do anything to make Samsung's Exynos devices more attractive to any particular market segment until they provide assistance (in the form of technical documentation and source code) in return. I don't know about the others, but if they offer me a free device I'll say no - I refuse to participate in a PR stunt like the I9100 donations were.
Pretty much the only way I'll go back is if I see reference platform source that is up to the same standards as CAF and omapzoom, or they actually start providing real documentation and source code for the devices I'm currently working with.
Click to expand...
Click to collapse
Skickat från min GT-N7100 via Tapatalk 2
Thanks entwicklun,
I Googled "verizon locked bootloader samsung galaxy note" and from what I understand that it was Verizon's request to lock the bootloader. Not sure what I would do if I was Samsung but my guess is, if it helps sell more phones on Verizon then lock the boot loader. Money talks, right?
But then I'm hearing news about Samsung not giving developers this and that, just like the example below.
jbounours said:
Well I don't get it because it is sharing most of the hardware with S3 so the stuff should be at least ported easily.
Now I understand Samsung being a complete ass with their proprietary drivers
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
And I also need a phone that will have Paranoid Android (and the odd CM here and there), but it must also a 5" phablet. I guess there is nothing wrong with my current Note, but again by searching on Google there's a possibility that the "next big thing" might be the HTC Google Nexus X+. If that has an expansion card slot, that's it, I'm not getting the Note 2.
E90 Commie said:
This is a great thread. I hope more chefs will chime in.
I am considering a Note II but it is absolutely vital that CM is developed for it, together with Paranoid Android. Especially since Key Lime Pie (CM11?) is be around the corner.
I also think it is important with AOSP/AOKP development for it.
So I hope the issue will be sorted during this month. If not, I am afraid that I have to consider a different game plan.
Buying a device without proper developer support is a no go for me.
Click to expand...
Click to collapse
Thanks for all the work the dev's put in. I'm just saying, my next phone is where the developers are. Samsung doesn't own us. :laugh:
I'll be here when I get my note2 in December
For those that don't know, TW ROM, aokp and multi booting kernel (or at least 2 sesperate kernels )
Myself and utaka could probably come up with a aosp supporting kernel for the device if official CM does not materialise.
Crash Rom will be here to
Sent from my GT-N7000 using Tapatalk 2
cheers, I'm sure those browsing like me will know what's up now.
I've already ordered my note 2, but I would fully support the dev crew. even if that means selling my note 2 at a loss and buying what's being developed, pending though. I do like phablets and if the x+ doesn't have an exspansion slot then I probably wouldn't buy it.
I also hope aokp devs on the note 2. I certainly love their ROMS
leafsacc said:
Samsung getting too big for their own ego?
I currently own the Int'l N7000 and I found the development to be good for what I want. But then, I think I'll just go get a Nexus for ease of development (but the screen is so small!)
Click to expand...
Click to collapse
+ 1
g.lewarne said:
I'll be here when I get my note2 in December
For those that don't know, TW ROM, aokp and multi booting kernel (or at least 2 sesperate kernels )
Myself and utaka could probably come up with a aosp supporting kernel for the device if official CM does not materialise.
Click to expand...
Click to collapse
Are noobs like me allowed to jump in please?
Utacka sir is so kind to us all in his PA thread
Anyways, I think devving for this device would initially start with kanged TW based ROMs. With CM wary on supporting the device, it does seem a bit dark but hey, I am sure there are others to step up.
But then again, you can never be too sure.
Sent from my GT-N7000 using xda premium
---------- Post added at 08:55 AM ---------- Previous post was at 08:54 AM ----------
BTW, next nexus device is perhaps open to all OEMs.
Might be an Optimus from LG but from what I've read other manufactures are welcome to jump in and join the party.
Sent from my GT-N7000 using xda premium
I am the same, an expansion card slot is a big plus.
development support is also a big factor.
I would flash aokp right now but i'm so scared of emmc bug (which I assume will not be in the Note 2 just like it did not exist in GB ROM Notes. But who knows if "Key Lime Pie/Kandy Kane" might have a similar brick bug) on ICS kangs that I just stay far, far, away.
My ultimate fav is CassiesXtraLite so it's good to see thering1975 on the list.
entwicklun said:
I do like phablets and if the x+ doesn't have an exspansion slot then I probably wouldn't buy it.
I also hope aokp devs on the note 2. I certainly love their ROMS
Click to expand...
Click to collapse
I might bring VillainRom to the Note2, but only if/when we can get our OTA update/optional mods app up and running to a high enough standard.
Would be nice to know for wich model is going to work each developer.
- f3w1n -
Ok..Sorry to be noobish guys..but i am looking forward to get my hands on a nexus 10 pretty soon, but the "Never" mentioned on the android development thread for nexus 10 made me uneasy.. is it just that the device hasnt lainched yet so its that way or there will never be any development?
I would expect a bit development. Personally I've been waiting since the Nexus 7 launch for this device, and I can't be the only one.
No point in creating a ROM at this point though, no one can even test it. With it being pretty well priced for what you get, I'd be kind of suprised if at least a couple devs don't pick one up.
Patience..
Sent from my HTC One S using Tapatalk 2
doc_fx said:
Ok..Sorry to be noobish guys..but i am looking forward to get my hands on a nexus 10 pretty soon, but the "Never" mentioned on the android development thread for nexus 10 made me uneasy.. is it just that the device hasnt lainched yet so its that way or there will never be any development?
Click to expand...
Click to collapse
The "never" is just a default with this forum software, when there's been nothing posted, the date of the last post is "never". Don't sweat it.
It's a Nexus device with the expectation of full source being released, it's hot hot hot hardware, it's well priced and it will be selling world-wide.
There will tons of development for it, guaranteed.
There will be some super sweet customers roms, always is nothing the Nexus devices.
Me? I'm waiting on ParanoidAndroid.
Sent from my GT-I9300 using Tapatalk 2
Not only with their be amazing ROM development but there will also be custom kernel development. I know Francisco Franco has said he will be developing his kernel for the Nexus 10 and his GNex kernel is amazing. Nexus devices are made for development, they are the easiest to work with and since this is WIFI there's no carrier involvement. Updates are straight from Google the day they are release and they usually update AOSP source just before or in conjunction with the release so custom ROMs will incorporate the changes before or right after the update drops.
Sit back and relax, development will take off Nov. 14th.
Nice to know that..shall have my hands on one soon.!
Sent from my HTC One X using xda premium
bigrushdog said:
Ohai! Here's the deal. I pulled the plug on the Eos project for a few reasons. First, I became unable to maintain the quality of the project while having to deal with countless internal systems issues and doing branch and build maintenance. Second, I didn't have control of the servers and other various resources, like the Goo account. That's why I couldn't get rid of the last two derped builds. Third, I'd rather focus on innovation than dealing with all the internal AOSP build system stuff. As of now, it appears the Eos servers are offline. Which is fine because i have the repository on numerous boxes and right here on my laptop. Finally, I was no longer enjoying Androiding. I NEEDED SOME FRESH ENERGY! Virtually the entire Eos team has already migrated to the new project and got their respective devices up and running! I put about 40 hours a week into Android and I needed to find some guys who have similar time to dedicate to a project. And that team is CodeFireX, lead by Synergy.
A little about Synergy, founder and new combined project team leader. Synergy is a linux guru. He is a master of the aosp build system and talented C programmer. Synergy leads the AOSP scene in innovative new optimization techniques and build solutions. TeamEos has worked closely with Synergy and CodeFireX for a while now. So the decision for us to migrate over to CFX made perfect sense.
When I drop some test builds, you will notice that, indeed, it is a new project, with some new philosophy. There is more CyanogenMod resources in this project. Particularly, some of the CyanogenMod apps including the CMFileManager and Apollo, the CM music player. We are also using the open source Superuser solution from Koush. "Why is this?" "Won't it look like a kang build?" Well, yes. But this project will be the one getting kanged. Like Eos, this project started with a pure AOSP base. I have been surgical in bringing in select desired resources from other teams. Synergy embraces the philosophy of having a solid build without a gapps package installed. In light of recent revelations regarding government surveillance, many people are enjoying Android without the Google Services. We want to provide a build that caters to these wise individuals. And, we feel that the open source CyanogenMod resources are the best. You will "feel" Eos in this build. The Eos spirit lives on in CFX. Always remember, it's not about team names, it's about people.
We now have a wealth of new resources to provide to our users. We have dedicated hosting in which downloading builds will be smoking fast. We have SERIOUS bandwidth. We also have a new forum in which we can provide users with tools that go beyond XDA support. However, I will continue to maintain XDA threads, of course. We have a sophisticated new ChangeLog scheme. And we now use Phabricator instead of Gerrit for project review.
Xoom users face a challenge now. Because of optimization, the build is rather large. Optimization increases the size of libraries and binaries. So, in order to get a successful Xoom build, I have to really "unbloat" the build. This is due to the Xoom having such a small system partition. And that brings us to gapps. Many of you know, CyanogenMod has made the decision to discontinue support on "non-neon" devices. The Xoom is one such device. The reason for this is mostly because Google is discontinuing support of non-neon devices as well. So, for now, I don't have a solid gapps solution. But i'll come up with something, I always do ;D
Test Builds: I should have round 1 up soon. First rounds will be no gapps and meant to simply test core functionality and hardware.
I truly hope you guys enjoy the new project. Besides, it's time to get some fresh ENERGY back in the Xoom scene anyway!
Stay tuned
Click to expand...
Click to collapse
(Taken from http://forum.xda-developers.com/showthread.php?t=2372197)
That said, welcome to the evolution of TeamEOS - CodefireX or more to say the CodefireXperiment!
Randall (bigrushdog) and me worked hard the last weeks to get the TF101 supported properly with CodefireXperiment, as we promised all devices supported by EOS will be supported by CFX, too .
I finally achieved a mostly working build yesterday, with main hardware working and I couldn't find any issues that EOS hasn't had.
I also ran some benchmarks and compared them to the latest EOS builds (the good ones, not the borked of course) with the help of @Roach2010, EOS and CodefireX team member and the original EOS on TF101 developer. We came to the conclusiion that CFX will give you a roughly estimated 10% performance boost, mostly notable for CPU and I/O performance.
So here I am, to share the first test build with the TF101 community!
Test build #1 - Download
Credits go to the original TeamEOS, and of course the new CodefireX team!
Special thanks go to @bigrushdog for helping me with TF101 bringup (mostly frameworks stuff, I really suck at that) and in general for being a nice team member who is always there for a chat, @synergye for leading the new team and bringing one HELL of optimizations to the new ROM and thus to the TF101. Thank him for the performance boost! @timduru also deserves at least a massive special thanks for assisting and contributing back in EOS times, sadly he didn't move over to CodefireX due to various reasons. However, we all know he enhanced EOS and especially the TF101 to an extend noone of us could have achieved on his own.
Tried this out this evening. Seems pretty good, but minimal, so far. Will check back again after some more work is done.
Pleasure to see you back Chris :good:
Let's test it!
Where to look for changelog, and stuff like "merged" "opened" ... as in Teamos ?
Cool!
I'm still using the last builds of Eos4 on both my Nexus7 and tf101. Both work so well I have a difficult time moving on to anything else, but i'm gonna give this a shot and see how I like it. Thanks for continuing to work on Android for us!
I wonder how long this will last.
Any screenshots?
Sent from my Atrix HD using Tapatalk 4 Beta
Have to say i forgot i still had the test build on my TF. Still going strong without a single issue to report. Hopefully get RaymanFX back with us for another stint seen as hes not allowed to move on and have a life of his own :laugh:
st0nedpenguin said:
I wonder how long this will last.
Click to expand...
Click to collapse
Looks like it was over before it ever really got started.
Sent from my Transformer TF101 using XDA Premium 4 mobile app
just lou said:
Looks like it was over before it ever really got started.
Sent from my Transformer TF101 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup sad but true
Sent from my SCH-I535 using Tapatalk 4
I've noticed quite a bit of development for alot of other devices from CodefireX, but I have not seen anything for the TF101 or any other Asus tablet. Have they abandoned this device line or just really slow to work on it? Timduru since returning from vacation has been a madman and has released not only multiple updates on the 4.2.2 chain but has moved the device onto a stable 4.3 ROM by himself.
Not criticizing here just curious.
Banetbc said:
I've noticed quite a bit of development for alot of other devices from CodefireX, but I have not seen anything for the TF101 or any other Asus tablet. Have they abandoned this device line or just really slow to work on it? Timduru since returning from vacation has been a madman and has released not only multiple updates on the 4.2.2 chain but has moved the device onto a stable 4.3 ROM by himself.
Not criticizing here just curious.
Click to expand...
Click to collapse
This project appears to have been abandoned. At least in terms of the TF101. Not a big deal. timduru has 4.3 fully working on the TF.
Sent from my Nexus 7 using XDA Premium 4 mobile app
just lou said:
This project appears to have been abandoned. At least in terms of the TF101. Not a big deal. timduru has 4.3 fully working on the TF.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Agreed. It seems like some of us saw this coming...
frederuco said:
Agreed. It seems like some of us saw this coming...
Click to expand...
Click to collapse
Yeah fx moved on a while ago in not sure why he comes back fur a tease then leaves again
Sent from my SCH-I535 using Tapatalk 4
zachf714 said:
Yeah fx moved on a while ago in not sure why he comes back fur a tease then leaves again
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I don't know either. He abandoned all his TF projects, then comes back only to tease a new project that never materialized.
Sent from my Nexus 7 using XDA Premium 4 mobile app
just lou said:
I don't know either. He abandoned all his TF projects, then comes back only to tease a new project that never materialized.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah .. I teased 1 project on accident just because I ended up not having time to fully complete it (PAC)
Sent from my SCH-I535 using Tapatalk 4
Well, they did quite a bit at one point or another for our tablets, and it was based on their own time and interest, so I'm not slamming them for moving on to other things, although I am a bit disappointed that they would make the noise of supporting it and nearly completely ignoring it (they did put out a test build).
And I agree, Timduru's builds have been phenominal, I just hope he was able to enjoy his vacation since he's been back, the boy seems to be working like a dog....er a meercat.
Banetbc said:
Well, they did quite a bit at one point or another for our tablets, and it was based on their own time and interest, so I'm not slamming them for moving on to other things, although I am a bit disappointed that they would make the noise of supporting it and nearly completely ignoring it (they did put out a test build).
And I agree, Timduru's builds have been phenominal, I just hope he was able to enjoy his vacation since he's been back, the boy seems to be working like a dog....er a meercat.
Click to expand...
Click to collapse
I do agree with you 100% .. In not slamming them or "bashing" them at all
Sent from my SCH-I535 using Tapatalk 4
zachf714 said:
I do agree with you 100% .. In not slamming them or "bashing" them at all
Click to expand...
Click to collapse
They did good things but it would have been nice to at least say they were not going to continue. Checking that crazy change log has been a pain.
We have to thank Tim for the work but I don't think he will be able too keep it up alone he will burn out trying. He is a great guy.
Which is timdru's most recent stable Rom ,um currently using team eos b202 with kat kernel and it's rock solid and would only change if I can get similar on 4.3,
Sent from my HTC One X using xda premium
I haven't seen any posts about it. I am sure our phones can handle it, but are there any devs thinking about working on it? I know someone got the Nexus 4 to boot on L.
ashwinmudigonda said:
I haven't seen any posts about it. I am sure our phones can handle it, but are there any devs thinking about working on it? I know someone got the Nexus 4 to boot on L.
Click to expand...
Click to collapse
Patience.
I guarantee numerous devs will build L for the S4.
ashwinmudigonda said:
I haven't seen any posts about it. I am sure our phones can handle it, but are there any devs thinking about working on it? I know someone got the Nexus 4 to boot on L.
Click to expand...
Click to collapse
Also remember that "L" is a developer preview. It isn't really designed to work - it's designed to show developers what the next version of Android will be like. Very basic things like the API are still changing. Even when an "L" ROM comes out, I would avoid it as a daily driver at all costs until it stabilizes and gets into Beta.
Hobadee said:
Also remember that "L" is a developer preview. It isn't really designed to work - it's designed to show developers what the next version of Android will be like. Very basic things like the API are still changing. Even when an "L" ROM comes out, I would avoid it as a daily driver at all costs until it stabilizes and gets into Beta.
Click to expand...
Click to collapse
I am aware of all that. I have been watching Android evolve for a few years now. My question was merely why there isn't any talk about it around here from the devs.
I'm hyped for L for the improved battery life.
Well since the Galaxy S3's are getting KitKat, I'm sure we'll be getting Android L when it's stable and released. If anything, we can always get an AOSP Rom
There's no talk because theres nothing to talk about except, "WHERES OUR L UPDATE SAMSUNG?! GOD. YOU TAKE FOR EVER. ANOTHER PHONE HAS IT. GOD I HATE SAMSUNG"
Sent from my SGH-M919 using XDA Premium 4 mobile app