Develop Bugs

[Q] [DEV] AIO Samsung SGS-II Tool?

Hey guys,
I thought I might get the ball rolling and throw a post up here. Was a Samsung Vibrant user before I got my SGS-II on Friday. The AIO Vibrant Toolbox became an invaluable tool for flashing/rooting/stock-flashing/etc. my Vibrant. Was wondering if anyone was working on developing the same tool for the SGS-II?
If the source is available anywhere, I wouldn't mind taking a look at it myself with one of my buddies. I'm a wireless test engineer for an Android Device that's in development and we've worked on some android housekeeping/downloading/utilities software over the past few months. Wouldn't mind trying to contribute to the XDA Community.
Either way, I think it would be awesome to have something like this with the inevitable torrent of ROMs/Mods/Roots and such that will be coming.

hexagon_sun said:
Hey guys,
I thought I might get the ball rolling and throw a post up here. Was a Samsung Vibrant user before I got my SGS-II on Friday. The AIO Vibrant Toolbox became an invaluable tool for flashing/rooting/stock-flashing/etc. my Vibrant. Was wondering if anyone was working on developing the same tool for the SGS-II?
If the source is available anywhere, I wouldn't mind taking a look at it myself with one of my buddies. I'm a wireless test engineer for an Android Device that's in development and we've worked on some android housekeeping/downloading/utilities software over the past few months. Wouldn't mind trying to contribute to the XDA Community.
Either way, I think it would be awesome to have something like this with the inevitable torrent of ROMs/Mods/Roots and such that will be coming.
Click to expand...
Click to collapse
The source code is available at https://opensource.samsung.com/ under SGH-T989_Opensource.zip

rUsTyRuSs said:
The source code is available at https://opensource.samsung.com/ under SGH-T989_Opensource.zip
Click to expand...
Click to collapse
edited for clarity..
hexagon_sun said:
...The AIO Vibrant Toolbox .. .anyone [] working on developing the same tool for the SGS-II? ... If the source is available anywhere, I wouldn't ... mind trying to contribute to the XDA Community...
Click to expand...
Click to collapse
IDK about you, but it seems pretty clear to me that he wants the source for the Toolbox, not the phone...

Thanks, downloading that now.
What about the binaries/source for the Vibrant Tool? I know I might have to check the Vibrant forums for this, but if anyone on here is a Vibrant Migrant like I am and happens to have/know the location of the original source for it, that would be awesome.
Thanks in advance.

cavemaneca said:
edited for clarity..
IDK about you, but it seems pretty clear to me that he wants the source for the Toolbox, not the phone...
Click to expand...
Click to collapse
You're right, that was what I was actually looking for. Doesn't hurt to have a link of the SGH-T989 source readily available though either.

cavemaneca said:
edited for clarity..
IDK about you, but it seems pretty clear to me that he wants the source for the Toolbox, not the phone...
Click to expand...
Click to collapse
Sorry about that. Still half asleep. lol.

[Q] AOSP samsung t989 compile?

Can some one tell me why we can't compile AOSP for the t989 and just use Samsung kernel so everything works? Basically why can't we kang together a t989 ROM that is how much ever is needed of Samsung device modules etc and the rest AOSP?

jahrule said:
Can some one tell me why we can't compile AOSP for the t989 and just use Samsung kernel so everything works? Basically why can't we kang together a t989 ROM that is how much ever is needed of Samsung device modules etc and the rest AOSP?
Click to expand...
Click to collapse
You should do it so that we get AOSP rom

jim93 said:
You should do it so that we get AOSP rom
Click to expand...
Click to collapse
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
Sent from my SGH-T989 using Tapatalk 2 Beta-5

Towle said:
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
It is cool. And yes i would love to do it. With my experience with linux this would be no biggie, but android i have no idea. I think that if it was possible surely someone would have made a flawless 98% AOSP rom with 2% samsung parts....... right?

