[Q] "Quick Launch" Settings Location - T-Mobile myTouch 4G Slide

Now, I found this once awhile ago but I can't find anything anymore on Google or XDA. My question is where are Quick Launch configurations (ie Search_Key+"Letter") stored on the data partition? I wanted to know so that I can backup that setting so I won't have to do A-Z all over again for every fresh rom install

Seriously? Nobody?

You know, I honestly have never looked into this.
I'll keep an eye out if I come across it in my works, but with some solid progress about to be made on kernel dev i'm not sure i'll see it anytime soon.
I still have to run through the code for Bulletproof again so the chance is there I may see it.
I am curious about this, and would like to learn it - so sometime after thanksgiving when I have open slots in my project sheet i'll pencil this in. Best I can do at this time.
Until then, hope you end up finding what you're looking for.

Blue6IX said:
You know, I honestly have never looked into this.
I'll keep an eye out if I come across it in my works, but with some solid progress about to be made on kernel dev i'm not sure i'll see it anytime soon.
I still have to run through the code for Bulletproof again so the chance is there I may see it.
I am curious about this, and would like to learn it - so sometime after thanksgiving when I have open slots in my project sheet i'll pencil this in. Best I can do at this time.
Until then, hope you end up finding what you're looking for.
Click to expand...
Click to collapse
For sure. I know its a file, I believe its a db file, sqlite3. I found somebody who posted something on another forum a long time ago but can't seem to find it again. I remember it being very easy. 8\

nm misread

Related

A suggestion.

