Related
I may be imagining it, but it seems like there's a steady increase of "help, I bricked my gtab" threads as people are starting to receive their woot's gtabs. Please stop and think. Have you ever done something like modding an android device before? Is it worth it?
If it ain't broken, don't try to fix it.
I currently got 2 gtabs. One I have modded the hell out of and the other I'm keeping the stock rom. What you can do is go to settings and set it to classic. The annoying weather TnT thing will go away and your gtab will work just fine. Very fast. Very sexy. Love you long time.
I beg you, please help yourself and consider just staying with the classic stock rom. I've been playing with it and I see nothing wrong with it. Works wonderfully.
One user on here came and said when he first started playing with the gtab in office depot he was expecting the worst screen ever because of all the negative reviews about the screen. But to his surprise, it turned out to be very pleasant. Why? Because people on the internet like to exaggerate.
And in this case, people really did exaggerate the unusability of the stock rom. If you're not doing aerobics and yoga with the gtab, you won't notice it. Please do yourself (and us all) a favor by not simply plunging into modding as soon as your gtab arrives. Play with the stock rom first. Make sure you set it to classic. Give it a couple days before you decide to whether put a custom rom on there or not.
Please think about what I just said. Amen.
+1 good advice!!!!!!
x2. And please read up on things like adb and nvflash BEFORE you you start modding. Imo, anyone modding their device should have these tools handy, in advance.
"adb", for example, is almost a standard requirement in other Android phone forums. But for some reason it's not stressed here - I am guilty of that as well. I think that, if you are taking the risk (and it IS a risk) to mod your device, you should have the tools to save yourself from yourself. There's a nice writeup on nvflash that I posted (and "Rev" wrote) and adb instructions are all over the place, not just here.
Thanks!
i dont understand where all the problems come from. if you do it just like the guide tells you, shouldnt it work? i havent dont it myself but ive read and reread the guides. arent they all exactly the same out of the box if there ota version is the same? is it people are just not following directions? cause its seems pretty simple to me even though i havent done it before.im planning on doing it and if i follow the directions exactly and it doesnt work, im just gonna throw it out the window.
Also, I forgot to add.
I work in a research lab. Even though I'm an engineer, I'm really the acting tech guy. As a side job, occasionally I make house calls to fix people's computer problems.
It is my experience that not-so tech savy people always manage to find problems that us techies would never find. Not only that, not-so tech savy people most of the time can't remember what they did and can't verbalize what they did. This makes it 100x harder on us techies.
You see, there are unspoken rules in the world of tech. For example, dealing with system files is risky. Deleting them is bad. Things like that. Not-so tech savy people don't know these rules and so they just stumble all over the place finding and creating problems that the tech people would never find.
What I just said above means that when you find (or create) a problem and you didn't follow the proper procedures, you're not always going to find someone that knows a solution. Why? Because the rest of us never dared to go down that dark narrow alley that you decided to run into. We don't know what's in there. And if you manage to find a 3 headed troll, how are we to know what to do since we've never been down that alley?
Take it for what it's worth. If I haven't detered you, at least have adb and nvflash ready. And make sure you know what you're doing with those.
fridge011 said:
i dont understand where all the problems come from. if you do it just like the guide tells you, shouldnt it work? i havent dont it myself but ive read and reread the guides. arent they all exactly the same out of the box if there ota version is the same? is it people are just not following directions? cause its seems pretty simple to me even though i havent done it before.im planning on doing it and if i follow the directions exactly and it doesnt work, im just gonna throw it out the window.
Click to expand...
Click to collapse
(1) Not-so tech savy people like to take short cuts for whatever reason. They also sometimes skip important steps in a procedure even though it's right there in front of them. At least one wooter has already bricked his gtab without backing up.
(2) No, they're not all exactly the same out of the box. Nothing is ever all exactly the same out of the box.
(3) Everything seems simple to me, too. But according to my experience, what seems simple to someone with experience isn't always simple to everyone else.
Just last week, I went to a woman's house to help her with computer problems. She made it sound like life and death on the phone. The only reason I tolerate her is because she might be my in law one day. Anyway, it turned out that the problem was she thought the monitor was the computer. We have explained to her over and over that it's only the monitor and that the box sitting below is the computer. Seems silly to us, but there it is.
fridge011 said:
i dont understand where all the problems come from. if you do it just like the guide tells you, shouldnt it work? i havent dont it myself but ive read and reread the guides. arent they all exactly the same out of the box if there ota version is the same? is it people are just not following directions? cause its seems pretty simple to me even though i havent done it before.im planning on doing it and if i follow the directions exactly and it doesnt work, im just gonna throw it out the window.
Click to expand...
Click to collapse
My transition from stock 3588 to tnt lite 5 now twotapsx went smooth as butter however some devices moving from other mods back down to 3588 and then to twotapsx had problems!!! The biggest issue was a confusion on using clockwork mod recovery as those who tried it with the ttx mostly found themselves semi-bricked which led to a literal borkathon . Most issues were from user error but on some cases there were oddball problems that just popped up!! So my point is that in Modding your tablets to anything other than stock you are risking a BORK but if you follow directions and have the proper backouts tools ready such as nvflash and adb you should be ok.
goodintentions said:
(1) Not-so tech savy people like to take short cuts for whatever reason. They also sometimes skip important steps in a procedure even though it's right there in front of them. At least one wooter has already bricked his gtab without backing up.
Click to expand...
Click to collapse
+100 on this one. I have a friend that I had to help with rooting her evo and Gtab, and had to ask her every step she took to make sure she actually took them. Luckily she learned early on to use Nandroid and keep a backup of the stock rom and any working roms before you switch to another one.
fridge,
I've skipped posts after yours to answer you, so I apologize if I duplicate something.
YES, if you do everything right bad things CAN happen:
1. Android is not a well-documented operating system and something you just "think" your doing it right.
2. The G-Tablet can be cranky. Unexpected things happen. The other day my pristine, perfect tab
was shut down properly. Next time I turned it on I had huge
"android.process.acore" errors and I had to fix it.
3. I don't know of anyone who has revealed themselves on this forum that thoroughly
understands the structure of the OS software on the G-Tablet. Read all the posts
on boot.img and partition structure. It really would help us all if we knew more.
4. There are a lot of good people who "help" others on this forum Most give good
advice most of the time -- but those of us that are human make mistakes once in a while.
And honestly, some helpers may not give good advice -- don't do it if you don't
understand and feel good about it.
5. Some people don't abide by good IT practices. I saw someone trying to get help
the other day that had barely gotten started with the G-Tab and already had CWM and had
tried three or four ROMS and other related software -- and had a soft-brick!
People need to move slow and check things out more carefully.
6. And some of the software posted here for your use may not even work right. I know a
couple of programs I have seen associated with lots of crashes. If a program
is listed in the threads with lots of crashes around it -- you better be careful!
I could go on for a long while further. If you REALLY read the forum and what's going
on instead of just looking for things to install, you will see these patterns.
Rev
Agreed completely with the intention of this post but I don't think the increase of people messing theirs up is due to woot just yet. I ordered one from the woot sale and i am fairly sure that it hasn't even shipped yet, the email said within 5 days. They aren't the fastest at shipping stuff.
It's probably more so just due to the dropping price in general.
People who have not done any moding of other android devices before should absoltely so slow and wait on loading whole roms until they get familiar with it and read up a lot and do their homework otherwise they will risk breaking their device.
Sent from my ACS frozen Epic
May or may not be Wooters but several *have* posted that they have recieved them.
Adding one small thing I've learned over the years: sometimes an install/upgrade/mod just doesn't take the first time. Or the second. Or the third. Patience is a key to sucess in these things. If it doesn't work the first time, come back the next day and try it again.
Repeating again: READ the forums and all the old threads. Go back and read them again.
And if you don't do backups, I have no pity for you.
iamchocho said:
Agreed completely with the intention of this post but I don't think the increase of people messing theirs up is due to woot just yet. I ordered one from the woot sale and i am fairly sure that it hasn't even shipped yet, the email said within 5 days. They aren't the fastest at shipping stuff.
Click to expand...
Click to collapse
Actually, mine from woot is due to arrive tomorrow. May be that's because I ordered mine 10 minutes after midnight.
But regardless, people need to think twice before deciding to take the plunge.
Edit.
And I'm just cranky because I just found out this morning I've been a victim of credit card fraud. Someone's been doing a lot of shopping online with my credit card. Mostly games, so I'm guessing it's some spoiled brat somewhere who got lucky at hitting random numbers and got mine.
roebeet said:
x2. And please read up on things like adb and nvflash BEFORE you you start modding. Imo, anyone modding their device should have these tools handy, in advance.
"adb", for example, is almost a standard requirement in other Android phone forums. But for some reason it's not stressed here - I am guilty of that as well. I think that, if you are taking the risk (and it IS a risk) to mod your device, you should have the tools to save yourself from yourself. There's a nice writeup on nvflash that I posted (and "The Rev" wrote) and adb instructions are all over the place, not just here.
Thanks!
Click to expand...
Click to collapse
I've been lurking on the gTab forums here for the last several days, and have been trying to absorb all of the info I can. I tend to research everything in depth before I plunge into anything. While much information is here, it is fragmented, and what is easy to follow for a developer is not as easy to follow for others. roebeet, you do the best of any I've seen, and I appreciate it. I've done a lot of searches which have helped some. I'm not new to Android (or XDA) as I have a stock Droid Incredible, but I am new to mods to Androids. I have also used Linux in the past, and modded kernels for newer drivers using cookbook approaches, so little scares me if I have enough information. I've sort of figured out how to install and use nvflash, ADB, and CWM using the various guides, but I'm missing some fundamental knowledge on WHEN and WHY I should really be prepared to use them. I've also tried to do some reading on Nandroid, but have found little pertinent to the gTab. So here goes:
1. What is the primary use of each of the following tools, nvflash, ADB, and CWM? When should I expect to have to use each of them? Are there gTab specific guides to their uses and the options for each outside of ROM installation guides, etc? Specific examples of when I should use each, and even more important, when NOT to use them, would be helpful. I've read all of the ROM, nvflash and ADB installation guides, and the various FAQs, and I understand HOW to install each of, just want to understand the best practices for each.
2. After reading a lot, it appears that having a complete backup of my particular ROM would be a good idea since partitions seem to differ even on stock gTabs. I've read posts here that refer to Titanium, and the use of ADB and CWM to do backups, and others that refer obliquely to Nandroid. What is the use of each of the above to do backups? It appears that Nandroid is a piece of CWM, but I may be mistaken. And if I install TnTlite using roebeet's guide, I'm not supposed to use CWM anyway. So how do I do a backup?
3. I plan to use my gTab as I get it, allowing it to do OTA updates only, for a few days, playing with the TNT and normal Android interfaces. I understand that a major OTA may be imminent anyway, possibly based on the leaked 3991 ROM, so my current plan is to wait for it, at least for a week or two. I plan to explore the guts of the file system carefully to fully understand the various instructions I've found here. Is there a way to safely install nvflash and ADB and explore more, or do I need to have an already rooted ROM installed on the GTab.
4. Some people recommend updated to newer or tweaked kernels. I've found the kernels, but haven't found any good step by steps on how to install them. Any links you can point to?
As an aside, I think roebeet's idea of a good wiki for this forum is a good one. The main XDA wiki is about useless. I would expect to see beginners guides to nvflash, ADB, CWM, etc.
Thanks for your help.
Jon
Suggestion. If you are going to install a ROM, pull the detailed instructions from one of the reputable Devs here, paste it into a word processor and add a check box before each step ( can use bullet tool) Then make sure you go thru one step at a time and check the box just in case you get interrupted. If you are unclear on a step ( ie clear cache) research it before you do anything.
thanks for your replies guys, it is definitely good to know that even if i do it perfectly it might still not work the 1st time. ill just nvflash it and try again. this is a really informative forum.
I think a centralized FAQ and / or Wiki is needed, for all the concerns you stated.
"How do I setup adb? What is it used for?"
"What is nvflash? How do I backup all my partitions?"
"What's the difference between clockworkmod and standard recovery? What are the pros and cons of both?"
"What are the difference ROMs available and what are their differences?"
"What is a customized kernel and why would I use it?"
"I have an error <fill in the blank> -- what do I do?"
etc etc. With potentially hundreds of Woot users about to jump into XDA, I think this would be a fantastic thing to have. Heck, it would a good thing to have for ALL of us, myself included.
It's NOT an easy task, however. I would argue that it's a very arduous task and something that would need to be ongoing. But I think it would ease some of the repeat questions here, and give new users a good guide to understand some of the basics.
lamchocho,
Wrong! The wooters are here!
And as the days go by there's going to be more.
Gonna be interesting.
Rev
jonalowe said:
I've been lurking on the gTab forums here for the last several days, and have been trying to absorb all of the info I can. I tend to research everything in depth before I plunge into anything. While much information is here, it is fragmented, and what is easy to follow for a developer is not as easy to follow for others. roebeet, you do the best of any I've seen, and I appreciate it. I've done a lot of searches which have helped some. I'm not new to Android (or XDA) as I have a stock Droid Incredible, but I am new to mods to Androids. I have also used Linux in the past, and modded kernels for newer drivers using cookbook approaches, so little scares me if I have enough information. I've sort of figured out how to install and use nvflash, ADB, and CWM using the various guides, but I'm missing some fundamental knowledge on WHEN and WHY I should really be prepared to use them. I've also tried to do some reading on Nandroid, but have found little pertinent to the gTab. So here goes:
1. What is the primary use of each of the following tools, nvflash, ADB, and CWM? When should I expect to have to use each of them? Are there gTab specific guides to their uses and the options for each outside of ROM installation guides, etc? Specific examples of when I should use each, and even more important, when NOT to use them, would be helpful. I've read all of the ROM, nvflash and ADB installation guides, and the various FAQs, and I understand HOW to install each of, just want to understand the best practices for each.
2. After reading a lot, it appears that having a complete backup of my particular ROM would be a good idea since partitions seem to differ even on stock gTabs. I've read posts here that refer to Titanium, and the use of ADB and CWM to do backups, and others that refer obliquely to Nandroid. What is the use of each of the above to do backups? It appears that Nandroid is a piece of CWM, but I may be mistaken. And if I install TnTlite using roebeet's guide, I'm not supposed to use CWM anyway. So how do I do a backup?
3. I plan to use my gTab as I get it, allowing it to do OTA updates only, for a few days, playing with the TNT and normal Android interfaces. I understand that a major OTA may be imminent anyway, possibly based on the leaked 3991 ROM, so my current plan is to wait for it, at least for a week or two. I plan to explore the guts of the file system carefully to fully understand the various instructions I've found here. Is there a way to safely install nvflash and ADB and explore more, or do I need to have an already rooted ROM installed on the GTab.
4. Some people recommend updated to newer or tweaked kernels. I've found the kernels, but haven't found any good step by steps on how to install them. Any links you can point to?
As an aside, I think roebeet's idea of a good wiki for this forum is a good one. The main XDA wiki is about useless. I would expect to see beginners guides to nvflash, ADB, CWM, etc.
Thanks for your help.
Jon
Click to expand...
Click to collapse
I'm quoting Jon's post in its entirety because he both perfectly articulates a number of my questions as well as captures my sense that after days worth of information mining on this site, I'm semi-well-informed enough to do the kind of damage that will surely add to the confusion you all seem to realize is imminent here.
I may be able to help with question 4. Buried in Clemsyn's kernel thread (52 pp!) ...
http://forum.xda-developers.com/showthread.php?t=895825
...is this:
INSTALLATION INSTRUCTIONS:
1. ROOT, Flash CWM Recovery (if you haven't done this yet)
2. Create a FULL nandroid backup (optional since its just a kernel)
3. Download a kernel of choice
4. Put the kernel on root of sd
5. Boot into Clockwork MOD recovery (either from ROM Manager or manually- hold volume up and down at same time and press power button, then select "apply sdcard: update.zip"
6. In recovery select "Install zip from sd card"
7. Select "Choose zip from sd card"
8. Navigate to the kernel file and select it
9. Let it install, it will take a few minutes...screen will go weird (black with big blue letters) then take you back to recovery.
10. Reboot phone
Click to expand...
Click to collapse
goodintentions said:
Just last week, I went to a woman's house to help her with computer problems. She made it sound like life and death on the phone. The only reason I tolerate her is because she might be my in law one day. Anyway, it turned out that the problem was she thought the monitor was the computer. We have explained to her over and over that it's only the monitor and that the box sitting below is the computer. Seems silly to us, but there it is.
Click to expand...
Click to collapse
Just a fair warning, they (the in-laws) never change.
A little note as to why we'll probably start seeing a lot of uninformed people here is because Viewsonic actually has a link to XDA on the "Favorite gTablet Apps and Resources" page of their site, which is accessible from the main G Tablet home page
It's in the developer resources section, but as everyone already knows that doesn't stop some people.
Can someone with good experiance, possible write up a 'doc', or start a thread on what n00bs can or maybe should do with various things once they for instance root them etc.? (In this instance for the gt-p5113 specifically, if you would.) sure it will be opinion, etc. but for instance I just rooted my samsung galaxy tab 2 10.1 gt-p5113 (by the excellent docs here btw, I think they worked flawlessly.) But I just do not know what to do next.....it is freshly rooted.
and by next I do not mean things to use and do WITH it....I know somewhat some of the things I want to do there, but for instance making a backup...probably a good idea, but I do not really know the best way to go about it....or installing super user...it was mentioned, but I have no clue really how, or if they were talking about another device or needing to or not. or installing a firewall or some other type of protection. I don;t know...I guess I am expecting someone to do some thinking for me, and maybe that isn;t always the best thing to do, but it'd sure help me thats for sure, because I'm sorta weary at this point and not yet comfortable messing with it, sorta and could use some verification/validation of thinking with less of the fear of bricking my tech. I literally just rooted it like 5 minutes ago.
RS-232D said:
Can someone with good experiance, possible write up a 'doc', or start a thread on what n00bs can or maybe should do with various things once they for instance root them etc.? (In this instance for the gt-p5113 specifically, if you would.) sure it will be opinion, etc. but for instance I just rooted my samsung galaxy tab 2 10.1 gt-p5113 (by the excellent docs here btw, I think they worked flawlessly.) But I just do not know what to do next.....it is freshly rooted.
and by next I do not mean things to use and do WITH it....I know somewhat some of the things I want to do there, but for instance making a backup...probably a good idea, but I do not really know the best way to go about it....or installing super user...it was mentioned, but I have no clue really how, or if they were talking about another device or needing to or not. or installing a firewall or some other type of protection. I don;t know...I guess I am expecting someone to do some thinking for me, and maybe that isn;t always the best thing to do, but it'd sure help me thats for sure, because I'm sorta weary at this point and not yet comfortable messing with it, sorta and could use some verification/validation of thinking with less of the fear of bricking my tech. I literally just rooted it like 5 minutes ago.
Click to expand...
Click to collapse
Did the root method install a custom recovery?
RS-232D said:
I literally just rooted it like 5 minutes ago.
Click to expand...
Click to collapse
It will take a little more than 5 minutes to do your research.
My experience over the years has taught me that doing your own research is far more rewarding than having someone else do it for you and hand everything to you on a plate.
You can take it at your own pace, and you will get a far more rewarding experience of your tech if you put the effort in. Not only will you learn more, but you will discover other things as you search for the answers. This is truly mind expanding stuff, but it requires effort.
And that's the point of Android I find - if you don't want to make the effort and you want someone to do everything for you then buy a product from Apple. They are the masters at making things easy...as long as you are prepared to do things their way, and not expect too much from your device.
Android is flexible and configurable, but that means thinking, exploring and discovering things yourself.
If you're not comfortable then don't do anything. Read, read and read some more until you get comfortable - then act. That is the safest way to avoid problems as well as rewarding you with knowledge and understanding.
Good luck in your quest.
acefsw said:
Did the root method install a custom recovery?
Click to expand...
Click to collapse
Uhm.....uhm......I am not thinking so.....I used a method which used Odin....I started in I think recovery mode, by holding power and volume up, then switched to volume down, and selected a recovery file that I had put on my Sdram card, it did it's thing, and now I notice I have super user capability. I then installed supersu and quickboot . And that is where I am at. Pretty much.
Mr.Anderson....ya.....I hear you, and have run with the rtfm crowd enough to grasp the concept..... but perhaps that is why the other guy after joining Iin 2012, has a thank you meter of 16 and you have one of 6 after joining 4 years ago? I am not trying to really skip the 10 billion posts of reading time exactly, or learning on my own. What I am trying to do is avoid problems I might from more experianced people who wish to share, after looking and not finding a specific post that I am sure is up to date, thag answers the issue. Frankly, I'd like for there to be a sticky on it specifically for this model. I''ll write one myself and submit it once I know enough to do it probably......but I promise, if you do not wish to help me, I won't think any less of you, or blame you. I am sure you have gained all your knowledge and earned it on your own, or if not, on this subject specifically, it wasn't any help from me, so neither you nor anyone else owe me anything.
RS-232D said:
Uhm.....uhm......I am not thinking so.....I used a method which used Odin....I started in I think recovery mode, by holding power and volume up, then switched to volume down, and selected a recovery file that I had put on my Sdram card, it did it's thing, and now I notice I have super user capability. I then installed supersu and quickboot . And that is where I am at. Pretty much.
Mr.Anderson....ya.....I hear you, and have run with the rtfm crowd enough to grasp the concept..... but perhaps that is why the other guy after joining Iin 2012, has a thank you meter of 16 and you have one of 6 after joining 4 years ago? I am not trying to really skip the 10 billion posts of reading time exactly, or learning on my own. What I am trying to do is avoid problems I might from more experianced people who wish to share, after looking and not finding a specific post that I am sure is up to date, thag answers the issue. Frankly, I'd like for there to be a sticky on it specifically for this model. I''ll write one myself and submit it once I know enough to do it probably......but I promise, if you do not wish to help me, I won't think any less of you, or blame you. I am sure you have gained all your knowledge and earned it on your own, or if not, on this subject specifically, it wasn't any help from me, so neither you nor anyone else owe me anything.
Click to expand...
Click to collapse
Ok, go in to recovery mode volume up+power and see what it loads, if it is cwm, then you can select backup, I backup to my extsd because it takes up a lot of space on internal sd, then reboot. If not, then search for install cwm on the forum. I can explain later, but am on vacation visiting the parents, so I can't guarantee how timely my response will be.
Starting a new thread here.
YES I A NEWBIE!!!
(when it comes to Android at least).
That said. Nobody has to point it out. I know where I stand and I don't know much about Android. I know quite much about Unix/Linux so that's
a start. I know some electronics. I own a Note 3 that I think is mostly the same and want to try to take it parts from there.
It's not about stealing, "kanging", code. Please see it as a journey of fun. Of learning. Making something!
Newbie or not. I think we could be a fun bunch. Since we all want to learn!
I see more want the same. So why don't we pool? Why not make a "Hello I9506!"-Rom?
It's something I want to learn. Today I don't know something. Tomorrow I will. But just the satisfaction of doing something is worth it.
So if someone is interested. Message me. Hell. All the devs where newbies once.
Some are very helpful and some are jerks. We have the whole spectrum here and met both sides. But I don't care if a "elite-dev" snorts at me.
I want to produce something. From there on? Who knows?
A quick question:
Do we have some bloatware-list we can use or it the same? Still would need it thank you
I got some strange behavior of it yesterday (yes, I rooted it and tripped Knox, knowingly). It says it doesn't have space.
Folderspace says otherwise but saw that the /system was 89% and that feels just like it needs a real good cleanup.
I need to do the same with my Note 3. There I think there are scripts, but not for this. Is it the same TouchWiz as on the '05?
I contacted the "head developer" (I think, the one that made the first post) from FoxHound Rom since they
1) Makes a really nice rom
2) Have a release it on Note 3
So I asked for some help, hints. I'm sure he answers when he sees it.
What I like is the AOSP-feel of it. I'm like all the time running, between them. Flash, flash, flash. Ok dual boot now, but not the same!
Was same on my HTC until Venom released Viper for One X. The rom of roms! Venom Team. They are damn skilled.
So you find your "fav-rom". Me I like Foxhound just because it connects the two worlds. It's aiming for the best of the both worlds. Innovative.
Granted TouchWiz as a base is stable. They have a whole stab of people working on it.
It's fun to play around with both Probam or Pac-man (as it's built on) but it has drawbacks.
I can't use my Flipcase, and on the Note the pen and then we have some bugs on it. As all the rest.
Nothing that I can't complain about, since then I should take my butt and fix them or report them at least.
Please. Report. Never complain of bugs, because they happen. It's their hobby project ffs!
I really hate people that start to "demand" or are very unfriendly in their bug reporting.
It goes the other way around as well. Sauerkraut-devs with snotty answers.
Having worked with several closed and open source projects bug-reports are good, ideas for change. You can voice.
Sometimes strongly, about a new direction you don't like but you can NEVER demand, complain. Want something that badly? Ok. Pay me.
Over the years I've been on the net (like since 1991) I've seen this circle over and over.
The circle of Open source development
1) Enormous enthusiasm. The start! The first little halting buggy rom. So proud. Full of energy.
2) Taking in own and others ideas and develop, develop, develop - this is the happy times
3) The bugs start to be complicated as the code complicates so they are not that "fun" as to implement new stuff - and here starts the spiral
4) Here it's a combo that can go two ways or together
a) Constant nagging, demanding users without positive feed back makes them think that the users are just ungrateful. Because they are.
The coding is done on spare time. You can't "demand" someone from an Open source project. You can ask, propose.
In some you can expect it holds high standards and you can sometimes question if the decision in some part is wise and made a good and sound argument.
Give an alternative. But never demand and the final decision is up to the project.
b) The coders starts to seem themselves as the best on the earth and starts to see the users as something unavoidable.
This is a big error because then they should stop releasing version and just have their own. So they stop listen to ideas, and feel that the users
are ungrateful ****heads that should just follow the path and be happy that they get some app at all.
That is the negative spiral.
The frustration and the worst scenario, a rouge programmer, that go it's own way in the project. That makes a schism. Quarrels
Either the code is then forked (parted) or the whole structure starts to fall apart in who is the leader, owner, and never-ending discussions
because everybody knows BEST. Here the users are totally ignored since the internal conflicts takes over the whole project.
5) The coders gets tired of all this. Have bugs they don't care to fix and if someone files a report or do a suggestion they get a "Do it yourself" back.
6) Abandoned code or a restructure, a new way of working and uniting, some people leave, some new joins.
Healing and a fresh start or the project dies, often with the last version full of bugs that people still use because it's still what they want.
If there is luck, an new bunch of coders take that code and start from 1
I've seen this so many times and it's always the same.
In commercial projects you try to identify when the coder comes to this frustration point, because then it's time to move him/her to something else.
Because a disgruntled and unhappy person is never good, in anything. So it goes both ways.
So how to avoid it?
Basics. Planning. Setting goals. Having a real bugtracking system. Making clear that suggestions are suggestions and have a civil tone from both ways.
And then talk, yell, have big arguments inside the group, but make a real case for it. Like having your own space, where you give proposals.
But in the end. ALWAYS RESPECT.
A round table is not a bad thing, but there has to be respect and it has to be someone that has the final word that you have enough respect
for and trust that he/she decide what he/she think is the best and accept it. Else it's a chicken-yard. Never ending back and forth.
If you can't live with it because YOUR proposal was not granted either leave in a good way or make a fork. Or be a good player and not a crybaby.
A proposal should be in the form of What, Why, Time, Benefit (and if you are mature enough - potential problems and implications).
And then have a discussion about it. Advocate your case. Have a chat in the group.
There is nothing to say that a program can't have two different versions. Sometimes an experimental branch just to test things.
Time can tell which is the best. Be humble and respectful. Have heated discussions, as I have in a current project, challenge something.
That way, you see if it holds. It's the basis of research as way.
Postulate something. Try to prove it. Find someone to disprove it. Have an argument. See if it holds else start over. Boring? Yepp.
Does it give results? Oh yes. This is how mature people work.
Especially when it comes to medicine (that is my field now). Proving something is not easy. And think of those who sit for 20 years with a problem,
try 200 ways that fails, but don't give up. Persistence towards a goal. I met a professor. She has been working with HIV for something like 20 years.
She told me how many times they thought they where close. How it looked so nice. How it looked "THIS IS THE KEY" to see that it held for that part of the virus,
but not for the other 18 mutations and that it doesn't do any real benefits compared to the disadvantages. Finding a "hook" as they thought a few years back.
That was the most promising. Because a specific "hook" in something means that you can do something that grabs it. But it failed.
Or the people working on Malaria that kills so many. It's a complicated parasite and we have been so close, so close, but not yet.
The really big big thing. Documentation. I know, this is sooo damn boring, but to write out what you are doing in this block of code
(if obvious, just one line), If more complicated, explain.
Don't over complicate.
Don't insert numbers that you forget lie *1024 or +2, use a label for that. Document!
Try to write as general code as possible. KISS! (Keep it simple, stupid).
There is this case that we always get. It's about a coder in a project. He has this subroutine. He has been writing it to "perfection". Rewriting it.
Over and over. The machine went for years. Then it called that function and it crashed. Oh the irony,
In Sweden we call code that is in total disarray for spaghetti-code, because YOU know it, can navigate, but for someone new, it's hard or impossible.
Modularize as much as possible! Can't stress this enough.
That way, even if it take a bit extra time you have "boxes" that are taking in stuff and spitting out stuff.
Example.
We need a database to store things. We chose X. We work with X and then the X is not ideal, we need to make compromises in the code.
Mend it to work with X. But we come to a point where we want and need Y. But since the code is so intertwinned with X it's a hell to change it to Y.
Making an "interface", where you define clearly, the function of the database simplified (creations etc), boils down to this:
Search for something, read that something, write (change/add/delete) that something. That is it.
So yes, you write a few more lines, but today, we don't need to count how many clock-cycles the penalty it get (as I did way back).
We have damn fast things. When Java came it was like syrup. So zzzlooooowww. People just scratched their heads.
The only thing was that it worked over platforms. Today we have computers that can run it just fine. Fluid. Our phones for instance.
Same with C++. And yes, you can still make it zzzzloooow. So it's good to have some books (I have ebooks) on functions.
Don't reinvent stuff.
A sort function is mathematical. It will not change. When I started my masters we had this "little" book called "Introductions to algorithms".
It's like 3000 pages! Written in "pseudo code" 20 years ago but still holds. I can teach why we should not use this and why we should use that.
But I have not coded since 1997 or so and so much has changed!
But an Android is a Linux in the bottom. I've worked as a Unix specialist for many years before I changed path. So I know my way around there.
I DO need to update myself. I'm honest. I can spend time in clusters. Sometimes I have personal matters that hinders me. Like most people.
But first and foremost. It has to be FUN. This is our spare time. We do this for free. It SHOULD be fun.
Writing not fun is something you get paid for. Get a specification. Do this and that.
We still need that and it can be an obstacle but it still should be a goal to want to do this.
Persistence. Ask for help. Get a no? Ask another. We all have to start from square one. That is the beauty of this in a way.
So I'm asking if someone wants to make a group and do a ROM? I want to try. We seem to be an enthusiastic bunch here right now. Let's pool!
Let's make our "Hello Worlld! I9506 rom!
So if anybody else, newbie or not, feel it would be fun, message me. Cause I will try anyway and I would love some company.
I've had "some" project leading experience, and I still sit as a bit "advisor/pain in the but".
I don't code but most probably need to start again. But I do voice advice/concern from time to time. I try to propose some solution based on experience.
Call it "meta-coding", but it can be just as important to know how to move code fast then to be able to write the lines.
"Paradigms" don't change. If you look at a language, Java, C etc. You can boil it don't to rules. And the rules are basically the same.
The syntax, how you write it, is different. Some special solutions that is unique for just one language is there.
It's a pain to work with strings of text in C but easy peasy in Perl for instance.
And if we find someone that can give us hints help. That would be kind of them. We can ask. The worst response we can get is a "no", right?
As you see I'm known to write long. "Walls of text" is something I first got a bit mad at, now I find it funny. Sure, I "chat" in a written form.
But I'm full of ideas and enthusiasm here.
I have no plans to enforce me as some "boss". We are a team. Later on, someone will lead. We are a bunch of enthusiasts.
Right now. Baby steps. At least this is how I look at things. You might look at it otherwise.
Nothing stops us from exchanging ideas, even if we don't work on the same thing? I think that is the spirit. Helping each other.
This is not an competition. I don't care if 5 people uses the rom or not. It's not about that. The next one will be cooler. But competition?
Isn't that a bit childish? People have different tastes. I like the AOSP. If my flipcase etc worked I would move from TouchWiz since I even don't use it.
My subproject that takes precedence
KNOX. I will not give up on Knox. That is my main goal right now.
It affects me personally. If we don't stop it. Stop wasting time how to circumvent the bootloader. That is irrelevant.
If not stopped NOW. We will have an S5 with a chipped version of it. Then it's too late.
I see, in some despair, people whining in the threads, but no action. Why don't 20 people start to reg at user-forums and start to spread this?
I have MY theory. You can have that. I think it's for spying. Because I can't any other reason. My employee would give me a phone.
It has no place in our phones. But whining in a thread in a special forum like XDA, where there are people who are wizards when it comes to
developing and people that want to custom their hardware doesn't do it.
We need to spread it to the forums where the "normal" users sit. That probably never noticed it's even there. The ones that ask how to change
the different levels of volume, for calls and system. The user-base. Make them understand in simple terms. Telling them that this place, where the
best people frequent, doesn't really know what it does, because Knox is more then a bootloader that you want to circumvent not to trip that "flag".
That is the only place where we can reach the masses. Make people think. NSA. Snowden. Reading my mails? Recoring my calls?
I don't know. Do you? But it's possible. Who am I to know if my provider feeds my government with data. We already feed them with positiondata.
Make people aware. Make this crowd DO SOMETHING...
[/I]
When you turn on Skype it tries to make a tunnel through in a very sneaky way to "somewhere". I see it each time I turn it on since I tap my ethernet.
My webcam is on a switch. When I Skype I turn it on. Else it's off. And aimed at the wall, if I would happen to forget to turn it off.
So they can make happy pictures. So did Hitler. I just don't buy their bull**** of security for individuals that they added a few days ago.
if I don't want to use a firewall and a viruskiller on my PC. That is my choice. If I look at the downloaded movie Intel won't blow up my CPU.
But here, if this e-fuse is true. That is a deliberate active action. Then they are destroying my property. That is not acceptable.
But to make the "whiners" do something. Damn. That takes energy.
Ok, I stop here. If someone IS interested in experimenting together, message me. I think it can be a fun journey
All the best,
Absolon (yes I got my real nick back!)
:good: Nice explanaition of your opinion and you plan!!!
Never Seen such one!!
.........Few things about me...
1. I AM A NEWBIE TOO IN ANDROID AND LINUX!!
2. I want learn more about LINUX and ANDROID
3. Everything that i know about LINUX and ANDROID i learned here from Instructions of some people( cant remember all nicks - but BIG THANKS to THEM!!! ) that are posted on XDA Forums or Googled it!! And that is not much since i can not even compile a CWM from CM source - after 2 weeks of investigation and always getting error - - i understand its not easy to do that with my less experiance!!!
4. I have a wife and 2 kids around me - so thats top priority 1 for me!
5. I do things in Android when i got time for that - thats mostly on weekends in the evening or night when wife and kids are in bed!!
6. My english is not the best!!
7. Yes of course i am interested in experimenting and learning with other interested people!!!!
8. If you can live with that 7 points before this point - you can call me a member of the ROM "Hello I9506!"
Click to expand...
Click to collapse
Cheers
absolon said:
Starting a new thread here.
YES I A NEWBIE!!!
(when it comes to Android at least).
.....
.....
......
.......
Ok, I stop here. If someone IS interested in experimenting together, message me. I think it can be a fun journey
All the best,
Absolon (yes I got my real nick back!)
Click to expand...
Click to collapse
xenix96 said:
:good: Nice explanaition of your opinion and you plan!!!
Never Seen such one!!
.........Few things about me...
1. I AM A NEWBIE TOO IN ANDROID AND LINUX!!
2. I want learn more about LINUX and ANDROID
3. Everything that i know about LINUX and ANDROID i learned here from Instructions of some people( cant remember all nicks - but BIG THANKS to THEM!!! ) that are posted on XDA Forums or Googled it!! And that is not much since i can not even compile a CWM from CM source - after 2 weeks of investigation and always getting error - - i understand its not easy to do that with my less experiance!!!
4. I have a wife and 2 kids around me - so thats top priority 1 for me!
5. I do things in Android when i got time for that - thats mostly on weekends in the evening or night when wife and kids are in bed!!
6. My english is not the best!!
7. Yes of course i am interested in experimenting and learning with other interested people!!!!
Cheers
Click to expand...
Click to collapse
DEAL!
ALL programming books starts with how to write a "Hello World!" program. That's why I thought of the name
So "Hello I9506"?
/Absie
Looks interesting, i have only build a buggy CM rom for S3 but never released it, can i join ya .
Sent from my GT-I9505 using Tapatalk
absolon said:
DEAL!
ALL programming books starts with how to write a "Hello World!" program. That's why I thought of the name
So "Hello I9506"?
/Absie
Click to expand...
Click to collapse
Yes "Hello I9506" sounds nice and the Rom Name got also a background by this way why we call it so.
cheers
Sent from my GT-I9506 using XDA Premium 4 mobile app
Hey man, i agree with your point. I'd like to help even if I own a I9505. That shouldn't be a problem though! Count me in as a developer! :good:
My I9506 is ready for testing!
A lot of being a good developer is mindset and enthusiasm. I'm sure you'll do great!
Sent from my GT-I9505 using xda app-developers app
I hope the ROM also includes support for the E330S variant....
GO young Dev's !!
@Absie
Hi, my mate.
If u need help/some knowledge in decompiling/compiling of apks and framework jar files and building yr own ROM, PM me.
I have done my ROM projects in the S2 forums and some mods in I9505.
But I'm not a C++/java programmer freak.
I didn't have time to study in this field .
Just a tiny bit of xmls, themings and smali codes here and there that I can help u.
I'm sure u can make a good ROM in this forum.
U need more "real" devs to help u in making yr own ROM.
Cheers.
You are not alone on this. if you can do a clean system dump of 4.3 for me when it released I will take on some projects for you folks
Absolon said:
She told me how many times they thought they where close. How it looked so nice. How it looked "THIS IS THE KEY" to see that it held for that part of the virus,
but not for the other 18 mutations and that it doesn't do any real benefits compared to the disadvantages. Finding a "hook" as they thought a few years back.
That was the most promising. Because a specific "hook" in something means that you can do something that grabs it. But it failed.
Or the people working on Malaria that kills so many. It's a complicated parasite and we have been so close, so close, but not yet.
Click to expand...
Click to collapse
Yup, that about sums up the majority of time I spend troubleshooting, with the answer often being something very simple that I overlooked in the beginning.
As for de-bloating, once you get familiar with what's what it can usually be done pretty quickly.
The first thing to always do is make nandroid of everything and save it your desktop just in case. Having a zip with the stock ROM handy can also save you a lot of time if you need to replace just one app.
There are four main places you have to remember when doing this:
/system/app - primary location for system apps
/data/data - where the app's data is stored
/data/app - where upgraded copies of the apps are saved
and the dalvik-cache (usually /data/dalvik-cache or /cache/dalvik-cache)
If you're using an odexed ROM you'll want to get both the .apk and .odex files at the same time. Many apps will also have two or three widget providers, etc., be sure to get all that stuff. Just keep a list of everything you've removed.
Facebook is usually the first thing I nix as it often uses ~50MB, is redundant when it's going to install itself from the market anyway, and always has way to much access to your personal information as a system app. Twitter, flickr and any other apps like that, which you don't need or want as a system app, can all go too. Some devices also ship with keyboards for every language ever created, you can get rid of any that don't apply to you.
Once you've cleaned out the easy ones take your list and open up Settings -> Apps. The apks may be gone from /system, but all their data and updates are still taking up space. So to finish removing them look under the "All" tab and when you see one hit wipe cache, wipe data & uninstall.
Now just return to the recovery so you can wipe your dalvik-cache and create another nandroid. If you want to clean even more this will give you a good checkpoint to revert back to if needed.
xHausx said:
Yup, that about sums up the majority of time I spend troubleshooting, with the answer often being something very simple that I overlooked in the beginning.
As for de-bloating, once you get familiar with what's what it can usually be done pretty quickly.
The first thing to always do is make nandroid of everything and save it your desktop just in case. Having a zip with the stock ROM handy can also save you a lot of time if you need to replace just one app.
There are four main places you have to remember when doing this:
/system/app - primary location for system apps
/data/data - where the app's data is stored
/data/app - where upgraded copies of the apps are saved
and the dalvik-cache (usually /data/dalvik-cache or /cache/dalvik-cache)
If you're using an odexed ROM you'll want to get both the .apk and .odex files at the same time. Many apps will also have two or three widget providers, etc., be sure to get all that stuff. Just keep a list of everything you've removed.
Facebook is usually the first thing I nix as it often uses ~50MB, is redundant when it's going to install itself from the market anyway, and always has way to much access to your personal information as a system app. Twitter, flickr and any other apps like that, which you don't need or want as a system app, can all go too. Some devices also ship with keyboards for every language ever created, you can get rid of any that don't apply to you.
Once you've cleaned out the easy ones take your list and open up Settings -> Apps. The apks may be gone from /system, but all their data and updates are still taking up space. So to finish removing them look under the "All" tab and when you see one hit wipe cache, wipe data & uninstall.
Now just return to the recovery so you can wipe your dalvik-cache and create another nandroid. If you want to clean even more this will give you a good checkpoint to revert back to if needed.
Click to expand...
Click to collapse
Thank you!
Right now, all we have is the original rom, that is "normal" so I gess it's "dexed". I have no clue how to make it odexed, since what I understood it makes
the whole rom smaller?
The thing that worries me is the bootloader, since we only have the one with Knox in it and I don't know how other bootloaders work or are compatible.
But that means that we are locked into SELinux, right? So until having a "Knox-free" bootloader we can't do **** when it comes to customizing roms?
Because we can't add our own kernel or is there some code that Samsung have, because I found out that Samsung had a code-repo (wow), but
not for this phone yet.
I tripped the Knox-flag when I rooted it. Found no other way really. And I don't know if this is Knox-related or something else. I noticed this on the i9505
as well. I have space but when I try to install things it says that it's out of space and can't install it. The "funny" thing is if I push the install from the webpage
of Play it installs just fine so it's seems to be something preventing it?
I don't recall if I had it before or after Knox since I tripped Knox unknowingly on my other phone before we even found out what it was.
So I need to clean it out. Yes, /system is 76% full with the original. Since all I have done so far is just rooted the phone.
If someone has an I9505, can you do
1) df -k
The partitions (not counting the sd.) on I9506 are:
The root partition (/)
/efs
/firmware-modem
/data
/persist
/system
I'm too tired to write out a good coomand, but best is to use "find" and with some -printf options and then start to hunt.
Then we can compare the phones. The special parameters for SELinux are the next step. But this is a start to see how
The SELinux special parameters part is also something that I want to see, but I want to start with this.
Btw. On my Note 3 I got an "update" of the SELinux rules. Anyone else? (Will ask in the Knox-tread as well).
That is not rooted but totally plain vanilla and I didn't even noticed that there was an update function but got "update 16".
See my post: From Knox-thread
I read and read this night, and to just condense it since I write too long anway and I'm tired. Since the bootloader
is loading an SELinux, that won't boot if it's not compared with an unique X.509 cert in every phone and see if the
loader checksums we really get an virtual environment. That is the "wrong" feel I've had I think. And I think that we need
to sit down and test some things to verify this theory. Get some programs that can do some deep probing of the hardware.
If I'm right, and they have made a VM out of the phone we should probably notice it somehow, because it's easy. I looked,
SEAndroid that NSA created is a VM with Xen.
That means that the SELinux can just run in the background with it's processes that it will never show to you and you think
you have a rooted and Knox-free phone when you never have it since the bootloader loags a SELinux and makes a sandbox.
If's perfect. Unique id on each phone. Your signature on the papers with the serial numbers which identify you as the owner.
So perfect that I could cry if I was an engineer at Samsung...
/Abs
Please make a custom ROM that works for the SHV-E330S as well
THank you very much!
sheesha_straw said:
Please make a custom ROM that works for the SHV-E330S as well
THank you very much!
Click to expand...
Click to collapse
We need to start with baby steps so a skeleton for the I9506 is the first prio.
SHV-E330S I head that before. What IS that? Can you give me details? Is that some version of the I9506?
If it is then you are most welcome to help out!
/Abs
Absolon said:
We need to start with baby steps so a skeleton for the I9506 is the first prio.
SHV-E330S I head that before. What IS that? Can you give me details? Is that some version of the I9506?
If it is then you are most welcome to help out!
/Abs
Click to expand...
Click to collapse
I think it's the Korean SK Telecom version of the i9506
It has the same LTE-A support & Snapdragon 800 processor and everything
GSMarena description of the phone
Also known as Samsung Galaxy S4 with LTE+
Available as Samsung SHV-E330S Galaxy S4 LTE-A for SK Telecom.
Inventory
First,
I need to know if it's ok that I take the Project leader role here a bit? I have sat down and identified the things we need to even start and I have some pretty good idea.
But I can only be a Project leader if you let me. If I'm allowed to spread out the work. Else we can close this. I can't do this alone. It's too much work.
But I think that the work WE can do is the base that will benefit all rom-makes. Because this is the starting point that anyone that want to make a
rom has to start from.
The difference is that I want this to be here. In the open, and not at some closed webpage. I want all to benefit from what we do.
Either we do this openly or not at all.
And so you know. There will be a bit of work. I have my Unix knowledge and I run several Linux/BSD machines at home. I did a small calculation.
I have now been playing/then having it for getting bread on the table with Unix for 23 years.
I don't know everything. Far from. Even though I been working with it that long, the part I did as a consultant was within a certain part and I never learnt
other. Simply because I was hired for knowing just that part really well.
The problem with Unix (and why I use Unix is that everything is basically Unix, even though it called differently. It would be called Unix today if it didn't
happen to be a patent fight over the NAME. The one that held the patent of the name Unix wanted money for people to use it (it might have been SCO,
they tried to get money for anything they could. Really despise that company).
So instead of paying the companies invented their own names, Sun went for SunOS and then Solaris, Hp (HP-UX), IBM (AIX) etc.
So it's hard to say that Linux is not a Unix because it's not a Unix Unix (that doesn't exist anymore) but when I say Unix I mean the whole spectrum
of very very closely related OS to it, ok? So I will sometimes say Linux and can say Unix, but I mean basically the same.
The thing with Unix is that the learning curve is steep. You install it and have a black screen with a ">". It's a bit more easy now with Ubuntu (that I hate),
but it's better for you, that never worked with it to have something to "point and click". When it comes to the real work you will have to open up a
terminal anyway and TYPE command. See it a bit as a DOS-windows in your Windows.
There is two distinct flavors though. The one is BSD and the other is the Linux, bla bla. Those two are a fork that happened long ago and you tend
to feel like a newbie again, once you sit in from of a FreeBSD after being a homie on Linux because everything is different.
There is a standard basically on how to start up things. There is now a new thing that comes more and more that should be less conservative then
what has been the case the last 20 years but that is another thing. The Linux that Android is based on has a normal "init.d"-structure and that is
where the different scripts are that start up, in an order you decide, different parts of the system, or do what ever really. They are just scripts and
could write "Hello I9506!" on the screen if you would like that.
Did you all see the post I made about the i9506?
PLEASE ALL. I need to verify this so it's not some duckup from my part but I will do a odin today to be sure
Take a look at what I wrote: http://forum.xda-developers.com/showpost.php?p=48320189&postcount=1402
Anyone here that tripped Knox? Anyone got any strange things?
We need to know this before making any attempt at all.
I don't cry wolf here. This is true. No bulltitting. I KNOW I had this.
If you look my sig, you might think I know has build a Faraday's cage around me and have a folio-hat while looking through a magnifying glass at my
monitor at a Youtube-video showing taped in a tv that was recorded by a CC-camera from a TV in the 80-ies about the (pick one):
Moon landings
Kennedy
Roswell
9/11
Ilumatnii/NWO
And I wish I where. But the phone is erratic and I really think it's tampered. Did someone get a notice with rule-updates? I didn't get it to this one
but I got it to Note 3.
-------------------------------
So in case that you let me lead the project here in the start and be able to have work that I can "assign", or I rather want to list work and have volunteers for it.
Then I can say "Ok, test that then" etc. And we have a dialog that is open and never that someone feels forced over it, ok?
We need a BASE. Something to start from and we need to see what we have so this is the inventory part. What we have, where we start.
The first step
And I need someone that can do some deep probing for me of the hardware. We need to start comparing.
Can all do a *#1234# and post it?
I have:
AP: I9506XXUAMI3
CP: I9506XXUAMHD
CSC: I9506NEEAMI1
I noticed it only works on the original "Phone app".
This is what I think we need as a base to start with.
I9505
As close stock rom as possible. Now I saw that Hotfile was closed down (did a post about it) so I hope we get
Base
I9505 - Plain vanilla rom. As close we can get
I9506 - Depends here what you have. Here I would ask if someone has an unrooted and a rooted version.
Note 3 - I have an unrooted version. Anyone has a rooted? Knox tripped? I tried to root it with that Universal thing that doesn't trip know but it hangs.
This are the things we need to start with at least. Make nandroid-backups on them. When you have them I'll prepare a space for them on my g-drive
where you can upload them and then I can start to compare them.
Also, anyone with a Knox-tripped I9506. Please PM me. I got really strange behavior and I don't know if it's Knox or something else.
The ones with Note 3, did you get an "SELinux rules upgrade #16" a few days back? I didn't see that was an option to turn them off.
As I wrote in my other thread. My I9506 started to behave real strange. REALLY strange. There are a whole bunch of programs missing.
The are gone. I have 3 icons on them in launcher but they are just not there. So what gives?
Is this only me or is this something that we all get when we trip the Knox?
After I did a clean with the CleanMaster and removed the Knox apps, I can't get into settings, so I need to try a nandroid restore or in worst case
try to install a odin-version and reroot it. Or maybe play with it unrooted for a while.
This is serious things is this Knox-flag tripped something. I talked with my provider today about this.
So an inventory! What do we have for hardware to test on?
Things to investigate - Here I start list things that any of you can do. As I said. I can't do all and I have so much IRL that I shouldn't be here at all...
Hardware
We know it's closer to Note 3 then to 05. When I look at specs it seems like the same phone.
But I need a rooted Note3 to get the app that list ALL hardware, sensors etc, to compare it. An unrooted Note 3 will not get that access.
My theoryI is that a BL from Note 3 will probably work but one from 05 will not.
But that need to be verified. And I need to see that Odin can reflash if we do something that hangs the phone. This is the risk I will take.
What is on it?
Here I could start to compare. But I need backups of the phones!
If you happen to have any personal password for your wifi, I can give my word that I will overlook it.
Besides, what do I need it for? Not like I would come home to you and hack your Wifi
So here is a list of things:
There is no source released on their webpage about the i9506 yet.
We don't have any "pre-knox" BL for this one.
Can someone check the Note 3 forum if there is some pre-knox. Did a 4.2.2 even existed or was it a 4.3 from the start?
And then backups of the partitions for comparison.
That is the first steps to even start to move this.
/Paul
Absolon said:
First,
I need to know if it's ok that I take the Project leader role here a bit? I have sat down and identified the things we need to even start and I have some pretty good idea.
But I can only be a Project leader if you let me. If I'm allowed to spread out the work. Else we can close this. I can't do this alone. It's too much work.
But I think that the work WE can do is the base that will benefit all rom-makes. Because this is the starting point that anyone that want to make a
rom has to start from.
The difference is that I want this to be here. In the open, and not at some closed webpage. I want all to benefit from what we do.
Either we do this openly or not at all.
And so you know. There will be a bit of work. I have my Unix knowledge and I run several Linux/BSD machines at home. I did a small calculation.
I have now been playing/then having it for getting bread on the table with Unix for 23 years.
I don't know everything. Far from. Even though I been working with it that long, the part I did as a consultant was within a certain part and I never learnt
other. Simply because I was hired for knowing just that part really well.
The problem with Unix (and why I use Unix is that everything is basically Unix, even though it called differently. It would be called Unix today if it didn't
happen to be a patent fight over the NAME. The one that held the patent of the name Unix wanted money for people to use it (it might have been SCO,
they tried to get money for anything they could. Really despise that company).
So instead of paying the companies invented their own names, Sun went for SunOS and then Solaris, Hp (HP-UX), IBM (AIX) etc.
So it's hard to say that Linux is not a Unix because it's not a Unix Unix (that doesn't exist anymore) but when I say Unix I mean the whole spectrum
of very very closely related OS to it, ok? So I will sometimes say Linux and can say Unix, but I mean basically the same.
The thing with Unix is that the learning curve is steep. You install it and have a black screen with a ">". It's a bit more easy now with Ubuntu (that I hate),
but it's better for you, that never worked with it to have something to "point and click". When it comes to the real work you will have to open up a
terminal anyway and TYPE command. See it a bit as a DOS-windows in your Windows.
There is two distinct flavors though. The one is BSD and the other is the Linux, bla bla. Those two are a fork that happened long ago and you tend
to feel like a newbie again, once you sit in from of a FreeBSD after being a homie on Linux because everything is different.
There is a standard basically on how to start up things. There is now a new thing that comes more and more that should be less conservative then
what has been the case the last 20 years but that is another thing. The Linux that Android is based on has a normal "init.d"-structure and that is
where the different scripts are that start up, in an order you decide, different parts of the system, or do what ever really. They are just scripts and
could write "Hello I9506!" on the screen if you would like that.
Did you all see the post I made about the i9506?
PLEASE ALL. I need to verify this so it's not some duckup from my part but I will do a odin today to be sure
Take a look at what I wrote: http://forum.xda-developers.com/showpost.php?p=48320189&postcount=1402
Anyone here that tripped Knox? Anyone got any strange things?
We need to know this before making any attempt at all.
I don't cry wolf here. This is true. No bulltitting. I KNOW I had this.
If you look my sig, you might think I know has build a Faraday's cage around me and have a folio-hat while looking through a magnifying glass at my
monitor at a Youtube-video showing taped in a tv that was recorded by a CC-camera from a TV in the 80-ies about the (pick one):
Moon landings
Kennedy
Roswell
9/11
Ilumatnii/NWO
And I wish I where. But the phone is erratic and I really think it's tampered. Did someone get a notice with rule-updates? I didn't get it to this one
but I got it to Note 3.
-------------------------------
So in case that you let me lead the project here in the start and be able to have work that I can "assign", or I rather want to list work and have volunteers for it.
Then I can say "Ok, test that then" etc. And we have a dialog that is open and never that someone feels forced over it, ok?
We need a BASE. Something to start from and we need to see what we have so this is the inventory part. What we have, where we start.
The first step
And I need someone that can do some deep probing for me of the hardware. We need to start comparing.
Can all do a *#1234# and post it?
I have:
AP: I9506XXUAMI3
CP: I9506XXUAMHD
CSC: I9506NEEAMI1
I noticed it only works on the original "Phone app".
This is what I think we need as a base to start with.
I9505
As close stock rom as possible. Now I saw that Hotfile was closed down (did a post about it) so I hope we get
Base
I9505 - Plain vanilla rom. As close we can get
I9506 - Depends here what you have. Here I would ask if someone has an unrooted and a rooted version.
Note 3 - I have an unrooted version. Anyone has a rooted? Knox tripped? I tried to root it with that Universal thing that doesn't trip know but it hangs.
This are the things we need to start with at least. Make nandroid-backups on them. When you have them I'll prepare a space for them on my g-drive
where you can upload them and then I can start to compare them.
Also, anyone with a Knox-tripped I9506. Please PM me. I got really strange behavior and I don't know if it's Knox or something else.
The ones with Note 3, did you get an "SELinux rules upgrade #16" a few days back? I didn't see that was an option to turn them off.
As I wrote in my other thread. My I9506 started to behave real strange. REALLY strange. There are a whole bunch of programs missing.
The are gone. I have 3 icons on them in launcher but they are just not there. So what gives?
Is this only me or is this something that we all get when we trip the Knox?
After I did a clean with the CleanMaster and removed the Knox apps, I can't get into settings, so I need to try a nandroid restore or in worst case
try to install a odin-version and reroot it. Or maybe play with it unrooted for a while.
This is serious things is this Knox-flag tripped something. I talked with my provider today about this.
So an inventory! What do we have for hardware to test on?
Things to investigate - Here I start list things that any of you can do. As I said. I can't do all and I have so much IRL that I shouldn't be here at all...
Hardware
We know it's closer to Note 3 then to 05. When I look at specs it seems like the same phone.
But I need a rooted Note3 to get the app that list ALL hardware, sensors etc, to compare it. An unrooted Note 3 will not get that access.
My theoryI is that a BL from Note 3 will probably work but one from 05 will not.
But that need to be verified. And I need to see that Odin can reflash if we do something that hangs the phone. This is the risk I will take.
What is on it?
Here I could start to compare. But I need backups of the phones!
If you happen to have any personal password for your wifi, I can give my word that I will overlook it.
Besides, what do I need it for? Not like I would come home to you and hack your Wifi
So here is a list of things:
There is no source released on their webpage about the i9506 yet.
We don't have any "pre-knox" BL for this one.
Can someone check the Note 3 forum if there is some pre-knox. Did a 4.2.2 even existed or was it a 4.3 from the start?
And then backups of the partitions for comparison.
That is the first steps to even start to move this.
/Paul
Click to expand...
Click to collapse
Main:
AP: I9506XXUAMHE
CP: I9506XXUAMHD
CSC: I9506VF6AMH4
It's GOOD!!!
Ap : E330sksuamg5
cp : E330sksuamg4
csc : E330ssktamg4
Hi all. I'm new here so excuse me if this has been posted many times before, but I can't find specifically what im looking for. I have an original nvidia shield tablet thats part of the recall. I just got around to filing my claim this week for a replacement and want to save my old tablet to use as a dedicated gamestreaming/set top box machine.
I'm completely new to rooting and custom ROMs and would like to know what I need to do to deactivate the kill switch. I've done research on this and found a wealth of information , but am still having difficulty putting the pieces together to figure out the process. From my understanding I believe I need to first unlock the bootloader, root the device, install a ROM (I think I want to use an old version of nvidia software such as 2 . 2 . 2 so I can still have the gamestream and controller functionality), and delete tegraOTA apk file (where do I find this? do I delete through windows? How?). This is basically the extent of my knowledge and as mentioned I feel I need to understand what programs and processes to use before diving in.
Thanks in advance. :good:
Hello all,
I just bought a Transformer Pad TF0310C (after a bunch of research it looks like it is the Best Buy exclusive version of the TF103C which unfortunately has an Intel quad core, 1gb ram, 16gb storage), I am guessing there probably are no roms, or really anything at all for this device (spent an hour or so yesterday trying to find any and all I really found were posts of people trying to figure out what this device equivalent was to try and see if the roms will work for it)? I wish I had researched a bit more before I bought it, but too little too late (it was only $85~ so no huge deal). Assuming there are no roms for it, is it possible to adapt a current rom over to this architecture?
I am familiar with linux, several programming languages (not an expert in any, but definitely know enough of each to get any job done that I have needed thus far), manipulating devices to suit my needs, etc, so I feel that if I had enough documentation and resources available I could get something going, as long as someone with more experience tells me that it is indeed at least possible. There are probably going to be quite a few more people who are going to be looking for them as well as this device is currently a "best seller" on woot.com as a refurb, so I am hoping to try and help not only myself, but possibly the community as a whole by trying to provide at least a rom for the device, if nothing else, it will be a great learning experience for me.
Thanks all!
Hello
m374llic4 said:
Hello all,
I just bought a Transformer Pad TF0310C (after a bunch of research it looks like it is the Best Buy exclusive version of the TF103C which unfortunately has an Intel quad core, 1gb ram, 16gb storage), I am guessing there probably are no roms, or really anything at all for this device (spent an hour or so yesterday trying to find any and all I really found were posts of people trying to figure out what this device equivalent was to try and see if the roms will work for it)? I wish I had researched a bit more before I bought it, but too little too late (it was only $85~ so no huge deal). Assuming there are no roms for it, is it possible to adapt a current rom over to this architecture?
I am familiar with linux, several programming languages (not an expert in any, but definitely know enough of each to get any job done that I have needed thus far), manipulating devices to suit my needs, etc, so I feel that if I had enough documentation and resources available I could get something going, as long as someone with more experience tells me that it is indeed at least possible. There are probably going to be quite a few more people who are going to be looking for them as well as this device is currently a "best seller" on woot.com as a refurb, so I am hoping to try and help not only myself, but possibly the community as a whole by trying to provide at least a rom for the device, if nothing else, it will be a great learning experience for me.
Thanks all!
Click to expand...
Click to collapse
Hi, I am in the same boat as you and was just wondering if you found anything more on this? Unfortunately, I am not a DEV at all so wouldnt be able to help you out other than perhaps testing things? I have rooted many devices and am surprised there is nothing for this one..- Thanks!
ill_caper said:
Hi, I am in the same boat as you and was just wondering if you found anything more on this? Unfortunately, I am not a DEV at all so wouldnt be able to help you out other than perhaps testing things? I have rooted many devices and am surprised there is nothing for this one..- Thanks!
Click to expand...
Click to collapse
Hey there, I have came across a few things. It looks like at least rooting is possible, it was found and tested that the process and tools to do so from the TF103C work on the TF0310C as well from a forum post I found that I had to use chromes google translate to read here : http://www.phonandroid.com/forum/comment-rooter-votre-asus-tf103c-k010-tf0310c-t101416.html I found it at work yesterday and was going to do more research but am still in the process of moving, so my evening was filled with nothing but moving boxes, lol. I will be doing more research though. I believe it is possible to install Clockworkmod recovery using the TF103C image as well, which might mean that if there are any roms for it, they might work for ours as well!
Here are a few things I found that may or may not end up being useful
http://marshmallow-rom.net/download/rom-asus-transformer-pad-tf103c/
http://forum.xda-developers.com/general/xda-assist/asus-transformer-pad-tf103c-k010-bricked-t2889843
http://forum.xda-developers.com/android/help/comprehensive-guide-unbricking-asus-t3106719
(This one, I read on another forum, can be used if you want to possibly install windows 8 on it.)
http://forum.xda-developers.com/x98-air/general/teclast-x98-air-3g-tablet-9-7-2048x1536-t2913035
Thank you for the great info. Did you end up trying anything? I was thinking about trying the tutorial from the marshmallow- rom forum but am a little nervous.
D