Towle said:
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Csb are u done tryna be a mod? Cause reading back to your comment you didn't really contribute anything useful to his question either.
Now as for the question also apks cannot simply be installed on a touchwiz room the framework for both of these is pretty different you have to actually change code and port it over can't simply uninstall =(
Sent from my SGH-T989 using XDA

lilz4life said:
Csb are u done tryna be a mod? Cause reading back to your comment you didn't really contribute anything useful to his question either.
Now as for the question also apks cannot simply be installed on a touchwiz room the framework for both of these is pretty different you have to actually change code and port it over can't simply uninstall =(
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
You did not answer my question at all.

Then I don't u derstand ur question.
Sent from my SGH-T989 using XDA

Okay, it is very difficult to make an AOSP ROM with no device tree. That's why we have barely any 100% working. Remember, if you take kernel apart, you will find yourself with many, many files. You need to look through them all and link all the files. If those linked files don't work, then maybe you have to add some. If it still doesn't work, you will need to rework the drivers/firmwares. It is a difficult process. You also need to link all kernel/ROM together. *APK's HAS NOTHING TO DO WITH THIS PORTING PROCESS*

jahrule said:
Can some one tell me why we can't compile AOSP for the t989 and just use Samsung kernel so everything works? Basically why can't we kang together a t989 ROM that is how much ever is needed of Samsung device modules etc and the rest AOSP?
Click to expand...
Click to collapse
Apparently you have never worked with source and/or compiled from... there are plenty of reasons why that can't happen. Main reason there is no device tree with proper source.
:: DARKSIDE ::

thederekjay said:
Apparently you have never worked with source and/or compiled from... there are plenty of reasons why that can't happen. Main reason there is no device tree with proper source.
:: DARKSIDE ::
Click to expand...
Click to collapse
I only use linux for the past 5 years i sure the hell have compiled and worked with source. I just never had to compile for anything other than x86(_64) cpu before aka no toolchaining.

Towle said:
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
This is among the useful response for the original question. I was just encouraging him to go try it that is the best way form him to figure out why its not that simple.
This question has been asked before and I have seen how people have responded with different answers of this question. Whenever this question has been responded with technical reasons then it just ends up being followed by a question of why cant you do "A" even though "A" is based on not knowing another technical reason. The problem is the real satisfactory answer involves knowing alot of the basics which would have precluded you from asking the question in the first place.
Asking this question is like ends up like the following
"A: Why cant you fish with potato bits as bait?"
"B: well fishes dont like to eat potatoes"
"A: potato is food though,Why dont they like food"
It has been suggested before so clearly if someone knew how to do it they would have done it. The best thing at this stage is to try it.

alphadog32 said:
Okay, it is very difficult to make an AOSP ROM with no device tree. That's why we have barely any 100% working. Remember, if you take kernel apart, you will find yourself with many, many files. You need to look through them all and link all the files. If those linked files don't work, then maybe you have to add some. If it still doesn't work, you will need to rework the drivers/firmwares. It is a difficult process. You also need to link all kernel/ROM together. *APK's HAS NOTHING TO DO WITH THIS PORTING PROCESS*
Click to expand...
Click to collapse
Yea.. I was not implying that we grab APKs from some random AOSP build and copy on top of some working stock ROM. My question more is that I see on samsungs opensource site they give us kernel source for the t989 (have not looked at it yet) and then they gave us some build files to copy over and overwrite the build environment for AOSP which I did and built (currently trying to figure out how to use the *.img files), but shouldn't that give us a ~90% AOSP build? That or I am completely not understanding the README file from samsung.

jim93 said:
This is among the useful response for the original question. I was just encouraging him to go try it that is the best way form him to figure out why its not that simple.
This question has been asked before and I have seen how people have responded with different answers of this question. Whenever this question has been responded with technical reasons then it just ends up being followed by a question of why cant you do "A" even though "A" is based on not knowing another technical reason. The problem is the real satisfactory answer involves knowing alot of the basics which would have precluded you from asking the question in the first place.
Asking this question is like ends up like the following
"A: Why cant you fish with potato bits as bait?"
"B: well fishes dont like to eat potatoes"
"A: potato is food though,Why dont they like food"
Click to expand...
Click to collapse
I think he was trying to say if you don't want to spend the time explaining the details because you make some asumptions about people and their posts whom you have never met... then it is best you remain silent rather than giving some smart remark as an answer.

