Develop Bugs

[Kernel][Both] USB host mode support added (github link)

Hi ya'll,
I've just added USB host mode support for the Galaxy Tabs. ( Can some mod move this post to the Android developer forum and bless me for posting in that forum? I'm happy to answer questions/discuss but I can't post there yet because I just created this account)
[Ugh! because I have less than eight posts I can't include github links - you'll need to linkify yourself... ]
The github site is here:
github.../humcycles/galaxy-tab-modified
Documentation on the changes:
github.../humcycles/galaxy-tab-modified/blob/master/Kernel/Documentation/usb/s3c-otg-host.txt
The changelist you probably want if you are want to cherry-pick into another kernel tree:
github.../humcycles/galaxy-tab-modified/commit/99388abf98f8b8583dcfb31339c8673a9fea62bd
These changes fix a number of bugs in the Samsung host mode software but are probably not well suited for regular end users. I would recommend that developers who are generating Galaxy Tab kernels consider picking up these changes.

https://github.com/humcycles/galaxy-tab-modified
https://github.com/humcycles/galaxy...ter/Kernel/Documentation/usb/s3c-otg-host.txt
https://github.com/humcycles/galaxy-tab-modified/commit/99388abf98f8b8583dcfb31339c8673a9fea62bd
Links for the lazy..

Wait it so long
Sent from my GT-P1000 using XDA App

Does P1000 have the right hw, can it provide 5 volts to usb client or we also need a power injector (usb hub)?

It really works? That would be superb news! Thank you very much for investing your time in it. Can`t wait to see it in a kernel on my tab.

Mjoelnir77 said:
It really works? That would be superb news! Thank you very much for investing your time in it. Can`t wait to see it in a kernel on my tab.
Click to expand...
Click to collapse
Yes. It works for me on a Sprint SPH-P100, but I bet it will work on all 7" tabs (the USB hw seems the same). I look forward to some other dev trying it out and letting me know how it works for them. From looking at the samsung sample code, I bet it will work on most samsung chipset based devices (certainly the S5PC100 based ones).
*** Can some mod move this thread to the Galaxy Tab Development forum and bless me for posting there? ***