Hello everyone. I want to thank you all for this site, I have learned a great deal here and appreciate all your efforts. I have a question that many new comers have asked and they have been told to go read, so thats what I will do. I want you to know tho that its very hard when you have a baby, and very little time. I also want you to know that the only times I am really productive getting somewhere with my phone is staying up till like 4 am because everyone is asleep and I have the time needed to dedicate to all this reading, trying and learning.
I am not complaining, in fact I am grateful because I am getting somewhere thanks to your help, which has been more valuable than all the help Samsung and Rogers have given me washing their hands clean and leaving me with a defective phone. My problem has not been solved just yet, but I think a 2.2.1 rom will fix my problem. Ill keep reading and trying, ill get there.
I suggest you guys have a wikipage with a table with all the roms, what versions of android they are, what kernels, modems, etc they work with ( or not work with ), bugs, features, something all in 1 page for easy access. This would make it easier for people to access information. The easier it is the more people will use them and come here, the more ideas you will have, the more testers, its a win win situation!
I have been to the pages for all the roms, some of them tell you the bluetooh voice dialing is not working, most don't, id have to go looking for my answer. I have learned that for instance it seems people do not have an issue with it with froyo 2.2.1 but again, some roms tell you in the main page its 2.2.1, others don't.
I can't grasp all the information staying up at night till 4 am. Its the only time I have. I almost had a heat attack when I thought I bricked my phone, I can't afford another one. If all the important information is right there on 1 page, like links to the usb drivers, tools, roms, kernels, everything. Have the instructions to flash. Have a table with all the roms, their versions, what versions of kernels, modems, etc, they do ( or dont ) work with. maybe even some of the table cells are clickable, for instance bugs, click on it and a window pops up with a list of them.
I know all this information is in here somewhere. Thanks to everyone for it, but it needs to be on 1 page. Please make it easier for people who are new to this. You will benefit as well as them. Looking forward to being able to use voice dialing. I think it will be working by tomorrow or after tomorrow thanks to you guys. I could have done it in a day if all the information was right there .
Thanks for reading.
Try searching.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897
I have that bookmarked. It is also a sticky in this section.
But it doesn't say for instance which ones are 2.2.1, or which ones have the terrible voice dialing over bluetooth..
I do search and end up with over 15 tabs...
I am getting by, I am just saying it could be organized better for everyones benefit. It could be made so someone who has never done this before can get it done in a couple of hours if even, without keeping asking you the same questions here. I understand why people keep asking to recommend a ROM. It is not they they do not search, not all of them anyway. Things can be better organized.
I hear what you're saying, I think it's just that within the course of a month, about 20 ROM's have been released, if not more. And no one has had time to update the wiki.
vunuts said:
I hear what you're saying, I think it's just that within the course of a month, about 20 ROM's have been released, if not more. And no one has had time to update the wiki.
Click to expand...
Click to collapse
+1
The thing is that its not just the number of ROMs, but also the number of versions that are released. It would be a real pain and an added overhead for anyone maintaining it.
Also note that most devs are working too, and doing this in their free time. The little time they have to spare is taken up for making improvements. But they do release changelogs to look into.
If anyone has time, I would suggest they take it up to create a wiki and maintain it, rather than relying or asking the devs to do it.
Try capfaq.com it has a ROM table section, and I've used it alot.
Same issues with being 100% up to date, but it's the best Rom table format I've seen.
i897 running Cognition 3.02
Madtowndave said:
Try capfaq.com it has a ROM table section, and I've used it alot.
Same issues with being 100% up to date, but it's the best Rom table format I've seen.
i897 running Cognition 3.02
Click to expand...
Click to collapse
http://www.capfaq.com/w/ROM_Table
Looks like they have updated it!
Thanks guys, I will check that table out tomorrow.
It'd be nice if there was a modem chart as well. I know there are modems in the modem thread
forum.xda-developers.com/showthread.php?t=835272
...but near as I can tell it's not up to date, or at least the first page is not up to date (ie base Cognition runs on JL1 and Andromeda on JL2, but aren't on the first page).
If anyone knows a good and current modem reference guide, please let me know.
I can't complain too much because obviously things change all the time and it's a PITA to constantly update info...I'd volunteer but I got a 2 year old and baby 2.0 due in April.
Madtowndave said:
baby 2.0 due in April
Click to expand...
Click to collapse
made me lol at the versioning of baby
diablo009 said:
made me lol at the versioning of baby
Click to expand...
Click to collapse
Yeah it's like Richter Scale difference at least 0 to 1, and 1 to 2 kids...people that have more than 2 are either really bad at birth control, Catholic, or gluttons for punishment.
distortionist said:
I want you to know tho that its very hard when you have a baby, and very little time. I also want you to know that the only times I am really productive getting somewhere with my phone is staying up till like 4 am because everyone is asleep and I have the time needed to dedicate to all this reading, trying and learning.
Click to expand...
Click to collapse
And I thought I was the only one!
Thanks pal for making my day...
Sent from my SGH-I897 using XDA App
I bricked my phone
distortionist said:
I bricked my phone
Click to expand...
Click to collapse
How? What happened?
I have no Idea what I did wrong, my goal before I started was getting voice dial over bluetooth working for me, its essential to me. It started with trying to install paragon, as per http://www.capfaq.com/w/ROM_Table mentioned above.
I was stock rogers 2.2 so I wiped it clean, and tried the update thing, it didnt work. The only step I skipped was flash to stock and the master clear since it was 2.2 recently and I did the factory wipe. It did not work but I did not brick anything just yet. I figured most people tell you to flash with the one click odin which puts stock at&t on it. I did that and the phone stopped going into download and recovery, it did not stop completely i have gone into download and recovery a few times after that but it was a battle with my phone, since it was booting, I used adt instead which worked like a charm. at&t rom was not happy on my phone, it was going into at&t reboot loops where it would just reboot the bios over and over. after trying and trying it would boot android, i was trying to fix it but each time it restarted the reboot loop would kick off. I could not go to recovery or download mode till i finally got back into the OS and used adt to tell it to go to download mode where i reflashed my stock rogers.
My phone now had at&t logo on boot before rogers, which is not that bad but i had read you can get rid of it, i tried going into download mode with the buttons but didnt try too hard, adt was easier.
I was following these instructions :
http://www.mmacleod.ca/blog/2011/01/removing-the-att-boot-screen-from-a-samsung-captivate/
it wanted me to use odin to flash a file. I used my oden 1.3, i think he says oden 1.0, I didn't think it would make a difference.
Odin started to flash and said fail. I got the screen with "android ! computer", I have been there before when I first ever tried using odin and had to fight with my phone to get to download mode at the time ( this was before at&t ever came close to the phone, i never used odin before so i probably had trouble because of inexperience ).
anyway, this time no matter what I do I cannot go to download mode, I plan on making a jig today if i find someone who sells resistors in this little town.
any help would be appreciated. I dont want to put any more roms on my phone, i just want it to work. I am worried. Ill wait till samsung releases 2.2.1 I just want my phone back to the way it was when I bought it
As the person who write most of the documentation for Team Komin (the developers who make Andromeda), I would say this would be an immense pain. copying all of our information from the website, formatting it into wiki form and then posting it would be very time consuming.
nbs11 said:
As the person who write most of the documentation for Team Komin (the developers who make Andromeda), I would say this would be an immense pain. copying all of our information from the website, formatting it into wiki form and then posting it would be very time consuming.
Click to expand...
Click to collapse
True, but once done, it would be much easier to maintain and navigate. There is going to be a lot of crossposting and people asking for insight and advice.
I'm sure we all understand the search feature in the forum, but to be honest things change topic within a thread, and where someone asks a question that is somewhat unrelated and gets a very good answer, it is not always apparent by poking through page after page of posts to find that nugget of gold. I mean, searching for 'kernel' will give literally thousands of hits. A wiki would be much better in terms of 1. Where you are starting out from 2. what you need to do what you want 3. where to find these things, and 4. maintaining updates and version revisions.
I really appreciate all the work people do here, and I have had to find everything I wanted to know the 'hard' way, but as Android grows in popularity and market percentage, more and more people are going to come here looking for this information. Pobably better to do it sooner than later.