jahrule said:
I think he was trying to say if you don't want to spend the time explaining the details because you make some asumptions about people and their posts whom you have never met... then it is best you remain silent rather than giving some smart remark as an answer.
Click to expand...
Click to collapse
I wasnt giving you a smart remarks just pointing out that at this point it is best to just try it because nobody knows all the exact steps because nobody has done it for this device.
You are left seeking genera android kernel advice which ->
If you run into trouble with technical details go here http://forum.xda-developers.com/forumdisplay.php?f=565 since it is a better place to ask questions about using img files than in the same forum where people ask "how do I install custom rom" even the themer section is a better place.

jim93 said:
I wasnt giving you a smart remarks just pointing out that at this point it is best to just try it because nobody knows all the exact steps because nobody has done it for this device.
You are left seeking genera android kernel advice which ->
If you run into trouble with technical details go here http://forum.xda-developers.com/forumdisplay.php?f=565 since it is a better place to ask questions about using img files than in the same forum where people ask "how do I install custom rom" even the themer section is a better place.
Click to expand...
Click to collapse
I was not saying you were being a smart %^& just saying what I think dude was saying. In fact because of your comment I went got the source from samsung and repo synced AOSP and compiled it and have been playing around since just a little stuck now. My question was for more a technical reason. I understand now that we don't have a device tree for the t989 that works flawlessly... at least thats what i get from alpha and darkside. Now my question more is what the heck is the use of the source from samsung then?

jahrule said:
I was not saying you were being a smart %^& just saying what I think dude was saying. In fact because of your comment I went got the source from samsung and repo synced AOSP and compiled it and have been playing around since just a little stuck now. My question was for more a technical reason. I understand now that we don't have a device tree for the t989 that works flawlessly... at least thats what i get from alpha and darkside. Now my question more is what the heck is the use of the source from samsung then?
Click to expand...
Click to collapse
You can actually modify the Kernel it just takes work. For example if for some reason either the t989 or skyrockets ICS kernel was open sourced there would be a rotation fix so quick for the one with broken rotation.
Samsung just throws the source they finished out there but doesnt really provide or I think care to provide any work towards AOSP builds.

Check out this thread.

rynstphn said:
Check out this thread.
Click to expand...
Click to collapse
Hes asking about compiling Kernel from source I think

jim93 said:
Hes asking about compiling Kernel from source I think
Click to expand...
Click to collapse
No i am talking about the userland
Sent from my SGH-T989 using XDA

rynstphn said:
Check out this thread.
Click to expand...
Click to collapse
Yea thats cool and all but i am more intetested in GB. There is sone source that samsung gives us which i thought is the device tree for this phone... So in essence what i am asking is: what is the source that samsung provides and what use is it? I am aware of the kernel source already i am refering to the other package.
Sent from my SGH-T989 using XDA

[Q&A] CM10

This will be the offical q&a thread for my CM10 rom, if you have any questions or would like to report a bug please do so here and not in the development thread, thanks!
The thread

I really like that you are doing this, wish I could help you more but just dont have the knowledge.
Are you planning on a straight cm10 ported to this phone or are you going to try and keep the s pen functionality?
Either way excited to see your progress.
Thanks for taking the time to make more options for this bad ass phone.

From what I understand the CM team is considering on working on the spen functionality, as far as I know it is dependent on touchwiz, even if they were to get it to work it would be nothing more than a regular stylus.

Theres some good stylus gesture apps around that will help with that though...im checking out your port tonight. .
Is this a direct port from the other version of galaxy note2..or did you use a stock att note 2 stock base and port this ? Just curious before I try to install this so I have an idea..does it include the att modem and a stock kernel within the rom?.. thank you