mdalacu said:
Does P1000 have the right hw, can it provide 5 volts to usb client or we also need a power injector (usb hub)?
Click to expand...
Click to collapse
I bet it will also need power for the 5V USB. In the samsung code they have bits that look like it is turning on the right LDO to have power, but nothing comes out on my SPH-P100. Either the sw init needs more work, or they didn't stuff some part when they built up the units.
[ Ugh - I can only reply once every 5 mins because I don't have enough posts ]

punkgeek said:
Yes. It works for me on a Sprint SPH-P100, but I bet it will work on all 7" tabs (the USB hw seems the same). I look forward to some other dev trying it out and letting me know how it works for them. From looking at the samsung sample code, I bet it will work on most samsung chipset based devices...
Click to expand...
Click to collapse
Does that mean this hasn't actually been tested on a SGT yet?

Blittz said:
Does that mean this hasn't actually been tested on a SGT yet?
Click to expand...
Click to collapse
I've tested it on a few Sprint 7" SGT's here, but it would be great for another dev to try it in their kernel.

It is a great thing, you deserve so many thanks!...
Now what I need is a kernel with usb host and swap enabled.

Can somebody explain why it is needed? What is it good for?

odysseus84 said:
Can somebody explain why it is needed? What is it good for?
Click to expand...
Click to collapse
It allows the Tab to act as the controller for USB devices, rather than the other way around. In practice, it means that you can use things like usb sticks, keyboards, mice and the like which usually require a computer (the host) with the Tab.
Anyone more knowledgeable, feel free to correct me.

for months I wait this,
SGS also waiting it too, Shall you post in their forum?

zoftdev said:
for months I wait this,
SGS also waiting it too, Shall you post in their forum?
Click to expand...
Click to collapse
Sure. And since I haven't seen a mod move this to the right forum yet, I hope ya'll don't mind if I bump up my post count to 10 by replying to this thread. After I have ten posts I can post in their forum.

bumping my post count

bumping my post count

This is great!!

bumping my post count

lol, don`t get banned over this - it is for a good cause, but one never knows if the Mods that see this see it the same way

Mjoelnir77 said:
lol, don`t get banned over this - it is for a good cause, but one never knows if the Mods that see this see it the same way
Click to expand...
Click to collapse
Hmm - I just want to be able to discuss this in the right forum. I hope I don't get banned, but I don't really care to much - I made these fixes because I needed host mode for my application. I'm almost there - just need one more post

flashing i9100 roms to t989

i know its been asked but i'm starting the discussion. there has to be an easy way to flash all these great i9100 roms on to our tmobile t989. i would think its mostly a kernal difference and some hardware buttons. i say this because i love hyperdroid roms (mostly wanted s2 for use of his rom) .with the hd2 all builds worked on all phones (europe,asia,usa,etc) no matter the model number.
i am starting the discussion and will help to develop with my time and limited knowledge (i need people who know more about building these roms) a simple zip file to be flashed through cwm. most builds use a base version, then have roms and etc over the top of them. so there must be a way to find a base version you like for any i9100, flash over cwm, then flash a "kernal" of sorts that "adds in or takes out" what is needed for android to run on our t989.
any thoughts? anyone want to discuss this? i have the time (as much as possible, my gf keeps saying "why dont you just make your own and quit bit$%ing").
also i saw a kitchen for building roms for s2 but not sure if its t989 compatible.
lets get to work, our phone is new but the i9100 is already cooking along, we can piggy back and make our phones just as awesome!

Reading from the tittle of the thread, please dont do it! Just fall back..
Sent from my SGH-T989 using XDA App

So I understand you're not going to try to flash it but you're wrong about the major hurdle: Its the different processor. Since we have different hardware we're not talking about a slightly different radio, we're talking about two completely different devices branded as the same thing.

i realize its hardware, but isn't that all controlled by the kernal? it holds the drivers. it would be like "porting" take a rom everyone loves, make the hardware drivers work, then flash. like i said i'm limited knowledge but i want to start work on this. its a hardware thing i understand. but there must be something we can do to ease the process.

To sum up what Kevin said : It's like flashing a sensation rom on our sgs2...(Right?)

but sense has been ported to other non htc devices. my point is it can be done. we should talk about it and get a discussion going. i'd be more then happy to help "port" other roms that are out for s2 varients

cashyftw said:
To sum up what Kevin said : It's like flashing a sensation rom on our sgs2...(Right?)
Click to expand...
Click to collapse
kenVAN its my first and last name pushed together But yes.
letrain02 said:
but sense has been ported to other non htc devices. my point is it can be done. we should talk about it and get a discussion going. i'd be more then happy to help "port" other roms that are out for s2 varients
Click to expand...
Click to collapse
letrain02 said:
i realize its hardware, but isn't that all controlled by the kernal? it holds the drivers. it would be like "porting" take a rom everyone loves, make the hardware drivers work, then flash. like i said i'm limited knowledge but i want to start work on this. its a hardware thing i understand. but there must be something we can do to ease the process.
Click to expand...
Click to collapse
Porting sense to non-HTC phones requires massive amounts of work and open source. Yes, it is possible but whether or not its feasible is a different option. You're right that the kernel is the main difference but even so its much more work than simply adjusting the kernel since there are soooooo many differences. Cashy put it well: you're porting a ROM from effectively a Samsung device to an HTC device. The only similarities are the screen and touchwiz. If you want to give it a go, I'd wait until we have a full ODIN tar to help you recover your phone because you're going to get a few bricks.

Well good luck to us all.
got my T989 few days ago, and I find it much better than the usual i9100 that everyone have on every aspect, except for the lack of support and android development. I regret I based my decision solely on technical spec rather than checking the verity of available firmware and development.
I live and use this phone in Israel, and that stock T-mobile rom I got with it is loaded with lots of irremovable T-mobile apps. Those are irrelevant for me. But the real issue is about the RTL support. I now have to read Hebrew text backwards (taht ekil hpargarap eloh a daer ot yrT) in some text fields. And it won't let me use the mobile hotspot by saying my sim card is not supported. I can't see why it connects to the internet (it does, checked my APN settings twice and it configured right) but won't let me use that hotspot.
Can't these changes in the level of GUI be implanted from other equivalent roms as source code? Does these minor changes take so much work? Before overclocking my phone to 1.89 Ghz I would rather get the basic functions done.
And I'm willing to donate, and to help in any way to promote this project.

I tried a similar thing with my LG optimus 2x (I have model p-999 which is really t-mobile's g2x) by accident. Even though the variations are named optimus 2x and the specs are almost identical, firmwares just aren't compatible with one another.
I flashed a optimus 2x firmware (p-990) to my p999 and I bricked my phone. At this point, even clockworkmod could not recover it. I had to manually partition a t-mobile g2x recovery file one by one on DOS mode to fix this. Finding this solution was like finding a needle in a haysack. I thought there was a good chance that I flushed $400 down the drain when this happened.
So, lol I dont recommend it knowing that gs2 is even a higher price to pay. Hope this helped.

it's something that I almost gave a try and then decided to check in here to see what people say about flashing these roms.. lol. Thanks guys

Lol I actually did try to flash cm for the i9100 on this phone, but thankfully it only gave me an error and didn't actually go through with the flash. (I had literally gotten the phone the day before too lmao)

letrain02 said:
i realize its hardware, but isn't that all controlled by the kernal? it holds the drivers. it would be like "porting" take a rom everyone loves, make the hardware drivers work, then flash. like i said i'm limited knowledge but i want to start work on this. its a hardware thing i understand. but there must be something we can do to ease the process.
Click to expand...
Click to collapse
It sounds like youve got porting perfectly understood. The devs havent been able to do it, you should explain how porting works to them.

The problem is not just the kernel. The software is most likely compiled specifically for the processor. If you were talking about linux . . . it would be easy because the source code is there and you can compile it for whatever processor you want, but it seems Samsung is a a company who believes in leeching off off open source and mixing their proprietary crap in it then keeping the sources closed and giving the open source community the finger. Just look at how they handled the vertical lines screen issue. Its all about money to Samsung.

jim93 said:
It sounds like youve got porting perfectly understood. The devs havent been able to do it, you should explain how porting works to them.
Click to expand...
Click to collapse
Dude no need to be a punk, I seriously dislike people like you who make forums negative. He was asking a question and is trying to learn, which is more than some people do. Keep your negative comments to yourself. If you cant say anything nice don't say anything at all.

This thread was started in 2011, and hasn't been active in over 7 months. There is no need to bring it back from the dead to argue with someone.

Its not as impossible as it may seem(for the experienced dev) if u look in the dev section android88 has ported hellybean from the 9100. I'm learning & I've only gotten a bootloop at worse, haven't bricked yet lol.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

It is possible with a port. The thing that brocks your phone in flashing an i9100 ROM is the kernel. If you switched the kernels, you'll just have a boot loop or no boot. Flashing another devices kernel is the killer.
Sent from my Nexus 7 using xda app-developers app

letrain02 said:
i realize its hardware, but isn't that all controlled by the kernal? it holds the drivers. it would be like "porting" take a rom everyone loves, make the hardware drivers work, then flash. like i said i'm limited knowledge but i want to start work on this. its a hardware thing i understand. but there must be something we can do to ease the process.
Click to expand...
Click to collapse
Its not that easy. It the more similar to porting over a ROM for a Sony Xperia. Does that sound easy. Its just a name but inside very different
---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------
Tmogalaxys2 said:
It is possible with a port. The thing that brocks your phone in flashing an i9100 ROM is the kernel. If you switched the kernels, you'll just have a boot loop or no boot. Flashing another devices kernel is the killer.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Oh god not true at all people have already bricked their phone by flashing i9100 ROMS. Needs to be said before somebody bricks their expensive device.
---------- Post added at 10:48 PM ---------- Previous post was at 10:45 PM ----------
thefawns said:
Dude no need to be a punk, I seriously dislike people like you who make forums negative. He was asking a question and is trying to learn, which is more than some people do. Keep your negative comments to yourself. If you cant say anything nice don't say anything at all.
Click to expand...
Click to collapse
Its just logic. If its that easy try it and youll learn the inside out of why. Put in a similar amount effort you are asking the dev to put in by learning something about the challenges you are asking the dev to overcome instead of assuming devs arent putting enough thought into it

jim93 said:
Its not that easy. It the more similar to porting over a ROM for a Sony Xperia. Does that sound easy. Its just a name but inside very different
---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------
Oh god not true at all people have already bricked their phone by flashing i9100 ROMS. Needs to be said before somebody bricks their expensive device.
---------- Post added at 10:48 PM ---------- Previous post was at 10:45 PM ----------
Its just logic. If its that easy try it and youll learn the inside out of why. Put in a similar amount effort you are asking the dev to put in by learning something about the challenges you are asking the dev to overcome instead of assuming devs arent putting enough thought into it
Click to expand...
Click to collapse
i9100 roms port fine to t989 if you know what your doing. Getting BT to work is being a pita for me though

ThdDude said:
i9100 roms port fine to t989 if you know what your doing. Getting BT to work is being a pita for me though
Click to expand...
Click to collapse
Where are these ports?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

[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] Frame Drops, Not at All like "Butter"

So, normally help is plentiful on the Nexus S forums and I thought that here would be even better due to the devices popularity.
So far no matter where what or who the post is for or at, I have gotten no help from this community in any threads, for any issues I have encountered: I am not saying anything here to be a sarcastic idiot, but I am just hoping that I don't get 2 million people saying "WRONG THREAD IDIOT" and then not helping me or telling me where it should be...
None the less, if there is a good soul willing to help I am currently (and always) on the latest CM10 nightly build. My problem is that regardless of which version, or whatever I do, after about 4~ hours of the phone being on (used or not) it becomes very very.... low frame-y. Normally when the phone first re-boots it is smooth as butter and excellent, much like my old Nexus S yet unlike my Nexus S, it then begins to get worse as each hour passes.
It does NOT get slow.... apps take the same amount of time to load, and the phone feels as quick, yet the problem is it looks as if it is running at 5 frames a second. (This happens no matter the build and regardless of what is flashed with the ROM, but often times all I flash on top is just the GAPPS) This problem never existed on my older phones, and I really wish I could get some help for it.
Thanks guys, Eric.

I don't run that ROM so no idea if it would help but have you tried another kernel? Or tried changing governor's or scheduler
Sent from my SGH-I747 using Tapatalk 2

jasvncnt1 said:
I don't run that ROM so no idea if it would help but have you tried another kernel? Or tried changing governor's or scheduler
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I have tried other kernels and same thing happens sadly. I will give the performance schedule a try though.

Damn. Sorry. You have these issues even after a full wipe?
Sent from my SGH-I747 using Tapatalk 2

LGIQEXPO said:
So, normally help is plentiful on the Nexus S forums and I thought that here would be even better due to the devices popularity.
So far no matter where what or who the post is for or at, I have gotten no help from this community in any threads, for any issues I have encountered: I am not saying anything here to be a sarcastic idiot, but I am just hoping that I don't get 2 million people saying "WRONG THREAD IDIOT" and then not helping me or telling me where it should be...
None the less, if there is a good soul willing to help I am currently (and always) on the latest CM10 nightly build. My problem is that regardless of which version, or whatever I do, after about 4~ hours of the phone being on (used or not) it becomes very very.... low frame-y. Normally when the phone first re-boots it is smooth as butter and excellent, much like my old Nexus S yet unlike my Nexus S, it then begins to get worse as each hour passes.
It does NOT get slow.... apps take the same amount of time to load, and the phone feels as quick, yet the problem is it looks as if it is running at 5 frames a second. (This happens no matter the build and regardless of what is flashed with the ROM, but often times all I flash on top is just the GAPPS) This problem never existed on my older phones, and I really wish I could get some help for it.
Thanks guys, Eric.
Click to expand...
Click to collapse
This is why nightlies are Alpha builds. Random bugs and things happen.
As for the lack of help. You got to remember this is a development forum. Not a support forum. I see no mention of a logcat, things you have done to troubleshoot the issue. These things need to be done before opening a new thread

zelendel said:
This is why nightlies are Alpha builds. Random bugs and things happen.
As for the lack of help. You got to remember this is a development forum. Not a support forum. I see no mention of a logcat, things you have done to troubleshoot the issue. These things need to be done before opening a new thread
Click to expand...
Click to collapse
Nightlies are Alpha builds, yes. But how come my single core 1ghz Nexus S handles them nicer then my brand new dual core S3.
Also, This section on the forums is the "Q&A, Help & Troubleshooting" section is it not? In the equal forum over for the Nexus S, I got help from people as busy as the ROM makers them self. Here, barely even random people come on unless it is to say that I posted in the wrong section. As for a log cat, most every issue I have ever had ever with software has been resolved by something very simply, and only twice in my life was a log cat needed. Of those two times a log cat did not help in fixing the problem I had.
Man, I don't mean to sound mad here this is just my honest experience so far. I am very used to coming to XDA with a problem and leaving with the solution I guess. That and well I am a tad mad my phone is doing this. So please, don't take offense.

jasvncnt1 said:
Damn. Sorry. You have these issues even after a full wipe?
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yes I do, I also tried the stable releases of CM and the same problem persists sadly.

zelendel said:
This is why nightlies are Alpha builds. Random bugs and things happen.
As for the lack of help. You got to remember this is a development forum. Not a support forum. I see no mention of a logcat, things you have done to troubleshoot the issue. These things need to be done before opening a new thread
Click to expand...
Click to collapse
Nice to see you here Zel!
LGIQEXPO said:
Nightlies are Alpha builds, yes. But how come my single core 1ghz Nexus S handles them nicer then my brand new dual core S3.
Also, This section on the forums is the "Q&A, Help & Troubleshooting" section is it not? In the equal forum over for the Nexus S, I got help from people as busy as the ROM makers them self. Here, barely even random people come on unless it is to say that I posted in the wrong section. As for a log cat, most every issue I have ever had ever with software has been resolved by something very simply, and only twice in my life was a log cat needed. Of those two times a log cat did not help in fixing the problem I had.
Man, I don't mean to sound mad here this is just my honest experience so far. I am very used to coming to XDA with a problem and leaving with the solution I guess. That and well I am a tad mad my phone is doing this. So please, don't take offense.
Click to expand...
Click to collapse
The Nexus S will work better in SOME situations because those that build CM for it have ALL the needed drivers and such since it is a NATIVE ASOP firmware. The problems with any other device (specifically Samsung decices) is that Samsung doesn't share MANY of the hardware drivers and such for important things. So those that build for Samsung devices have to try and tweak things differently to make them work. That is why CM has nightly builds, sometimes with minor advancements in their tweaking and other times major advances. It takes the devs longer to work it out things.
Sent from my SAMSUNG-SGH-I747 using xda premium

As stated above. The nexus hardware was made to work with the open source files and drivers of AOSP. As OEM branded devices have their own closed sourced drivers. With the open source ones work? Yes but not as well.
Wayne Tech S-III

zelendel said:
As stated above. The nexus hardware was made to work with the open source files and drivers of AOSP. As OEM branded devices have their own closed sourced drivers. With the open source ones work? Yes but not as well.
Wayne Tech S-III
Click to expand...
Click to collapse
I see. That makes more sense. So these drivers can't be brought over to other stock builds I guess?

LGIQEXPO said:
I see. That makes more sense. So these drivers can't be brought over to other stock builds I guess?
Click to expand...
Click to collapse
No because the driver rely on other files that only work with files of the same type. So OEM drivers and files or OEM files and drivers.
Wayne Tech S-III

Petition to create MIUI ROMS for Xperia S to Xiaomi

Hello, guys.
As far as you know, some time ago Xiaomi stopped supporting our device, so, basically, after official 4.1 had come out, we have to inform them about that. So, if we gather together, we can get a nice and fast ROM for our device in some time. In my opinion, it's one of the best ROMs, and I personally think that it's really important for our device. Thanks.
Here is the link:
https://www.change.org/petitions/xi...&utm_medium=twitter&utm_source=share_petition

Gallardo994 said:
Hello, guys.
As far as you know, some time ago Xiaomi stopped supporting our device, so, basically, after official 4.1 had come out, we have to inform them about that. So, if we gather together, we can get a nice and fast ROM for our device in some time. In my opinion, it's one of the best ROMs, and I personally think that it's really important for our device. Thanks.
Here is the link:
https://www.change.org/petitions/xi...&utm_medium=twitter&utm_source=share_petition
Click to expand...
Click to collapse
They simply cant support the device because of problem which could BRICK our phones. For safety reasons they discontinued support.
They cannot be blamed. They do awesome job.

electrash said:
They simply cant support the device because of problem which could BRICK our phones. For safety reasons they discontinued support.
They cannot be blamed. They do awesome job.
Click to expand...
Click to collapse
If they develop under the Offcial Kernel they don't have that problem... or am I mistaken ?!
Previous versions ran over stock kernel, over Locked Bootladers... and where simply amazing!

electrash said:
They simply cant support the device because of problem which could BRICK our phones. For safety reasons they discontinued support.
They cannot be blamed. They do awesome job.
Click to expand...
Click to collapse
That are just false pretenses. There can't be anything that can brick our phone. Let me remind you, that a firmware consists of a bunch of /system files and a kernel. They can simply take an official kernel and edit it a bit. Even if so, we can just reflash it using fastboot. One more time, there is nothing that can brick our phone.

Their main reason May be that so you would force them to reveal the changes they always to the kernel under the GPL and this company has never followed the GPL.
Wayne Tech Nexus

zelendel said:
Their main reason May be that so you would force them to reveal the changes they always to the kernel under the GPL and this company has never followed the GPL.
Wayne Tech Nexus
Click to expand...
Click to collapse
That won't help us. At least the petition can be our chance.

Your not gonna find much help here. MIUI is not respected here to begin with. Your best bet is to try their site. As MIUI is on it's way to being banned from every tech site due to their lack of following the GPL and stealing of other developers work. I wish you luck but don't hold out to hope.
Wayne Tech Nexus

Gallardo994 said:
That are just false pretenses. There can't be anything that can brick our phone. Let me remind you, that a firmware consists of a bunch of /system files and a kernel. They can simply take an official kernel and edit it a bit. Even if so, we can just reflash it using fastboot. One more time, there is nothing that can brick our phone.
Click to expand...
Click to collapse
Flash someone's else TA in your phone and you'll know Mr. Hard-Brick.
Sent from my Xperia S using Tapatalk 4

RHBH said:
Flash someone's else TA in your phone and you'll know Mr. Hard-Brick.
Sent from my Xperia S using Tapatalk 4
Click to expand...
Click to collapse
Well, he probably meant it in limits of MIUI ROMs.