[Rom] Ics Nexus / Sdk Port [Alpha2]

Moved Here
Also a notice to the Admins, Mods, and various users at this site:
My personal email address is not to be used to mock, insult, or otherwise argue points made on this forum. The comments made here, despite how offensive they may be interpreted, do not hold a serious tone. If you feel it necessary to send things to my personal address, please have spine to use your own return address. Please respect the fact that I do not invade your personal life by keeping my comments restricted to this site, and I only request I am granted the same common decency.​
Wow, haven't seen you in a long time. Thank you for giving this a shot! : )
RjsShadows said:
Wow, haven't seen you in a long time. Thank you for giving this a shot! : )
Click to expand...
Click to collapse
It seems that in some alternate reality it is acceptable to assume that "in your spare time" means cancel all of your plans and get used to fluorescent lighting because daylight is just the glare on your computer screen. Either way, I am downloading some 2 gigs of random ICS stuff and finally received my replacement Macbook, so between projects I will try to get something moving on this.
You rock! Subscribing.
Right now all I have is the sdk version from RootzWiki, which appears was a post of just the modified boot. I have a few Nexus4g builds that claim to work. I have a rebuilt boot image and I am trying to pack all of it together and see what happens so I know where to start.
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
Right now all I have is the sdk version from RootzWiki, which appears was a post and abandon build. I have a few Nexus4g builds that claim to work. I have a rebuilt boot image and I am trying to pack all of it together and see what happens so I know where to start.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Sick, i'm really looking forward to this. Don't overwork yourself though
twistedumbrella said:
Right now all I have is the sdk version from RootzWiki, which appears was a post and abandon build. I have a few Nexus4g builds that claim to work. I have a rebuilt boot image and I am trying to pack all of it together and see what happens so I know where to start.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
i am guessing these first ports will be very alpha due to no real software from google to work with?
Thread cleaned (and it's only a few hours old).
If you have nothing useful to say, DON'T bother posting...
the_scotsman said:
Thread cleaned (and it's only a few hours old).
If you have nothing useful to say, DON'T bother posting...
Click to expand...
Click to collapse
What did I miss? Did the angry beavers try to build another dam? I fell asleep waiting for the new mac to migrate from the old one. Now that everything is moved over I can actually load up what I have and at least move a little closer to posting actual files to play with.
Sent from my ADR6400L using Tapatalk
Real deal? Did source drop and only for you? Cause otherwise this is just another non-working SDK port.
doug piston said:
Real deal? Did source drop and only for you? Cause otherwise this is just another non-working SDK port.
Click to expand...
Click to collapse
I guess if you didn't see the previous thread, which was more or less a rick-roll youtube video that said it isn't possible to get anything running, then an understandable first reaction is to make rude comments...
But if you read the thread you are responding to, you would have seen that on the Nexus it is a working build, capable of being used as more than just a proof-of-concept. Then again, I don't expect people to read these days because they are too busy writing...
http://forum.xda-developers.com/showthread.php?t=1313337
http://forums.androidcentral.com/sprint-nexus-s-4g-rooting-roms-hacks/127806-rom-ics-sdk-port-wip.html
Best leave the developing to the developers and stop back when there is something to load up and complain about
So getting an SDK port working on a Nexus S is the same as getting it to run on the ThunderBolt?
I'm not saying it isn't possible though I highly doubt it will work. I'm saying don't call it the "Real Deal".
doug piston said:
So getting an SDK port working on a Nexus S is the same as getting it to run on the ThunderBolt?
I'm not saying it isn't possible though I highly doubt it will work. I'm saying don't call it the "Real Deal".
Click to expand...
Click to collapse
This is real ICS development, and not a prank so it is as the title says "ICS Development (Real Deal)"
And no, getting a port working on the Nexus S is not the same as getting it to work on the Thunderbolt, which is why there isn't a file in that first post yet. I think you are assuming that the only thing available is the SDK image, though, when the full system dump is out there also.
My previous statement still stands.. Why don't you go shake down some kids for their script source, and come back when there is something here to test.
thatdudebutch said:
Posting threads with no content seems ridiculous. Why not work on the port rather than type sentence after sentence of nonsense in here. Just saying.
Click to expand...
Click to collapse
You do know downloads, packing, transferring, uploading, etc do run in the background right? I remember back when threads like this rallied up support and assistance instead of whatever you call what you're doing... For the record I am waiting on a data wipe and a lot of stuff is still installing since the computer only came yesterday.
I can just toss up every little edit I test and brick phones all day long, or I can document the process and release when it hits milestones. That way I can catch input along the way and prevent a lot of wasted time.
Just swapped the boot on the posted Nexus build, changed over all the apn info, and added in all the keylayout and hardware files. Going through and finding everything that needs to be swapped for a straight port, then if it runs I will post up the progress.
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
You do know downloads, packing, transferring, uploading, etc do run in the background right? I remember back when threads like this rallied up support and assistance instead of whatever you call what you're doing... For the record I am waiting on a data wipe and a lot of stuff is still installing since the computer only came yesterday.
Click to expand...
Click to collapse
Whether you get anywhere or not, good luck
Nothing wrong with doing something just for the challenge of having said you did it and the experience.
I am glad to see someone putting some real effort into getting an ICS port going. And appreciate you posting your progress here along the way. I'm interested in seeing how you get where you get.
Good Luck
As already mentioned, this thread is for relevant discussion of the upcoming port.
If you have nothing constructive to contribute then keep it to yourself.
No *****ing and whining about the probable lack of functionality, no pestering for ETA's and no petty personal playground nonsense.
No more warnings​If this goes off topic again then there will be repercussions​.
conantroutman said:
As already mentioned, this thread is for relevant discussion of the upcoming port.
If you have nothing constructive to contribute then keep it to yourself.
No *****ing and whining about the probably lack of functionality, no pestering for ETA's and no petty personal playground nonsense.
No more warnings​If this goes off topic again then there will be repercussions​.
Click to expand...
Click to collapse
Thanks. The good news is that I have a shopping list of what has been changed to go from sdk to working port. The bad news is that I also have a project due Thursday that I need to actually spend some time with.
For anyone with the sdk build, make sure before even trying to run it that you replace all the /system/bin files that just say toolbox with real files or set up symlinks for them. Busybox also needs to be added/replaced in /system/xbin
This will get that version to where you can run logcat and see the EGL errors, but it will also be in a condition to start tweaking files to get the touchscreen running.
Sent from my ADR6400L using Tapatalk
I can't waaaaiiiitttt!!
Take as much time as you need! Your life is more important than this.
I am uploading what I have, but not because it is a huge step forward. I fixed all the commands and added the files that should fix the touchscreen, but didn't on this device.
This is still a step forward from the base build we currently have. At least typing a command no longer results in "toolbox" being displayed instead of results. I reverted everything I tested to make sure the only test changes were absolutely necessary to provide a solid base. I will post a link as soon as it is up.
Sent from my ADR6400L using Tapatalk

Custom Apps and Code

http://myreanimatedlife.blogspot.com/
Check it out. I just started it but more will come.
Also anything you would like to see ill try to put in there. I kinda wanted it to be like a book of code when it's done... Not saying it would ever get that far. But here's hoping
No particular requests here, just a big thanks for sharing knowledge!
No problem lol I know there isn't really much of anything there yet but there will be so periodically check back

KERNEL source released

So exciting
http://www.androidpolice.com/2012/0...rnel-source-code-including-that-of-the-one-v/
EDIT: http://dl4.htc.com/RomCode/Source_and_Binaries/doubleshot-gb-crc-2.6.35-f3a1982.tar.gz
Sent from my DoubleShot Lite using Tapatalk 2
ac3theone said:
so exciting
http://www.androidpolice.com/2012/0...rnel-source-code-including-that-of-the-one-v/
sent from my doubleshot lite using tapatalk 2
Click to expand...
Click to collapse
yyyyyyyyyyeeeeeeeeeeeeeeeeeeeeeessssssssssssssssssssssssss
Soo.... Does anyone think we could see some pure AOSP action now? Or someone could update the kernel for CM7? As you will see in general someone -whom I suspect is not alone - would love an AOSP ROM on our HTC Doubleshot.
Maybe this kernel isn't that good as we suppose...
Nusferatu said:
Maybe this kernel isn't that good as we suppose...
Click to expand...
Click to collapse
Well.... What did u expect? we don't have an ICS ROM in our future that we have been made aware of, and it is truly great news as this is something that has made many a dev stray away from this device - now we might be able to get CM7 stable - and others to work off of CM7 such as blahblah
Good news nevertheless
We need to get CM7 STABLE ASAP
We may be late in the running, but that doesn't mean we still can't get merged into the main tree
Nusferatu said:
Maybe this kernel isn't that good as we suppose...
Click to expand...
Click to collapse
Its worse than you thought... The source code was released a really long time ago. This is just an updated kernel, so the real reason for lack of development isn't because the source code wasn't available. :/
michaelmab88 said:
Its worse than you thought... The source code was released a really long time ago. This is just an updated kernel, so the real reason for lack of development isn't because the source code wasn't available. :/
Click to expand...
Click to collapse
Updated source is awesome though. Tried to get it earlier and couldn't - can't on shift and will be working straight until Friday afternoon so won't have a chance to try again for a few days.
Any percieved lack of development is due to people not putting any effort into it - everyone who cries about a lack of development should do something about it instead of waiting for someone else to do so.
Why come here if you don't want to get into dev, worse, come here and complain about yourself not doing anything? Kinda silly.
Whenever I see people complain about a lack of development I wonder why they would basically make fun of themselves? It gives me a laugh at their expense...
Sent from a digital distance.
Yeah i just got the source downloaded because it matches the new ota I'm running now, I've never seen what a dual core source looks like, or if I'll even be able to compile a kernel for this device, I've only compiled a few for the EVO shift, which was straight forward with a little help from my boy drob...who knows o may get it to boot ha-ha.......nope I fudged something in my toolchain It's broke....again.....LOL
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
Yeah i just got the source downloaded because it matches the new ota I'm running now, I've never seen what a dual core source looks like, or if I'll even be able to compile a kernel for this device, I've only compiled a few for the EVO shift, which was straight forward with a little help from my boy drob...who knows o may get it to boot ha-ha
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
http://dl.dropbox.com/u/62701184/arm-eabi-4.4.3.zip
That link is for the toolchain you need, i've been hosting it on dropbox for a while until I get it over to a more permanent host.
I can walk you through it later if you want.
I have it written up on how to set up your linux environment and make changes, including versioning instructions, just haven't found the time to polish off a part of it and add it to the dev reference yet.
Got a whole space reserved for the how to from start to finish on making kernels for the doubleshot, and i've already walked people through it with no kernel dev experience so if you've done it for another device it'll be a cakewalk.
I'm eating breakfast now and gotta run out to another job, and going straight from there to dodgeball practice, then work again tonight and from there right to the job i'm about to do again tomorrow this time, so tomorrow night i'm doubtless going to sleep - maybe as early as saturday evening I could go through it with you on IRC if you are interested.
Otherwise I hope to have that in the dev ref next week, work permitting.
Blue6IX said:
http://dl.dropbox.com/u/62701184/arm-eabi-4.4.3.zip
That link is for the toolchain you need, i've been hosting it on dropbox for a while until I get it over to a more permanent host.
I can walk you through it later if you want.
I have it written up on how to set up your linux environment and make changes, including versioning instructions, just haven't found the time to polish off a part of it and add it to the dev reference yet.
Got a whole space reserved for the how to from start to finish on making kernels for the doubleshot, and i've already walked people through it with no kernel dev experience so if you've done it for another device it'll be a cakewalk.
I'm eating breakfast now and gotta run out to another job, and going straight from there to dodgeball practice, then work again tonight and from there right to the job i'm about to do again tomorrow this time, so tomorrow night i'm doubtless going to sleep - maybe as early as saturday evening I could go through it with you on IRC if you are interested.
Otherwise I hope to have that in the dev ref next week, work permitting.
Click to expand...
Click to collapse
I might have my little one on Saturday night so that maybe a no go for then, the tool chain I currently have is 4.4.1, because anything newer for the speedy breaks a ton during the compile.....I changed some commands around for ****s and giggles and got a zimage in arch/arm/boot so I split it with the ota ramdisk and I'm just gonna try....if that goes south I'll setup your tool chain....thanks blue your like the DoubleShot dictionary....
Also I'm gonna grab one of your kernel zips for test flashes if that's ok
Sent from my myTouch_4G_Slide using Tapatalk 2
Blue6IX said:
Updated source is awesome though. Tried to get it earlier and couldn't - can't on shift and will be working straight until Friday afternoon so won't have a chance to try again for a few days.
Any percieved lack of development is due to people not putting any effort into it - everyone who cries about a lack of development should do something about it instead of waiting for someone else to do so.
Why come here if you don't want to get into dev, worse, come here and complain about yourself not doing anything? Kinda silly.
Whenever I see people complain about a lack of development I wonder why they would basically make fun of themselves? It gives me a laugh at their expense...
Sent from a digital distance.
Click to expand...
Click to collapse
Hey I'm not complaining, and I am working on it! I just have to balance between school and work and learning how to build cm7/cm9 from source.
You can check out a little bit of what I've been working on github.com/mafischer
michaelmab88 said:
Hey I'm not complaining, and I am working on it! I just have to balance between school and work and learning how to build cm7/cm9 from source.
You can check out a little bit of what I've been working on github.com/mafischer
Click to expand...
Click to collapse
Lol no worries my friend, was a general comment and not aimed at you in particular, just a perspective I wanted to put out there and you were the first opportunity to do so.
I still haven't found the time to get git set up and learn how to use it - that whole life getting in the way of living thing. Given you have git going that makes you a more responsible dev then I in my book -
@ strapped: all my work available is a contribution to the open source community at large, and the members of XDA in particular. If any of it can be useful, especially as a teaching tool, I wholeheartedly encourage it!
Sent from a digital distance.
Where did all of you come from?
Never knew there was this many people working on the Doubleshot in the background...
gtmaster303 said:
Where did all of you come from?
Never knew there was this many people working on the Doubleshot in the background...
Click to expand...
Click to collapse
I've been here since i preordered my doubleshot... I just haven't had time to work on much of anything, so there's no point in advertising to the community that I'm gonna work on things that may or may not ever get finished. I don't want to spread false hope or anything.
I am however, graduating in may; I'm going to be working over at walmart isd for a summer internship, and I should have more time on my hands once school is over!
How integrated is the Sense stuff into the kernel? As I understand it, we've had trouble removing the Sense underpinnings from the operating system to get it working with things such as Sixaxis. I'm aware that this is entirely a lack of understanding on my part.
I would quite love to get involved in building a ROM myself, perhaps even setting up CM9 from scratch. I just have no idea how to get started. I've mucked around with custom kernels and embedded linux (not android) devices in the past, but I'm not sure how that knowledge would apply to this system. I also have no history of proper programming languages or anything like that. I'm vaguely familiar with how to compile things with the ARM toolchains.
I'm also a tad nervous about bricking the device by writing to a memory location that I really shouldn't be touching.
Kanerix said:
How integrated is the Sense stuff into the kernel? As I understand it, we've had trouble removing the Sense underpinnings from the operating system to get it working with things such as Sixaxis. I'm aware that this is entirely a lack of understanding on my part.
I would quite love to get involved in building a ROM myself, perhaps even setting up CM9 from scratch. I just have no idea how to get started. I've mucked around with custom kernels and embedded linux (not android) devices in the past, but I'm not sure how that knowledge would apply to this system. I also have no history of proper programming languages or anything like that. I'm vaguely familiar with how to compile things with the ARM toolchains.
I'm also a tad nervous about bricking the device by writing to a memory location that I really shouldn't be touching.
Click to expand...
Click to collapse
Sorry for quoting the whole post just to address one thing, but in regards to sixaxis I'm sure it's a safe bet that if one were to simply replace the stock bluetooth stack with the one kornyone used for cm7 in my bulletproof rom it would work fine, and I doubt much other, if any modification would be necessary.
I haven't had time to try, and truthfully i'd rather build my own so am kinda intentionally not trying - I am more interested in the project then just jumping into a solution.
It really depends on what you are trying to do - some sense things can be replaced with relatively little effort, other things are so interwoven it would take considerable effort and time to unravel, reverse engineer and implement a new solution.
A lot of people have been working on different parts of unravelling sense since back in august, and around the middle of that month we got s-off and really started digging in.
There is a considerable knowledge base lurking here to address this kind of stuff if people make it known they are working on things - dig back through the history of the device here at XDA and you can catch a glimpse of it and get some direction on who you can approach when you hit a roadblock, depending on what kind of roadblock it is.
It's better for us as a community to have that kind of knowledge out on the public forum, but there's much more here then what face value suggests.
I've been trying to get that kind of stuff and a general 'start here' knowledge base built in the developers reference stickied here in dev, reading through that would be a good place to start getting oriented on devving for the dubleshot.
I just go through some crazy work cycles and sometimes can't be around much for a time here and ther, so my contributions come in groups and gaps.
Sent from a digital distance.
michaelmab88 said:
I've been here since i preordered my doubleshot... I just haven't had time to work on much of anything, so there's no point in advertising to the community that I'm gonna work on things that may or may not ever get finished. I don't want to spread false hope or anything.
I am however, graduating in may; I'm going to be working over at walmart isd for a summer internship, and I should have more time on my hands once school is over!
Click to expand...
Click to collapse
It doesn't matter whether or not you finish. Status updates would be nice though. At least that way people can know what you're up to, and they may even be able to help you and vice versa.
No one here is demanding an ETA or even a completion at all. We're all in for the fun of it.
Either way I think I can safely speak for everyone when I say, we're excited to see what you got cooking
Blue6IX said:
Sorry for quoting the whole post just to address one thing, but in regards to sixaxis I'm sure it's a safe bet that if one were to simply replace the stock bluetooth stack with the one kornyone used for cm7 in my bulletproof rom it would work fine, and I doubt much other, if any modification would be necessary.
I haven't had time to try, and truthfully i'd rather build my own so am kinda intentionally not trying - I am more interested in the project then just jumping into a solution.
It really depends on what you are trying to do - some sense things can be replaced with relatively little effort, other things are so interwoven it would take considerable effort and time to unravel, reverse engineer and implement a new solution.
A lot of people have been working on different parts of unravelling sense since back in august, and around the middle of that month we got s-off and really started digging in.
There is a considerable knowledge base lurking here to address this kind of stuff if people make it known they are working on things - dig back through the history of the device here at XDA and you can catch a glimpse of it and get some direction on who you can approach when you hit a roadblock, depending on what kind of roadblock it is.
It's better for us as a community to have that kind of knowledge out on the public forum, but there's much more here then what face value suggests.
I've been trying to get that kind of stuff and a general 'start here' knowledge base built in the developers reference stickied here in dev, reading through that would be a good place to start getting oriented on devving for the dubleshot.
I just go through some crazy work cycles and sometimes can't be around much for a time here and ther, so my contributions come in groups and gaps.
Sent from a digital distance.
Click to expand...
Click to collapse
I've been trying to go through the dev reference that you posted and track down as much scattered information as I can, but I'm still not quite sure what I'm doing. Alas.
Regarding bluetooth: would the gingerbread stack be compatible with ICS?
gtmaster303 said:
It doesn't matter whether or not you finish. Status updates would be nice though. At least that way people can know what you're up to, and they may even be able to help you and vice versa.
No one here is demanding an ETA or even a completion at all. We're all in for the fun of it.
Either way I think I can safely speak for everyone when I say, we're excited to see what you got cooking
Click to expand...
Click to collapse
Well what I'm currently up to is making a stable version of cm7 for the doubleshot. I have made lots of progress as far as learning all the tools necessary to compile android from source, which is a relatively simple task. The not so simple part is trying to put together like a puzzle, the source code from other devices. I've hit some roadblocks and I'm currently asking some devs for help, but while I'm at it I guess I can ask for help here on xda.
michaelmab88 said:
Well what I'm currently up to is making a stable version of cm7 for the doubleshot.
Click to expand...
Click to collapse
Yeehaaa!

Let's make a rom! :) (question)

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

Categories

Resources