i didn't want to post in the dev thread, because i haven't done much dev . but i'm very interested in an aosp build for this device. i have my build environment setup and i can build, but i'm just adding random things now to see what sticks (from the international note2).
i can certainly lend myself or my build server out.

Will CM10 be 4.2 or 4.1.2?

My understanding is that basic stylus input works in the current CM10 for the n7100 and for most roms for the original note. Native support for stylus input was added in ICS.

Does anyone have an approximate date that CM10 might be available for the Note 2

MarkWorsnop said:
Does anyone have an approximate date that CM10 might be available for the Note 2
Click to expand...
Click to collapse
Rule number 1, never ask for ETA's. My guess is soon...but just wait , it will come
Sent from my SAMSUNG-SGH-I317 using xda premium

MarkWorsnop said:
Does anyone have an approximate date that CM10 might be available for the Note 2
Click to expand...
Click to collapse
I know. I can't wait either.

MarkWorsnop said:
Does anyone have an approximate date that CM10 might be available for the Note 2
Click to expand...
Click to collapse
As said before most users will all reply the same way. ..never ask for eta blah vlah blah.
To answer your question t there is kernel issues with the drivers for data and connection along those terms. From what I read we do have some developers compiling cm 10 from scratch for our devices. My guess we are a few weeks away b4 we see a daily use version. .Lots of errors but usable.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Haha i know better than to ask for an ETA on the developer section.
I was hoping someone might have an idea if it's in the works or not.
I got my note 2 and love it but miss cm10.lol

[Q] Build CM (CyanogenMod) for the hltetmo

Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht

gakio12 said:
Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht
Click to expand...
Click to collapse
It looks like it's progress or at least people are tinkering around with it. However, you would need a full tree for the device if you wanted to build it from source, know enough to get your own tree, or be able to fork from other device tree's to get something going. The new Nexus has the same chip so that may make things quicker with getting a full working device tree. I'm just quoting based on my own understanding of things, so please correct me if I'm wrong.

