Related
Alot of Developers have bought this phone!! development for Xperia T / TX and V is going to be good! so far we have 2 elite developers 2 recog developers,, correct me if i am wrong
FXP have 4 members
Bin4ry, Defer, Kali, Jerpelea
Codeworkx!
Tilal6991 too for paranoid android
Gok for kernel is gonna be beast.
Lol @ 4. Good start but not exactly a lot. Yet.
...
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
well this is my first sony device, but looks promising, if sony stays open and doesn't screw up like samsung did, even if they are on updates, we'll have CM team for regural updates. actually, i hope this is first device i'll have for more than a year.
we'll see.
Sent from my Xperia T
Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
Support is looking good for devs to get started and this can be seen from the speed CM10 has become available and is progressing on this device. I don't see the lack of activity in this forum as a bad thing and for a dev it's a good thing because they're not hassled every 2 mins with the same repeated support questions or for ETA's (don't do it ). Devs don't choose devices because they're popular, they choose them because they're good to work on and because they personally like the device as remember this is a hobby after all. I for one, if I do get this phone will hope for it to remain as one of the quieter forums but once people start finishing their contracts I can see it attracting a number of people. I finish mine end of this month so that's when I'll be choosing but that choice is based on how easy it'll be to work with as I like to have a play with compiling myself but only for myself really.
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
^aha your right
hello developer!
i think xperia t will get popular because it is the bond phone and the tx looks great in terms of design so it will get popular
Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
TL developer support is going to highly depend on the bootloader locking situation.
As I understand it, AT&T has a bad habit of forcing bootloader locks. I refuse to support any device that has a locked bootloader which is not officially unlockable - even if the lock gets broken unofficially, it's the principle of the thing.
tilal6991 said:
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
Click to expand...
Click to collapse
Yeah. The Infuse was a less popular device, and as a result, the developer community was highly cooperative for a while. Unfortunately, the device itself was a nightmare to work with so it was ditched by many. Although, interestingly enough, now that some of the worst aspects of this device development-wise have been identified, the Infuse is becoming kind of fun to work with again.
In the case of the T - all evidence seems to indicate that it's going to be a highly pleasant device to work with, AND if it's not a super-popular device, it may have a more pleasant development community than some of the more popular devices.
There's an existing well-established team of developers with Sony experience, AND there are also a number of Samsung Exynos refugees that have already made the jump or (in my case) are just waiting to see what their local version of the T has to offer.
That said - based on the developers I've seen hopping over, things are going to be heavily weighed in the AOSP-based firmware side of things. Sony's recent devices have become very attractive to developers of AOSP derivatives due to:
Sony's cooperation with the community in terms of technical information and source releases (see DASH)
Most Sony devices are based on Qualcomm chipsets, and over the past year, CodeAurora has emerged as a high quality reference codebase. (CAF has existed for a long time, but it's not really until this year that I saw people using it heavily.)
Sony's explicit AOSP support, both in terms of binary releases to support JBQ's Xperia S project, and frequent commits to AOSP. In fact, they have one developer working part-time on the AOSP Xperia S tree!
However, going back to Snow_fox's comments - if you want a device that is guaranteed not to be dropped early, purchase a Nexus. With any non-Nexus device, you are always taking risks.
Look at the Samsung Exynos situation - A year ago, Samsung devices were looking like your best bet for ongoing developer support. However, over the past year, a variety of things have changed:
Samsung constantly releases broken HALs that require all sorts of workarounds, and don't play nicely with backwards-compatibility solutions that work on other devices. ICS and JB bringup on Exynos4 devices has been an utter nightmare, leading to the entire team of CM on Exynos devices burning out or coming damn close to it
Samsung decided to use their phones as an outlet for gigantic batches of defective eMMC flash chips. They put workarounds in their firmware but didn't tell anyone. The end result is that you have to tread carefully with any 2011-model Samsung device. Their poor handling of the eMMC disaster has left a sour taste in many developers' mouths.
As a result, many developers are leaving, not necessarily for a device that is flashier, but one that is at least more developer-friendly. I think that in many cases, the Xperia TL will be a downgrade for me compared to my Galaxy Note... But dealing with the Exynos in the Note is driving me utterly insane.
AvRS said:
Support is looking good for devs to get started and this can be seen from the speed CM10 has become available and is progressing on this device. I don't see the lack of activity in this forum as a bad thing and for a dev it's a good thing because they're not hassled every 2 mins with the same repeated support questions or for ETA's (don't do it ). Devs don't choose devices because they're popular, they choose them because they're good to work on and because they personally like the device as remember this is a hobby after all. I for one, if I do get this phone will hope for it to remain as one of the quieter forums but once people start finishing their contracts I can see it attracting a number of people. I finish mine end of this month so that's when I'll be choosing but that choice is based on how easy it'll be to work with as I like to have a play with compiling myself but only for myself really.
Click to expand...
Click to collapse
I will have to decide on December 1st what phone I'm going to myself.
I personally understand the appeal of a quieter forum where the same issues aren't asked every couple of minutes.. Once or twice, I've actually had trouble finding a solution wading through the, "How do I ________" and most of them had the response, "do a search" :silly:
tilal6991 said:
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
Click to expand...
Click to collapse
Yeah.... there are a lot of ungrateful members. I find myself in an awkward position because, I'm not skilled enough to develop a ROM but, I'm know I'm reliant on whatever XDA puts out to stay up to date with the latest ROMs.
Entropy512 said:
TL developer support is going to highly depend on the bootloader locking situation.
As I understand it, AT&T has a bad habit of forcing bootloader locks. I refuse to support any device that has a locked bootloader which is not officially unlockable - even if the lock gets broken unofficially, it's the principle of the thing.
Click to expand...
Click to collapse
If I were in a position to take that stance, I would myself.
[/QUOTE]
There's an existing well-established team of developers with Sony experience, AND there are also a number of Samsung Exynos refugees that have already made the jump or (in my case) are just waiting to see what their local version of the T has to offer.
That said - based on the developers I've seen hopping over, things are going to be heavily weighed in the AOSP-based firmware side of things. Sony's recent devices have become very attractive to developers of AOSP derivatives due to:
Sony's cooperation with the community in terms of technical information and source releases (see DASH)
Most Sony devices are based on Qualcomm chipsets, and over the past year, CodeAurora has emerged as a high quality reference codebase. (CAF has existed for a long time, but it's not really until this year that I saw people using it heavily.)
Sony's explicit AOSP support, both in terms of binary releases to support JBQ's Xperia S project, and frequent commits to AOSP. In fact, they have one developer working part-time on the AOSP Xperia S tree!
However, going back to Snow_fox's comments - if you want a device that is guaranteed not to be dropped early, purchase a Nexus. With any non-Nexus device, you are always taking risks.
[/Quote]
That unfortunately isn't really entirely an option for me. I'm on a family plan and have no capability of getting out of it at the moment. I don't have enough data to make 16 gigs with no SD card feasible.
I really got lucky when my Captivate had identical hardware to the Nexus S and Samsung was actually good about supporting the devs.
Look at the Samsung Exynos situation - A year ago, Samsung devices were looking like your best bet for ongoing developer support. However, over the past year, a variety of things have changed:
Samsung constantly releases broken HALs that require all sorts of workarounds, and don't play nicely with backwards-compatibility solutions that work on other devices. ICS and JB bringup on Exynos4 devices has been an utter nightmare, leading to the entire team of CM on Exynos devices burning out or coming damn close to it
Samsung decided to use their phones as an outlet for gigantic batches of defective eMMC flash chips. They put workarounds in their firmware but didn't tell anyone. The end result is that you have to tread carefully with any 2011-model Samsung device. Their poor handling of the eMMC disaster has left a sour taste in many developers' mouths.
As a result, many developers are leaving, not necessarily for a device that is flashier, but one that is at least more developer-friendly. I think that in many cases, the Xperia TL will be a downgrade for me compared to my Galaxy Note... But dealing with the Exynos in the Note is driving me utterly insane.
Click to expand...
Click to collapse
Do you think that may have some weight on why Google decided to hop to LG for a Nexus device?
Either way, it sounds like I'll be on the Xperia TL or LG Optimus G this upgrade. The decision isn't exactly becoming easier to make though. At least I managed to scratch off the HOX+
i chose xperia phones becase developers say they are not hard to develop , i have an xperia ray and i have a buttload of roms to choose from... i cant decide so i need to fash every 2week!! (flashaholic :l)
also because sony provides solution for bootloader unlock
Here's what I know so far for the TL. Keep in mind none of this is official, and it is preliminary, so could change.
1) The bootloader will NOT be unlockable on any device that has an active SIMlock. e.g. any device sold on AT&T with a contract subsidy is not going to have an unlockable bootloader. This is almost 100% definite.
2) The bootloader should be unlockable for users who pay full price for the device from AT&T, e.g. anyone who can receive an immediate SIM unlock with AT&T's policies. That said, while AT&T says that any person with a full-price device should be able to immediately remove SIMlocks, often it's a major hassle, and I worry that the bootloader unlock "allowability" process will be even less integrated. Don't count on unlocking your bootloader if you purchase full-price directly from AT&T.
3) Sony may sell the device directly (again - they MAY do it, it's not guaranteed), direct-purchase devices will almost surely have an unlockable bootloader (Not guaranteed, but very likely).
Well,TX seems doesn't support for the rom made to T:crying:
niuzhd said:
Well,TX seems doesn't support for the rom made to T:crying:
Click to expand...
Click to collapse
of course not. It's a different device
Coming from laggy XS, now holding TX,
Sony is doing it right this time, TX design and ICS are so smooth, fast and bug free( at least haven't encounter any yet), TBH I don't have any intention to flash Rom or wait for update (JB).
Sent from my LT29i using xda app-developers app
Waiting for my first room tanks all
Envoyé depuis mon LT30p avec Tapatalk
Especially those people who owned the Note since the beginning in Q4 2011.
What do you think of the development of our Exynos-based Note?
How do you feel after one year that CM for our Note even our little brother S2 is not fully working?
Are you satisfied with the stock ROMs provided by Samsung?
How about the superbrick fiasco? Do you think Samsung should have done something more quickly?
What do you think of the Jelly Bean update for Note? Quality is there?
EDIT: One more question. Will you consider a Samsung for your next device?
Development - good not that bad
CyanogenMod - Not working at its full potential but it is still my daily driver
Satisfaction with Samsung firmware ? - Are you kidding ?
How about the superbrick fiasco ? - I considered selling selling my note when Superbrick bug was detected but there were no other 5' phones at that time. Even now, non-removable battery (Xperia Z and others) is a deal-breaker for me.
Jelly bean update - It does not have professional and finishing touch as I quoted your post in other thread.
Am I happy with my Note ?
I am happy because I'm content and I am content because I am happy
For your every question it's a no.. There are not much development even some peps here think uploading the stock deodex rom with xyz name adding some mods which are already present on forum individually is a developmnet..? A big no, but the elite xda-developers who are trying their best bringing cutting edge work and something innovative to android development world is called development and i am very thankful to them.. But still it's not up to par.. I wish i bought a nexus device in place of note regarding android development and modding.. And sammy is just to lazy in providing update to our device and providing source codes, stock jb is just unacceptable for me it's too laggy for anyone who uses cm as a daily driver.. I am afraid to say that cm is also not fully functional, the memory leak sometimes make me go crazy but have to live with this sh*t truth about my beloved note.. After all i love my note than any other device owned by me in past and please don't term me as complainig it's all what any note user has in his heart to say.. And yeah how can i forget about brick bug, when my note firstly got affected by it i was like what the heck is wrong with my baby it is dead and you will not believe still i fear from doing any wipes it doesn't matter if i have modified kernel or not and the black crush issue is like never gonna sorted out
Sent from my GT-N7000 using Tapatalk 2
Development - we hamper our own progress, more politics than codes, groupism, lack of feedback, squelching of viable ideas
CM - an alternative to explore but not be ruled/smothered by.
Samsung performance - Good in many ways- stable, battery friendly/new features/ frequent updates. Good inspite of black clipping, highly priced devices and poor build quality.
Brickbug - never existed beyond the walls of xda and/or rooting process.
Jelly bean - better than ics
Had a lot of fun with my Note. if i didnt have it , with my past experience of it, Id go for a Samsung product but would wait for price to go down first.
NB - Can you really hope for an unbiased answer ? where you become popular and part of the herd if you call Sammy Crapsung and start off your OP with a statement like - I hate Touchwiz , and thanks are heaped on you for it ? Hate begets hate.
I never put forth my views for argument so dont even try.
1 No development to full potential without Exymos drivers, still ppl did best they could. Most devs left by now
[email protected] ... ... ...them.
3No, but some custom ROMs are/were good.
4My phone has sane chip - they should recall vulnerable devices or deliver sw fix earlier.
5For me on AllianceLSZ it is as close as possibly, but I did not tried stock version.
Last one. I don't think so. They grow to big market share - lame corporation. They are lying, promising and not delivering. All I liked -big screen now is no longer Samsung's only thing. I am not fond of cheap plastic too. I liked sd card and removable battery.
Time will tell. HTC one Motorolla X LG who knows?
Development you can't talk about it since it is for every device separate and the devices high end life is under 6 months so developers are using the hit and run tactic since after awhile the device isn't popular and if you now add the delay of source to be given from the manufacture tell me what can - could you await from the developers. Who they make this with 0 to low profit gain except few of them, but that's another story.
You can't compare s2 with any device out there. S2 is legen wait for it dary .
Samsungs firmware upgrade policy was ok till ics came out, the updates where faster then you could find all the changes from one. After the second ics firmware the things did go worse, if I remember right it was s3 comming out time. And before the note 2 was introduced there was the end.
Profit rules them all.
If you don't buy that you will buy the other. Tell me a company who is making a good device with great support? None.
Google isn't producing her own devices.
Apple? Come on you can spend your money somewhere else.
As long smartphones aren't as PC's where you can add 10, different self picked, parts to make a phone and after that you pick a OS to install on it with the drivers for the parts. Till then you will pay to be happy when you will get a fully operating device with SOME of the things you need.
Own a DBT N7000
Flashed first time on JB leak since till then, the device and OS was enought/had nothing to offer more, to my needs.
Cm never used it. But N7000 without spen? Huge respect to the guys and girls for supporting so many devices ofc.
Let the "flames" begin.
Sent from my GT-N7000 using Tapatalk 2
1 [Development]. Well, there are some sweet ROMs and mods, but my mate that recommended looking for stuff here some time ago said there's everything here, and TBH I don't see it, was looking for ported S Memo for JB, ink effect for S Pen only and other small mods and didn't find anything
2 [CM]. Never cared about it, I picked Note for features built around TW
3 [Stocks]. Until JB, it was pretty good, new features, not too much crap, stable and efficient
4 [Brick]. Terrible mistake and marketing failure, didn't affect me fortunately
5 [JB]. Nope, it's a total disappointment, I was eager to update it ASAP, but after I did it I was like "WHAT THE HELL MAN?". Sad, sad update
6 [Sammy]. I never considered any Samsung's phone other than SII or Note, so no
I am still very happy with my Note...with some work to be done, JB is very fast and stable and bugfree...i tried all CM and his derivates and they are great, but i still like modded stock most, mainly for all the features coming with it or possible to add - and it lags 0 (in words ZERO) for me...brickbug was an awful mistake, bricked 2 devices for me (one i got repaired on warranty)...i dont care about blackclipping cause it never affected me that much...
And cause this seems to be the 'bash sammy and note 1 thread' i am looking forward to some public flogging
I am also happy with my note.
I feel there is a strong but disappointed community regarding development. Most developers have strained that Samsung closedness in regards of hardware level drivers have halted back development months if not a year.
I personally feel the folowing is true: because of difficulty in basic os openeness guys like CM team have found time wanting in further development then basic os. I saw endevours in spen functionality and firmly believe if Samsung was more open, not only would rom development taken off more but also the app development. Just gettting rom functional has sucked the living daylights out of a lot of good devs. Had that not been the case they would have been motivated and have time left to revolutionizing further spen/apps stuff. This is a cascading effect.
I in that sense having seen burnouts and close burnouts with certain devs, am definitely not dissapointed in the devs. Greatfull for their devotion and spirit. In Samsung, yes definately dissapointed. I love what Samsung did with JB. But this whole ordeal is not a good example of transforming an opensource platform into a true community platform. That Samsung can do better. Must do better, because the XDA community is already speaking of moving from Samsung to more dev friendly mobiles. Samsung needs to turn that around.
Their future lineup is promising, but with this trackrecord, its not gonna appeal the devs into storming buyin.
More and more users are following favorite devs, if those devs move away, so will xda members following those devs. Time to step up the game Samsung, we know you want to.
Note is a great device(except battery) for me.Yeah,I miss more ported roms from other phones too,but today we have so many different chips and without sources for drivers I know it's hard...
...from SG NOTE N7000 with Tapatalk 2
Livebyte said:
What do you think of the development of our Exynos-based Note?
Click to expand...
Click to collapse
From Samsung, laughable. From individuals, can't ask more.
How do you feel after one year that CM for our Note even our little brother S2 is not fully working?
Click to expand...
Click to collapse
Read somewhere that Samsung denied CM Officials' request to release TW Source. IMHO, I don't know if its true or actually a matter of concern but it is quite noticeable that other manufacturers' devices have amazing CMs whereas TW based phones are suffering.
Are you satisfied with the stock ROMs provided by Samsung?
Click to expand...
Click to collapse
No.
Dear Samsung, Nobody wants your ****ing motion sensor voodoo you call "Smart-this-Smart-that" and annoying visual/audio effects you call "Nature-Nature". Your idea of using a Digitizer with a phone? Excellent. Making a phone that is a Milestone for Smartphones? Fantastic. Providing Dedicated apps? Orgasmic. ****ty optimization? You lost me.
How about the superbrick fiasco? Do you think Samsung should have done something more quickly?
Click to expand...
Click to collapse
Lost my "dear" to that once. My Beloved Samsung with Amazing Proprietary Issues.
What do you think of the Jelly Bean update for Note? Quality is there?
Click to expand...
Click to collapse
Pfffffhahahahahahahaha!!!!!!!!!!!!!! xD
Will you consider a Samsung for your next device?
Click to expand...
Click to collapse
Probably. When it comes to RAW Power, Samsung doesn't shy away. That's the beauty of it.
Note has many achievements.
1. It tasted 3 flavors of android.
2. Its the first >5 inch phone which changed the way of users habit.
3. It has seen the mist development more than galaxy nexus. It got all tge major custom releases with tw stock roms as a bonus.
4. Its the only phone which even after 1 and a half year life has a place in users heart.
5. It was a future proof device of its time and the way dev helped it groom is remarkable.
6. Thanks to devs who despite being annoying contributes so much to make our experience good.
Entropy, dr.ketan,Eybee1976, chasmodo, Criskelo, and so many others who take out time to make things better.
Sent from my GT-N7000 using xda app-developers app
How soon do you guys think a ROM will be made for Nook HD/HD+ after Android L releases? Any guesses? Cyanogen have done a great job with 4.4
That's just going to be a lot of assumptions
sandsofmyst said:
That's just going to be a lot of assumptions
Click to expand...
Click to collapse
Probably why you were the only one to reply xD Thanks man
Just don't like to see 0 replies. That said, there's one now and then that I won't reply to. However, L is of much interest to me and some of the supposed improvements will hopefully be great. Plus L on the nooks would hopefully be even better. So I share your enthusiasm.
The release time could be shorter or longer depending on the amount of porting work to be done. There's other variables too. But someone else might also before cyanogenmod which would be fun.
Thanks for the reply, I agree on L being even better on the Nook varieties. Can't wait!
I was finally starting to look into bumping stock off og my HD9 and saw this... guess I can wait 4-6 months for this to all take shape... I wouldn't want to lose my progress in PvZ2 at this point anyhow
My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.
Goggles2114 said:
My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.
Click to expand...
Click to collapse
With the nook being the nook... you could be right. The latest tech really makes android smooth, not android on the older tech.
OSs don't tend to get faster as they get fancier and the latest tablets and phones have much faster hardware (and more RAM).
Well I mean take a look at the iPhone 4S, it used to be able to run IOS 5 and now it's up to IOS 8 and it's still pretty fast. These companies need to focus as well on making the newer OS work well with older devices. I mean the HD/HD+ is only 2 years old...
Corkerman said:
the HD/HD+ is only 2 years old...
Click to expand...
Click to collapse
It might be 2 years old but the hardware was never really all that great as it wasn't a top-of-the-line tablet when it came out.
Anyway, that's why I'm hoping 5.0 does something to improve performance, but wouldn't expect miracles from it if anything at all. Android just does better on newer hardware.
_________________________
Looks like cm11 m12 improved responsiveness a noticeable amount and finally too. Still not the same amount newer hardware would cause but a welcome improvement.
Goggles2114 said:
My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.
Click to expand...
Click to collapse
I upgraded my Nexus 7 2013 to 5.0.0_r2, and it is noticeably faster than 4.4.4_r2. With kitkat, art sped up menus and navigation, but not really much else. Lollipop is all art - no dalvik option - and not only are menus and navigation faster, but it seems to speed up apps as well, mainly the Chrome browser. I've been using Lollipop for a couple of weeks now, compiled 5.0.0_r2 with 4.4.4 blobs, and I've been pretty impressed. I just built 5.0.0_r5 from source yesterday with the new 5.0 blobs they released. I haven't had time to install it, but I would imagine the performance to be the same as 5.0.0_r2.
Unfortunately, the Nook HD depends heavily on CM source, and quite frankly, it's a little above my expertise. So I'll just have to wait for verygreen, bokbokan, and leapinlar to give us a lollipop build for the Nook HD and HD+.
cahrens said:
I upgraded my Nexus 7 2013 to 5.0.0_r2, and it is noticeably faster
Click to expand...
Click to collapse
That's great to hear it's indeed faster even though it's on a Nexus! Great job and hopefully the three guys can work some magic into the HD's
Corkerman said:
I mean the HD/HD+ is only 2 years old...
Click to expand...
Click to collapse
In consumer products, that's an eternity.
I've been working with Lollipop builds for a few weeks now, so I have a fairly decent idea of what is involved.
1) sensors.c (touchscreen) requires a minor rewrite.
2) hdmi_audio.c requires a symbol to be dropped (or qcom hardware specified, either/or)
3) selinux rewrites... blehch!
4) hwc, domx ... dunno yet, there's apparently working lollipop compatible source available
5) Changes to build/core/Makefile cause most builds to hang on imgdiff, some reversions are required to get around this.
OK, even with all this, I've only had one build boot enough to get some logs. Ironically it was my very first build.
http://pastebin.com/CNBrENWD
I did end up adding libcorkscrew. Anyway every subsequent build I've done reboots even before being able to get a last_kmsg. I'm at the point now where I believe our kernel will need to be patched to handle gcc 4.8. Changing the build to use gcc 4.7 is doable, but isn't very pretty or nice (too many headers have changed).
Anyone have any other hints or suggestions?
Jon Lee said:
I've been working with Lollipop builds for a few weeks now, so I have a fairly decent idea of what is involved.
1) sensors.c (touchscreen) requires a minor rewrite.
2) hdmi_audio.c requires a symbol to be dropped (or qcom hardware specified, either/or)
3) selinux rewrites... blehch!
4) hwc, domx ... dunno yet, there's apparently working lollipop compatible source available
5) Changes to build/core/Makefile cause most builds to hang on imgdiff, some reversions are required to get around this.
OK, even with all this, I've only had one build boot enough to get some logs. Ironically it was my very first build.
http://pastebin.com/CNBrENWD
I did end up adding libcorkscrew. Anyway every subsequent build I've done reboots even before being able to get a last_kmsg. I'm at the point now where I believe our kernel will need to be patched to handle gcc 4.8. Changing the build to use gcc 4.7 is doable, but isn't very pretty or nice (too many headers have changed).
Anyone have any other hints or suggestions?
Click to expand...
Click to collapse
If it were me, I'd look here http://forum.xda-developers.com/kindle-fire/development/rom-kernel-unofficial-cm12-0-otterx-t2958155 or here http://forum.xda-developers.com/kindle-fire/development/slimpop-otterx-t2957450 for some guidance.
Hashcode is a legend on XDA and he has almost single-handedly kept the very old, TI OMAP 4430 Kindle Fire alive. As for lovejoy777, currently, he has been the most active, hard working dev for that same KF. Hashcode has CM12 working and lovejoy777 has Slimpop.
Since our device is so similar to the KF and Hashcode has contributed to the Nook in the past, looks to be a good resource??? Then again, verygreen could also pop in sometime down the road.
Mike T
It was because of installing CM on a Kindle Fire 2 for a friend that I decided to purchase a Nook (wanted an OMAP).
I checked both threads over but didn't immediately find any lollipop android_device source available.
I was right about the kernel (arm/lib/memset.S?). Only took me a week to figure it out.
I'm not quite sure yet what to make of the second set of logs, but this is where I'm at now.
http://pastebin.com/EXnJpp3L
Jon Lee said:
It was because of installing CM on a Kindle Fire 2 for a friend that I decided to purchase a Nook (wanted an OMAP).
I checked both threads over but didn't immediately find any lollipop android_device source available.
I was right about the kernel (arm/lib/memset.S?). Only took me a week to figure it out.
I'm not quite sure yet what to make of the second set of logs, but this is where I'm at now.
http://pastebin.com/EXnJpp3L
Click to expand...
Click to collapse
One of my first android devices was the 1st gen KF and Hashcode helped make an inexpensive E-reader a very viable android tablet. I would PM Hashcode and/or lovejoy777. Hashcode is usually very busy but he has always been helpful towards other devs, I know he gave some assistance to lovejoy777 with SlimPop.
As for lovejoy777, he's fairly new at development but seems to be very helpful. I think he also may have gotten some help/guidance from MwisBest who built a LP rom for the OMAP 4460 Galaxy Nexus. I mention this because I believe he knows the importance of cooperation among devs. As an aside, while reading his thread I think I read that he was in the process of "cleaning up" his github. So, he could be a good source.
Maybe also PM killersloth. He built quite a few nice roms for our Nooks last year and just recently expressed some interest in trying to get LP on our device. Maybe if you contact him, you guys can make something happen. I'm an old fashioned XDA'er that believes cooperation amongst devs and end users is essential in the community. Every little bit can help.
http://forum.xda-developers.com/showpost.php?p=57255968&postcount=14
Anyway, you seem to be a very sharp guy. I wish you luck in getting LP to the Nook. I wish I could contribute more but I'm more of a file swapper and modder of existing work than a dev. :laugh:
Mike T
Moving to Texas in three days, been hectic around here lol.
I had major issues with hwc, selinux, and our old configs. Hashcode must have plowed through it if its running on otter. I'd check his commit history for some tips.
We needed this for prebuilt boot image before
http://review.cyanogenmod.org/#/c/36813/1
I needed it a few weeks back when attempting to build. They might have brought up their own method since then.
I wish they would have called it SlimPop instead of SlimLP ??
A 5.0 build for hummingbird would be nice. Hopefully it won't be hard to modify an ovation build since all the devel appears to be on ovation.
Hello developers.Dont want to be annyoing but I'm new to this devicee and i kinda like it and tried lots and lots of roms for it, and you know that android L/Lollipop is coming soon out, and i want to ask if anyone is gonna like port it to our device because i know some really good developers like the major tonyp and other ones.So if yes i would be really really hyped for it like many other lol
i think that for the reply we have to wait CM12(?)sources comes out,but as i understood in the past our phone is supporting kitkat with a base that starts from ics sources,so we must wait and maybe isn't possible to port, but also for me it will be interesting if the devs can port a rom with lollipop.By the way i was thinking that we are running also some old version of the gapps to make it work with our device due to missing neon support(like youtube or google search for ex.),so don't know if it's possible
TheMysteryouse said:
Hello developers.Dont want to be annyoing but I'm new to this devicee and i kinda like it and tried lots and lots of roms for it, and you know that android L/Lollipop is coming soon out, and i want to ask if anyone is gonna like port it to our device because i know some really good developers like the major tonyp and other ones.So if yes i would be really really hyped for it like many other lol
Click to expand...
Click to collapse
We had to wait 3 months for CM11 M1 to come out after KitKat was released, and knowing that Lollipop is quite a large overhaul and that it fully uses the ART runtime, we can expect a larger delay for CM12 M1. And even when it comes out, it will be almost featureless. As far as I know, Lollipop sources haven't been yet released, so we'll have to wait and see.
Second, yes, we are running on old ICS sources, so unless the 3.x kernel becomes super stable so we can use newer drivers, if they are available for our device, we'll have a bad time.
Third, this is a subforum for Development Discussion, so this kind of thread is more welcomed in the General Discussion section or even Q&A.
Keep on modding Other than that, KitKat development has been quite amazing in the last few months, and considering that the O2X is a device released in 2011, we are more than been blessed regarding this device. Ludnica, brate, ludnica.
Jes jes hahaha. Well whatever happens we will maybe be able to get something of it.I will try my best.I dont rly know much about coding but i know some stuff and i am learning every day more and more so yeah.I hope if we all combine our inteligence we will get something.
Oh and the sources should be out on i think November 5th
Testing Platform available
I like the idea of L for P990. I recently bought a new phone. That spares my P990 for testing full time as I have another phone for regular use. Please let me should you like to test anything, I will happily share the results. The least I can do to aid further development.
So this is a post for just making people realise some of the things going on in the Samsung Galaxy Tab A development forum (specifically the custom Rom development). So let's get right into the thing. I believe custom Rom should be focusing on bringing newness to old devices. Of course and some features are not available in New devices, and custom Rom and debloated roms help fill the gap ( we all know how heavily modded Samsung firmware is).
However recently there is a trend for DEVELOPERS to make custom roms for recently released devices ( SM-T580, SM-T280) . While the old 2015 models and others have no roms yet. I did hear that someone was making a unified Rom for some of these models months ago. I'm not saying that there shouldn't be any roms for new models . But there is an overcrowding in the market with custom roms for these devices and also with very little difference between these roms. Imagine this like there are a lot of products for one group of people and the rest get no products at all!
So this is my petition. Can just some of you show a bit love for these devices? If enough of you respond to this maybe there will be a positive change! That's all I want . I want everyone to pass this message around. Thanks for the help. And thank you Developers who make custom roms for any device because I know it's a hard job and you are doing this for free. :good:
Peace
P.S: This is my first post. I know I did some things wrong. So PLEASE don't be too critical about this.
Hint, Hint!! Devs make mods for devices they OWN. They aren't in it to support Samsung. They aren't in it to be charitable. They are in it because they enjoy doing what they do and want the "latest and greatest" for themselves. But they ARE NOT going to support old devices they no longer have.
edit: There is also the fact that "custom" ROMs, like RR, Extremely and Ultra, are all just modifications of the STOCK ROM from Samsung. So, if Samsung hasn't produced a new ROM for an older device, then there is nothing to modify. The exception to that are the ROMs based on the LineageOS. But, again, these are based on adaptions from other devices that use the same SoC. So, if the LineageOS devs haven't produced one for the SoCs in older devices, you won't see one for your older Tab A.
Then why do they provide support for their releases. I get the thing you said about how roms a modified. But I dont think they make it just for themselves. If that were the case the would not be any "community" and XDA IS a well-knit community. Developers like @ashyx and @JazzPresso provide and support people with their mods and stuff. So the "want the "latest and greatest" for themselves. But they ARE NOT going to support old devices they no longer have. " part I don't get.
Sent from my Samsung SM-T355 using XDA Labs
How are they supposed to debug problems when they no longer have a device to use for testing? What's not to get?
But once you have device tree (more or less in stone) it's easy to just keep up to date. (To a degree) but only the latest popular devices get anything. Look at the smt280 ... Absolutely f***ING nothing past root for it. One decent time (decent being used loosely) while the exact same one other than modems are activated (t285) gets quite a bit of love. They are the exact same device! I'm fairly sure the 280 even has the modems! Just deactivated. We have to work with the devs more flexibility do they can do build and have GOOD feedback, timely reports and sure knowledge of how to log. (I stuck at it all) that's how but there are thread after thread of similar devices that none ever gives these devs the info. Dumps, etc that is needed to help us. We inquire on root or rom then they ask for stuff and we disappear. Never to be heard from again. Lots of these devs are so selfless in their endeavor with goose eggs for return
remarkablecow913 said:
But once you have device tree (more or less in stone) it's easy to just keep up to date. (To a degree) but only the latest popular devices get anything. Look at the smt280 ... Absolutely f***ING nothing past root for it. One decent time (decent being used loosely) while the exact same one other than modems are activated (t285) gets quite a bit of love. They are the exact same device! I'm fairly sure the 280 even has the modems! Just deactivated. We have to work with the devs more flexibility do they can do build and have GOOD feedback, timely reports and sure knowledge of how to log. (I stuck at it all) that's how but there are thread after thread of similar devices that none ever gives these devs the info. Dumps, etc that is needed to help us. We inquire on root or rom then they ask for stuff and we disappear. Never to be heard from again. Lots of these devs are so selfless in their endeavor with goose eggs for return
Click to expand...
Click to collapse
The last Samsung stock ROM for the 280 was 5.1. and there is no Linage version later than that to work from. But if you are so sure there is no difference between the 280 and 285, other than the modem, why don't you try flashing the 285 ROM on the 280? There is an Omni 6.0 ROM for the 285. I've successfully flashed 585 ROMs on a 580.
Anyway, complaining isn't going to change anything. No dev is going to put any effort into an outdated tablet.
If only someone could port treble then the tablet would be sorted. But I doubt that's ever going to happen.
lewmur said:
The last Samsung stock ROM for the 280 was 5.1. and there is no Linage version later than that to work from. But if you are so sure there is no difference between the 280 and 285, other than the modem, why don't you try flashing the 285 ROM on the 280? There is an Omni 6.0 ROM for the 285. I've successfully flashed 585 ROMs on a 580.
Anyway, complaining isn't going to change anything. No dev is going to put any effort into an outdated tablet.
Click to expand...
Click to collapse
Anytime I tried twrp error was just because of device name or something of that sort. Is there a way of kinda forcing the flash? I've never tried it through other way. Thanks for advice