I've been wanting to know the same. I've built AOSP ROMs before (namely AOKP for my Note 1 pulling from CM's device tree) and would do the same if the files were available for the Note 3. A few devs have teased the community with screenshots, but until they post their code a tease and a cruel joke is all that it is. I really wish these devs would put their source code up even if it is incomplete and let the community at large get this thing in gear since obviously they can't do it fast enough single-handedly. Holding back code until it's "ready" defeats the entire purpose of open source development in the first place! We have the kernel but no one has a full device tree out yet, only a limited one for recovery purposes (mainly the TeamWin one from TWRP).

Any updates on cm10 or cm11 for the note 3
Sent from my SM-N900T

Within hours of any (usable) device tree updates you'll see an explosion of new CM-based firmwares in the Dev sections.
I'll be building BeanStalk for hltetmo, probably 100 ppl will upload unofficial CM 11, it'll be a giant party for all.

CrashTestDroid said:
Within hours of any device tree updates you'll see an explosion of new CM-based firmwares in the Dev sections.
I'll be building BeanStalk for hltetmo, probably 100 ppl will upload unofficial CM 11, it'll be a giant party for all.
Click to expand...
Click to collapse
Sooo... When's this party begin? :angel::fingers-crossed:

Can't wait for this
Sent from my SM-N900T using Tapatalk

Me neither even got rid of my note and went with n5 cause I couldn't wait but im back tk the beast just need cm
Sent from my SM-N900T

Ker~Man said:
Sooo... When's this party begin? :angel::fingers-crossed:
Click to expand...
Click to collapse
When a hlte device tree is buildable, looks like CM is making additions and others like nikkdotcom

gakio12 said:
Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht
Click to expand...
Click to collapse
Its getting real close. I imagine some other stuff is needed like qcom hardware updates and stuff. I'd give it another few weeks or so. BUT I imagine it'll be available soon.

I noticed nikkdotcom has a thread over in general for trying to get it running; he is asking for assistance in getting it to work.

CrashTestDroid said:
When a hlte device tree is buildable, looks like CM is making additions and others like nikkdotcom
Click to expand...
Click to collapse
That would be accurate.
Nikkdotcom GitHub here: https://github.com/nikkdotcom/android_device_samsung_hltetmo
---------- Post added at 01:18 AM ---------- Previous post was at 01:10 AM ----------
gakio12 said:
I noticed nikkdotcom has a thread over in general for trying to get it running; he is asking for assistance in getting it to work.
Click to expand...
Click to collapse
Im looking for someone who knows a little better than me about building without the proper blobs for the device. Once the right blobs are available, it will be custom ROMs galore!

What blobs do you need? I thought blobs had to be extracted from the TW stock ROM. GPU blobs should be able to come from any other S800 device right (like the Nexus 5)?
Sent from my SM-N900T using xda app-developers app

geekcentercreations said:
That would be accurate.
Nikkdotcom GitHub here: https://github.com/nikkdotcom/android_device_samsung_hltetmo
---------- Post added at 01:18 AM ---------- Previous post was at 01:10 AM ----------
Im looking for someone who knows a little better than me about building without the proper blobs for the device. Once the right blobs are available, it will be custom ROMs galore!
Click to expand...
Click to collapse
I'd be more than happy to lend a hand.

ProTekk said:
I'd be more than happy to lend a hand.
Click to expand...
Click to collapse
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?

idtheftvictim said:
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?
Click to expand...
Click to collapse
There's enough on GitHub right now for a starting point. I've just started to poke around this morning so I can't say much. Tbh, I've been fairly content with TouchWiz so that's been one reason I haven't had a strong interest in working on AOSP

idtheftvictim said:
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?
Click to expand...
Click to collapse
Really? Content with touchwiz? Hmmm...I wish I knew more, I would be started trying to build cm awhile ago
Sent from my SM-N900T using xda app-developers app

Here is the most likely furthest along tree for anyone.
https://github.com/utkanos/android_device_samsung_hltetmo
It just seems like we might not see stuff on this device. Looking back on this thread people talked like it would be released in a week but I think it's going to be a lot longer than that.

idtheftvictim said:
Really? Content with touchwiz? Hmmm...I wish I knew more, I would be started trying to build cm awhile ago
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
That stuff is 2 months old. Nothing in two months? Man...no progress
Sent from my SM-N900T using xda app-developers app

I've never seen a device of this caliber take this long to receive an AOSP ROM! Wish I knew how guys, I'm tired of the TW ROMS, need some action in this forum already

CyanogenMod, Paranoid Android, or any other ROMs?

Would Cyanogen Mod be interested in developing for this phone now that we have unlocked bootloader? Given the choice, I'd love Paranoid Android, but I went hold my breath.

CM is already in development . https://github.com/CM-zenfone2

BrokenROM https://github.com/BrokenROM/device_asus_moorefield

Seems that are only for ZE551ML I hope that will be compatible with ZE550ML

If someone can get pure AOSP or CM working, the ROMs will flow out like water... once a base is established building many ROMs is easy. If we get CM, then look for ROMs like Beanstalk, BlissPop, Carbon, , etc. to follow closely behind. Patience, it will happen...

MatteXperiaU said:
CM is already in development . https://github.com/CM-zenfone2
Click to expand...
Click to collapse
Yay! I really hope Paranoid Android follows suit. I LOVE Pa's Halo feature.

custom roms will help this phone.zenny 2 has one of the worst stock firmware optimization ever and seems like asus cant fix the problems.

Be patient guys, I just sent a couple developers phones this week.

Tuanies said:
Be patient guys, I just sent a couple developers phones this week.
Click to expand...
Click to collapse
Cool! I see lots of potential ROM development for this phone!
Sent from my ASUS_Z00AD using XDA Free mobile app

Tuanies said:
Be patient guys, I just sent a couple developers phones this week.
Click to expand...
Click to collapse
Good to see Asus is showing commitment to this phone. Also great to see you guys are embracing the aftermarket ROM community. More vendors need to be supportive like this.

We love the enthusiast community - you guys are the ones that like to tinker and have contributed to our growth over the years when we were just a motherboard vendor. I bet many of you still have fond memories of building PCs with our components before tinkering with phones .

Tuanies said:
Be patient guys, I just sent a couple developers phones this week.
Click to expand...
Click to collapse
Awesome! Is there/will there be collaboration with the developers regarding the kernel and device tree from ASUS as well? That would be key to have a fully-working custom ROM in the nearer future (versus the developers having to learn from scratch and sort of fend for themselves, kludging their way along and delaying the end goal).
So exciting!

We post our kernel source, but that's all we can offer, unfortunately. Our software development is done at our Taiwan HQ. But if any devs need anything, just send me a PM and I'll ask our software team.

Tuanies said:
We love the enthusiast community - you guys are the ones that like to tinker and have contributed to our growth over the years when we were just a motherboard vendor. I bet many of you still have fond memories of building PCs with our components before tinkering with phones .
Click to expand...
Click to collapse
Tuanies said:
We post our kernel source, but that's all we can offer, unfortunately. Our software development is done at our Taiwan HQ. But if any devs need anything, just send me a PM and I'll ask our software team.
Click to expand...
Click to collapse
Just got one single request... Open an official outlet or distributer in Pakistan... I am buying your items off international vendors without warranties... Would love to see if I can get some support locally...

Tuanies said:
We post our kernel source, but that's all we can offer, unfortunately. Our software development is done at our Taiwan HQ. But if any devs need anything, just send me a PM and I'll ask our software team.
Click to expand...
Click to collapse
CC: @TheSSJ, @shakalaca, @jrior001, @crpalmer, @sorg, @Harfainx, @vampirefo and other zf2 developers.. :victory:

Tuanies said:
Be patient guys, I just sent a couple developers phones this week.
Click to expand...
Click to collapse
This makes not much sense to me honestly. Why locking a bootloader in the first place and then stating to push development hard by providing test phones to specified devs?
But still I want to thank you for your commitment in making this phone a huge success - we'll kick Galaxy and Xperia and the likes out once done

Good thing to see Asus sharing to make custom ROMs efficient.
Already on Harfainx's ROM, can't wait to see things going even further.

SBFarooq said:
Just got one single request... Open an official outlet or distributer in Pakistan... I am buying your items off international vendors without warranties... Would love to see if I can get some support locally...
Click to expand...
Click to collapse
Unfortunately in only responsible for North America and have no say for any other regions.
TheSSJ said:
This makes not much sense to me honestly. Why locking a bootloader in the first place and then stating to push development hard by providing test phones to specified devs?
But still I want to thank you for your commitment in making this phone a huge success - we'll kick Galaxy and Xperia and the likes out once done
Click to expand...
Click to collapse
This is my push from Technical Marketing for North America due to needs and wants for the US market. I place great emphasis on the community that has made many of the previous phones I've owned so great. I want that for the ZF2.

I'll probably start development for this phone once i get it. Never worked with an x86 android device before but it sounds like a fun challenge

Tuanies said:
This is my push from Technical Marketing for North America due to needs and wants for the US market. I place great emphasis on the community that has made many of the previous phones I've owned so great. I want that for the ZF2.
Click to expand...
Click to collapse
Hi,
I've got some sort of situation here concerning building the kernel for ZF2 on my own. I downloaded the kernel source from ASUS website and followed the instructions one by one (download the android source code, use the appropriate toolchain, issue the kernel build command using fhd_defconfig, etc.
The phone boots and works good, BUT:
The phone never gets to deep sleep mode because of hsic_s3_wlock (kernel wakelock from USB HSIC). Could you please ask someone from the technical department to check what is causing this or if any config entry is missing? I am really starting to doubt that this is something I can influence at all