Develop Bugs

[ROM] [CDMA] CM7 Gingerbread RELEASED

Update 10-5
To make steve jobs roll over in his grave, I give you CM7.
Now to make this perfectly clear.....
I did not compile the kernel.
As it is, I was NOT going to release this until I completed the kernel so that it said MY name in "about"
We clear?
JT1134 did the kernel. I updated my source to compile the same kernel. I built a more or less custom CM7 system, did my crazy thing to it, however I used one of MY systems I built on my machine.
I am saying this, because I dont like releasing **** that I feel I didnt make 100%. Alot of people are ok with this, I view it differently.
Its easy guys.
Flash using CWM.
Get CWM anyway you have to on the tab, Im going to say wipe everything first, mount system, flash the rom, then do a full wipe again, should boot. I myself had issues with initial boot up, but i realised system needed to be mounted.
3G along with everything else works.
Download BTL CM7 RIGHT HERE
Oh, the DPI is set to the 185 I like, sorry.
Changes Ill be making this week/weekend....
Adding the audio to boot animation
System UI tweaks
Kernel with MY name on it out of respect to JT1134
A second "stripped AOSP version.
Sorry it has been so long for this release, ive been running it myself for almost a week.
​
Update 9-26
Back on the game 100% right now.
I took a break as I was taking this project very personal, and that was lame.
I was having an issue with the build being stable, all based on the data partitions.
I am going to sync the latest material off the interwebs today, try a few new builds to release, I am hoping to get something out today, If the kids let me work enough.
I am going to reach out and help Boush, and JT with their build, and see if I can get help with mine, cause in the end, it's not a race, it's an open source community.
I am building one right now, so we will see how it goes, I am down to only 1 tab right now, and while it is the Sprint model, i caqnt test 3g till i get my verizon one back from samsung.
After I am done with CM7, I will probably sell 3 of the tabs off, and switch over to writing workflows.
I, am tired.
So, before I get to the dirty details everyone wants, the more important stuff up front.
Spacemoose.
A friend, my pal, my Yoda. None of this, hell none of my roms would be here if it wasnt for him. He helped in so many ways, almost all ways up until the end. I hope next week is better for you.
Technomancer.
For the code, the answers, the help, the help you gave Dan, and then me when i picked this back up. Still trying to reach you via GTalk, however, you to are another major help, if not the reason i have the ability to build this stuff.
=================================================
CyanogenMod7 for Galaxy Tab CDMA {SPRINT AND VERIZON}
I dont know where to start, this is kind of a big thing, bigger than the 2 GB roms i did.
This is built from source, based on the GSM source with many many tweaks, including tweaks I had to do last night, and even today to get it to run for 5 minutes on my tab.
This is Alpha build quality, what can you expect, let me tell you..
This is not daily driver material.
This may, or may not run for more than 5 minutes, though I do have a streak of 60 minutes today.
However it boots, and loads the OS, and allows navigating throughout the system, but can and probably will randomly reboot.
I know what the issue is, it is kernel level, I know exactly what it is, and will be all over it tomorrow starting 6am cst.
Whats Working.
?? good question, never took time to try stuff
Launcher Pro if installed via ADB
Whats Broken.
ADW Launcher (touch calibration is jacked up from ADW)
Calibration? (had to edit build prop to rotate screen 180 so launcher pro would register my touch properly.
I have run through the system today a few times till i ran the battery down, and it worked, no idea on 3G or wifi as at that time I was worried about basic functionality.
Stages of work....
Effect tomorrow I will build a few new kernels, including a new one that should place CM7 directly onto the SD card, test those out, and get that patch done I need to. I do feel that patch is 98% of the problem.
I will then address any bug reports, start a list in another reply i will save, and cross off each one as fixed to eliminate future confusion.
There may be nightlies depending on how much I can accomplish in a 16 hour day.
This will be stable, and perfect. Has to be, it's CM7
Instructions for installation.
Flashing zip via CWM
Place on SD card, wipe everything, then choose zip, flash, and for good measure, wipe again after the flash.
Flashing with Heimdall
Ill release a heimdall version tomorrow by noon.
Make sure to wipe data, cache, dalvik, fix permissions, just run with it, better to be safe, than sorry.
Links
Download Link for Flashable Zip
Reboot and enjoy for as long as you can, I can not test how it runs on other tabs vs my daily driver right now.
CM7 Source.....
Let me finish this alpha to a stable beta, organise my source's, make sure all my patches are in, and I will be more than happy to put it all up on my Github. Placing my current source up right now, might cause problems. I will also post instructions like Technomancer did. Yall know i love to edit my posts, lol so check back often.
If you like my work, feel free to donate.
....​

Placeholder

2nd placeholder

3rd placeholder, and where I will be putting all sources, instructions, and patch information at.
Man....I am exhausted big time.

You are my personal Hero!

Not to thread jack but do happen to have a backup of kernel.org?
Sent from my SCH-I800 using xda premium

Hey I sent you a email Oldmacnut. Sorry, didn't see you turned it off.
The zip you provided is broken I think. cwm says it's bad, and when i open with winrar it says unexpected end of archive.
Otherwise great work! I'm loving the support you've given verizon gtabs!

caldeio said:
Hey I sent you a email Oldmacnut. Sorry, didn't see you turned it off.
The zip you provided is broken I think. cwm says it's bad, and when i open with winrar it says unexpected end of archive.
Otherwise great work! I'm loving the support you've given verizon gtabs!
Click to expand...
Click to collapse
This os why I prefer hdimdall
Sent from my DROIDX using xda premium

I rooted my tab when it was on froyo, unrooted it when the gb update rolled out and never felt the need to root it again.
If you get cm7 on my tab, I personally promise a hefty donation from me!
I'm so thankful us Sprint users have you in our corner. I have an evo 3d and there are more roms to flash that I don't know what to do with myself and cm7 is on the horizon for that phone also. Sprint didn't get as much love for our tabs dev wise (I'm not *****ing, god knows I'm not capable of doing anything but flashing) over here.
If there's anything I can do to help shoot me a pm.
Sent from my unrooted Galaxy Tab.

Kudos! I hope this will get you closer to the Dev title!
C.

We're cheering for you man

Updated OP with more info, im sure there will be more today, and hopefully, i am crossing my fingers, a move to Beta and stability

Links updated?
Sent from my SPH-D700 using XDA App

Dev update, last one for the night.

Exciting news! Gonna be hard for me to stay focused at work today.
Sent from my SPH-D700 using XDA App

Way to go omc! Rest is a good thing.give the testers some time to run the gauntlet and have a nice organized list rather than a piece by piece fix to drive you crazy
Sent from my SCH-I510 using Tapatalk

update
.

seeing how you work, i could say "this guy is awesome"
though i haven't tried this rom...im on overcome..

Hope the dog is OK.
Sent from my SCH-I510 using xda premium

How's the dog?
Sent from my SPH-P100 using XDA App

[ROM][DEVTEAM][GSM][17/04/12]GSM GalaxyTab Honeycomb team--HoneyComb RC1 REUPLOADED!!

Hi guys!
After going through some beta stages,we finally got Honeycomb RC1,with all the Major bugs IRONED OUT. Now it's only a matter of solving the minor resolution problems
UPDATE: Application requests for the team are temporary CLOSED.
Our team is made up of :
Devs:
- Me
-cdesal
-Frussou
-diagdave
Testers:
-stevensheaven
-Nezorflame
-slimdizzy
-captain134
-Wackymix
-Phelapkell
-ani55
Stay in touch with the team! Visit our (temporary) forums at http://honeycombsgt.freebb3.com/index.php
IRC Channel for team members only: #honeycombsgt @ freenode It will be opened to the public only in release days!! Requests for help and n00b questions wil be IGNORED in developing days,remember we can ban people from the channel!
HONEYCOMB RC1 20 OCTOBER 2011
DOWNLOAD---> http://www.mediafire.com/?mv5xavv0t1bkl57
Changelog
SD automount fixed with MUSIC and GALLERY working --- thanks diagdave
3G AND GSM FIXED!! --- thanks diagdave
New RIL from Samsung sources
Setup Wizard has been re-enabled because it works
WARNING--- THIS BUILD WILL PROBABLY WIPE INTERNAL SDCARD !!
INSTALLATION GUIDE! ---> http://forum.xda-developers.com/showthread.php?t=1296330
Additional notes:
- You may occur in strange issues like red borders in windows but they are known HC sdk issues, easy to overcome, just search on google or take a look in this forum
DEVELOPEMENT STATUS: Active
Things we're working at:
New kernel,built from new sources
Smoothness increase
Better screen resolution
Minor bugs fixing
I received some requests of guides on how to make a ROM. Well,there aren't specific guides for that,but our dev mssmison wrote a porting guide recently: it's a good start for beginners Take a look at it here: http://forum.xda-developers.com/showthread.php?t=1242216
Updates soon
Dario
Credits:
Spacemoose-- without him none of this could be possible
cdesai-- our kernel guru
diagdave-- for the SD auto mount and 3G fix
All the testers team
The entire XDA community

You have at least one more tester now count me in!

I'll be a tester if you want.
Sent from my ST15i using XDA App

I could be a tester. I have another account on the forum but I must get it back, LOL. So, reply to janne.paasimaa(at)gmail.com if you have something. I will follow that topic and I will tell ya my another account later.

@ OP
Hope this catches some devs eyes. I really hope some help out with a GSM port or possibly a CM8 based on ICS when its out
PS. Its better to put the date tag at begining of topic title in short format, ie [4.10.11]

You might want to have some pre-requisites for testers otherwise the vast majority of posts to this thread will be "Me too!!!11!" posts.
The primary difference between CDMA/GSM ports is at kernel level. The only real hardware difference is in the radio, touchscreen, processor, sound etc. are all the same.

I'ld like to help with it as much as I can, I do dev on my galaxy 3 now
If really the prime comes this month and we get ics sources we can forget honeycomb(although Google will need ta keep it sumwhere else, R.I.P. android.git.kernel.org)

I will defenitly be a tester, no matter what ...

I would gladly help if you show me where I could find tutorials for developing for android so I could help out. I must add I have some good experience with C/C++ and some with C#. If you would be so kind to send me a PM with some tutorials I would gladly help

i would love to be a beta tester but i cant make a nandroid backup on kratos.. any ideas?

can't wait. I am so anxious.
thanks DEV's for all the hard work in advance!!!

I very much doubt any real devs are going to bother with HC now. Spacemoose abandoned it without notice or explanation which is a real shame as he seemed really dedicated to the cuase, and oldmacnut looks like he has given up on challenge aswell.
IMO this is now just wishful thinking. Our best bet is to wait for ICS source to drop.

I have an early port of oldmancut's latest HC release I'm uploading right now,but this evening I can't test so I'm posting it here for the braves who can test
It's based upon old kernel sources and MAY wipe internal SD as old builds. ETA: 50 minutes!

smali26 said:
can't wait. I am so anxious.
thanks DEV's for all the hard work in advance!!!
Click to expand...
Click to collapse
+1
Sent from my GT-P1000 using Tapatalk

First port attempt: http://www.multiupload.com/HMD5JTNJ8X
It could not boot,and there are possibilities it will wipe internal SD. Only for the braves

TheATHEiST said:
I very much doubt any real devs are going to bother with HC now. Spacemoose abandoned it without notice or explanation which is a real shame as he seemed really dedicated to the cuase, and oldmacnut looks like he has given up on challenge aswell.
IMO this is now just wishful thinking. Our best bet is to wait for ICS source to drop.
Click to expand...
Click to collapse
spacemoose1 he doesn't need to explain why he abandoned the project
you must know , everyone here have another life outside the XDA forum
if he got the time , we should has it along time ago , but he doesn't have the time
cheer up ,
anyways , trust me , HC is not that good , GB is away better
HC is so damn bugy lagy crap , i use gtab10.1 and i can't tell you how many lags i get per second , so how about a ported hc ? how it will be you think ?

Lets stop banging our head on closed source HC . ICS is most probably coming on 11 october in samsung unpacked google episode.

ok i did flash it..
these errors come's up afhter boot.
Gmail (proces.com.google.android.gm) stopt
moon phase pro (proces.com.daylightmap.moon.pro.android)
gun bros (proces.com.glu.android.gunbros_free)
messages (proces.com.android.mms)
after close all errors it goes to the honescreen.
menu button not working.
home and back working.
auto turn screen not working.
keyboard don't show when trying to connect with wifi.
when i push the power button ones it reboots.(normali it put off the screen only.
btw boots in 35 sec..so pretty fast
all software still working.so it did not wip anything.
i will come back with more in a while..
hope it helps a bit so far.
regards stef

Downloading, will report asap...
Edit:
Booted in a minute or so, it gave me a Welcome screen with the list of languages and the Start button, I can choose language but nothing happens when I press the button so can't move further...
Wiped again and reflashed - same result. Stuck for now...=\
Btw, when the screen goes to sleep, it sends the device into reboot after a few seconds.
2sevensheaven, how did you pass through the Welcome screen?..

i just pushed the next button en cancel..
and like u say..when the screen goes out..it reboots.
i will now try a factory reset and see what happens.

Modifying CyanogenMod 7 for Nook Color to work on the N2E

I have, for the most part, returned from my leave of absence and hopefully this time around I will be able to provide you folks with something a bit more useful.
Admittedly, this was a fairly halfhearted attempt but, hey, it's something to start with. I branched the CM7 for Nook Color source. Part of the compilation process involves running a script (system/device/bn/encore/extract-files.sh) that extracts proprietary libraries (or something?) from stock Nook Color, so I plugged in a rooted N2E instead for this step and ripped the files off of it. Some files were missing from the N2E, so I copied those over from a Nook Color. Here's a list of those files:
Code:
/system/lib/libOMX.TI.720P.Decoder.so
/system/lib/libomap_mm_library_jni.so
/system/etc/powervr.ini
/system/lib/libpvrPVR2D_FLIPWSEGL.so
/system/lib/libusc.so
/system/lib/libpvrPVR2D_FRONTWSEGL.so
/system/lib/libOpenVG.so
/system/lib/libOpenVGU.so
/system/lib/liba2dp.so
/system/lib/hw/alsa.omap3.so
/system/usr/share/alsa/init/hda
/system/usr/share/alsa/init/00main
/system/usr/share/alsa/init/help
/system/usr/share/alsa/init/default
/system/usr/share/alsa/init/info
/system/usr/share/alsa/init/test
Compilation of the franken-nook-color source went without problems.
Unfortunately although unsurprisingly, the produced userland doesn't boot. I'll keep y'all updated with my progress; this is only the very tip of the iceberk.

I have two NST so I can use one for testing your rom if you promise no to brick it very often ;-)

I have a NST that, while the 3/4's of the screen is broken, it still functions fine and I can see anything in the top right quadrant of the screen. It doesn't do anything else for me, so you're welcome to brick it in the name of experimentation.

Thanks for the offering! I am not really in need of anything just yet but should anything come up I will PM y'all.
Anyhow, I tried again but this time excluded all the missing prop files from the build by editing them out of device-vendor-blobs.mk. It still didn't work so that means we're probably going to have to find a way to actually debug it instead of using trial and error like we have been.
Maybe there is like, a serial port or something on this thing.

klausef said:
Maybe there is like, a serial port or something on this thing.
Click to expand...
Click to collapse
Yes there is a UART on the OMAP3621.
Still, it's hard to get any info out of TI since it's an OEM part.
Does anybody have a real pinout?
Actually, unless somebody has a dead Nook that you can pull the processor off it would be hard to trace.
I guess the best bet would be to look for suspicious unused pc lands.

Can you toggle the charge light gpio as a progress indicator?

You don't need anything special.
As long as you can boot a kernel, which you can, you can do all your debugging over adb. Just enable adbd in the ramdisk.
The use for a serial console is for debugging KERNEL failures.

The firsts thing you really need to work on instead of just trying to boot CM7, is a compatible NST Kernel. Without a CM7 compatible kernel as far as I know it just won't boot. Once you know the kernel works you should start work on getting /system and such to work, as far as I know the major differences between the Nook Color and the Nook Touch are the input types and display types, which means you'll have to replace the drivers with ones that actually work.

GabrialDestruir said:
The firsts thing you really need to work on instead of just trying to boot CM7, is a compatible NST Kernel. Without a CM7 compatible kernel as far as I know it just won't boot. Once you know the kernel works you should start work on getting /system and such to work, as far as I know the major differences between the Nook Color and the Nook Touch are the input types and display types, which means you'll have to replace the drivers with ones that actually work.
Click to expand...
Click to collapse
Thanks for the direction, I kind of have been seeing that getting this working isn't as trivial as swapping a few files. I've been asking on some Freenode channels about what exactly makes a kernel 'CyanogenMod compatible.' There are clearly people out there who know exactly what facilities and stuff need to be backported, but such people are hard to find. Do you have any idea where this kind of stuff is documented? The CyanogenMod wiki seems a bit sparse, although maybe I haven't been looking in the right places...
If it is of any interest to anyone:
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html
I've recompiled U-Boot to call our current N2E kernel with a new `console=[...]` parameter, and recompiled the kernel with USB serial support. I figure I should be able to plug this thing into a linux box and just use `minicom` to look at the kernel's output in this manner. I know this probably won't give too much information about userspace issues but at least hopefully it will give some info on why/if/when/where init fails.

It would be nice if a spare UART could be found directly on the board.
http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel.html said:
The USB subsystem is started rather late in the boot process, console messages printed during boot before the USB subsystem is loaded will be lost.
Click to expand...
Click to collapse

I should be more specific, it's not so much you need to make the current kernel CM7 compatible, as it is you need to make it Android Froyo Compatible, which usually involves porting features from the eclair, if you want to get specifics, try talking with people in #nookcolor or #nook-tablet on Freenode. They may be able to help point you in the right directions for porting the kernel.

Waiting for my NST to come from new continent.
Personally, I would start building original kernel source from b&n. When it works and device boots, then I would clone google repository for kernel 2.6.x and would compare its files with the files from original kernel. And then adding needed source files for booting, and needed device drivers.
I doubt I'll have free time and enough knowledge for that.
Sent from my GT-I9000 using XDA

seeing as we now have the uart http://forum.xda-developers.com/showthread.php?t=1702734 i feel its time to make a cm7 port. it would unlimit the device, and bring it into more compatible apps.

How goes it? Will fundraising speed things up by letting you concentrate more of your time on this project?

imachine said:
How goes it? Will fundraising speed things up by letting you concentrate more of your time on this project?
Click to expand...
Click to collapse
Sorry if you weren't asking me.
I don't write a single line of C code since almost twelve years. I'm a programmer in a very different environment, fact which makes me know that such a port needs a lot of dedication.
In the next weeks I'm gonna be father for the first time and this makes me set completely different goals in my life.
As far as I've understood of cyanogenmod, is that this world is made of brilliant volunteers, some accepting donations, some not. Maybe in the whole cm community, there is somebody with time and experience.
Sent from my GT-I9000 using XDA

I've been considering picking this up as a project, because I'm tired of 2.1, i would like some GB at least I doubt we will see cm9, but cm7 seems doable. I'll have to learn some to do it, but I don't see why it's not outside of reach; now that we have a serial port, and such.

tdcfpp said:
Sorry if you weren't asking me.
Click to expand...
Click to collapse
No problemas, I wasn't. I directed my message at klausef who started this thread, though anyone willing to help out would probably be beneficient from fundraising, were it to start funding a project, instead of a single developer.
If money's a problem, perhaphs starting a kickstarter (or similar) project might help out?
Donating via paypal works as well, but I don't think it's possible to allow public access to account levels in order to motivate the experience of funding, by letting people see how much the project has risen.

i can't wait to get CyanogenMod on my nook! Have you guys discovered anything new?
Cheers!

Soooo, any news? Come on, klausef, we can help! Let us know how the progress is coming along

imachine said:
Soooo, any news? Come on, klausef, we can help! Let us know how the progress is coming along
Click to expand...
Click to collapse
Bump. I've got a great use for a NST / N2E application, and the app is currently compiled for Android 2.2 only. I may not be able to get to the source (and may not be able to make it work in 2.1 even if I did!), so a NST with 2.2 would be ideal!

A new appreciation for the devs here...

For a few months I've been reading everything I can so I can make a ROM of my own. I finally started building it with ICS LI3 and I am loving every second of it...
However, today I decided I wanted to give Jelly Bean a shot... So for the last few hours I've been trying to remember "Okay, what images did I edit again?" and "Which smali file was that tweak in?" and "Where was that thread with the how to?" Basically trying to remember every little detail that I had changed and re-creating it in Jelly Bean. Then I had an epiphany of sorts. I realized "I will, pretty much, have to do this with every new update that gets released. UHG!"
So, to the developers out there who do the same for all of us, I thank you. Not only have you inspired me to try my hand at something completely new to me, but you do this every day, every update, every new OS release. Some of you for every new device.
So truly, I thank all of you.

+1

Ditto from me!
Sent from my SPH-L710 using xda app-developers app

+1
I just want to say that I too want to thank all of the Devs here at XDA. I think the time and effort they give is greatly overlooked by some. I just want to send my gratitude to everyone here who is always willing to help people like myself, those who love Android and all it offers but need some help and guidance with how to make full use of it.
Thanks again to everyone who have done so much to make my experiences with the OG Epic and now the SGS3 such a wonderful experience.
Sent from my Nexus 7 using xda premium

Tsudeily said:
For a few months I've been reading everything I can so I can make a ROM of my own. I finally started building it with ICS LI3 and I am loving every second of it...
However, today I decided I wanted to give Jelly Bean a shot... So for the last few hours I've been trying to remember "Okay, what images did I edit again?" and "Which smali file was that tweak in?" and "Where was that thread with the how to?" Basically trying to remember every little detail that I had changed and re-creating it in Jelly Bean. Then I had an epiphany of sorts. I realized "I will, pretty much, have to do this with every new update that gets released. UHG!"
So, to the developers out there who do the same for all of us, I thank you. Not only have you inspired me to try my hand at something completely new to me, but you do this every day, every update, every new OS release. Some of you for every new device.
So truly, I thank all of you.
Click to expand...
Click to collapse
I felt the same... sort of why I put off updating my ROM for so long. But I finally got around to it. The key is making notes, and using diff'ing/compare software such as UltraCompare. It makes tasks like this much much easier.
Also, if you're doing any smali editing, it will make the job much easier to always keep a stock file from the previous update laying around, so that you can compare your changes to stock, then apply them to new updates. I have thought up a number of tricks to make updating software easier, but these are probably my most valuable.

freeza said:
I felt the same... sort of why I put off updating my ROM for so long. But I finally got around to it. The key is making notes, and using diff'ing/compare software such as UltraCompare. It makes tasks like this much much easier.
Also, if you're doing any smali editing, it will make the job much easier to always keep a stock file from the previous update laying around, so that you can compare your changes to stock, then apply them to new updates. I have thought up a number of tricks to make updating software easier, but these are probably my most valuable.
Click to expand...
Click to collapse
^+13567633689643589543
Every dev has his own tricks at keeping up to date
I'm glad some people appreciate our work and THIS is why I won't stop

I've used a program called ExamDiff to see the differences between the files I need to edit. It helps sometimes.. But I've made a few mistakes and needed to decompile working mods of my own only to find out the notes I have made in it did not appear in my newly decompiled apk.. Lesson learned.
I'm glad you and freeza especially found this thread. I've followed a few of your guides that you two have generously posted for the rest of us. Those have helped me quite a bit and given me a chance to find other things that I may not have necessarily found on my own.
Thanks again guys!
clark44 said:
^+13567633689643589543
Every dev has his own tricks at keeping up to date
I'm glad some people appreciate our work and THIS is why I won't stop
Click to expand...
Click to collapse

The devs have a few tricks up their sleeves. I would assume that most of them are using some kind of version control to keep track of all their changes (and keep their sanity). Good version control probably even allows them to copy their changes to new updates pretty painlessly.
I can't speak for anyone else, but any time I start even a small project, I start a git repo for it. It makes it easy to backtrack when I screw something up.

[Q] SuperSU on TW4.3

SuperSU on TW ROMs running 4.3 (regardless of version, source of version and how you got it) is frustrating. Apps that need root do sometimes able to get root access, and most often than not wont' be able to.
YES !!! I have done more of my share of reading. And please do NOT treat users with less than 10 posts like idiots.
*** The only solution is to change between Default Access modes. Going from grant, to prompt. Doing so for some strange reasons wakes up SuperSU***
The following solutions DO NOT WORK (meaning the problem resists)
1. Flash Antenna (regardless of which, even with the one provided by OP on their threads)
2. Flash insecure kernel zip
3. Download the version form Play and Update
Hope this help any of you that are experiencing some crazy frustrations like me.
*** Not to offend anyone, but the rule of 10 post or less = No reply/post on dev. forum is beyond me ***
*** I have tried to report my experience with certain ROMs, but Nooooooooooo.... <10 amigo ***
--- One more, since I think I am going be booted because of offending Seniors Party Members. ---
Can anyone tell me the logic of formatting a partition 3 times ??? I found this ridiculously offending being an engineer myself.
I do appreciate every single one of the developers who spends countless hours to make the word "FREE" as free as possible.

@mrbackdoor
Whoa Cool down Bro. Take a deep breath. Now tell me what precise are your problems ? I got the part with SuperSU making you go Ape. But what's with Roms and 10 Wipes ? I have no Idea what you are getting at.
So about SuperSU. If that app is making you go nuts, why don't you try SuperUser by @ChainsDD ? There's also a great Superuser app from CM team. But without knowing your Rom, I won't recommend it.
Do Kindly note, some Root apps are not compatible with 4.3. So you may get weird errors. Others like Nandroid Manager have their own limitations on Root access.
P.S. - Your Current Post Count is 1. I did respond right ?

LOL... thanks man. I am positively NOT HOT
what's with Roms
>>> TW 4.3 ATT leak on Tmobile LTElessS3
>>> I was just venting the fact that a member CAN NOT post on Development Forums because he/she has less than 10 posts.
>>> That's like filling 10 forms before you are able to download a file. Similar to registration process that just drive you nut.
>>> One engineering note is wiping a partition 3 times. The wipe process before installing a new ROM.
>>> I just don't get it... Why 3 ??? "insanity according to Albert Einstein"
Superuser..But without knowing your Rom, I won't recommend it.
>>>Superuser - NOT an option, not even working
Do Kindly note, some Root apps are not compatible with 4.3. So you may get weird errors. Others like Nandroid Manager have their own limitations on Root access.
>>> YES sir. Fully understood
P.S. - Your Current Post Count is 1. I did respond right ?
>>> call me up when you want a beer... or couple shots of the good sh****

@mrbackdoor
I don't have the ATT S3 Let alone the leaked Rom so can't comment. I hate TouchWiz anyway. I don't want to comment on the rules. They are there for a reason. Yes they may be an irritant but they keep Noobs away. You my dear friend is a Newb. There's a difference.
Whoever asked you to wipe the same partition 3 times needs to get their head examined. But then I am jumping ahead without knowing full circumstances. So if you don't mind, show me the thread link.
Are you trying to get the Leaked ATT Rom with a working Root ?
Now you too sir, have been guilty as well. I need to have full problem statement, which I am sorry I have not got as yet. So can you kindly explain what precisely are you trying to do and where does SuperSU come into play ?

Ok, first, please don't assume we are all jerks who are going to belittle you or treat you horribly and then ban you from OUR playground. I personally felt it a little insulting that your first post, coming to us for help, was so defensive and presumptuous.
Yes, we want you to do as much on your own as you can. No, most of us do not consider a low post count an indicator of idiocy. We might, however, judge how much we want to help depending on the quality of your post, or any other OP by anyone. If you do your best to find your own answers, and post clearly and respectfully, it'll show.
And there absolutely are reasons for all the rules here, and no one wants to hear anyone complain about them. (And if you haven't actually read them, please do so). The 10 post rule is to prevent spammers and bots from being able to post in the most important sections. And it's just 10 posts...see you're already on your way!
So if you'd care to try starting over on a better note, here are my points regarding your issues.
There is no real benefit to formatting something more than once. This is something that apparently began with some old device where the recovery wouldn't always format correctly. So people got in the habit of wiping several times rather than the king after each time. They then spread out across xda and push this practice like gospel sometimes, even though it gives no benefit and imo shortens the life of the device. I have tried to point out to folks this is not necessary, but gave up long ago! To each his own.
Enewman found a bit of a workaround for the su issues. It's not perfect but does seem to help a little.
Find these files
/etc/install-recovery.sh
/etc/init.d/dameonsu (or similar named script)
Find this line
/system/xbin/daemonsu --auto-daemon &
Delete --auto
Reboot
Hopefully that helps. And fyi, I'm going by memory, but am pretty sure I've been fairly accurate.
But also keep in mind that it's a combo of things, you do also need the insecure kernel. And Knox is still gonna screw with it if it's not been removed.
Also, try to remember, all of this stuff is brand new to all of us. Do not expect miracles, it takes time to relearn everything for everyone. But if it's really that bad, then consider going back to an older Rom for now.
These are after all leaked builds and should not be expected to be fully functional and bug free.
Sent from my SGH-T999 using Tapatalk

Dr. and Perseus
To you both, thank you, thank you and thank you. It would have been more appropriate on the General thread. Anyhow:
Perseus
If needed, I can point you to the threads. You are kind. I do appreciate that.
Dr.
I think you know exactly what I was talking about. So to you I do apology if my post is offended. In fact, to anyone who do feel the same. My bad.
please don't assume we are all jerks who are going to belittle you or treat you horribly and then ban you from OUR playground. I personally felt it a little insulting that your first post, coming to us for help, was so defensive and presumptuous.
>>>No Sir, no way in any shapes or forms I do assume people are jerks. Like I stated before, I was just venting on the fact that the rule cripples members ability to contribute and alienates them as well.
And there absolutely are reasons for all the rules here, and no one wants to hear anyone complain about them. (And if you haven't actually read them, please do so). The 10 post rule is to prevent spammers and bots from being able to post in the most important sections. And it's just 10 posts...see you're already on your way!
>>> Understood. Complain is absolutely not my thing. If there is a way to monitor users' footprints, you will find out that I have been here for a while, and it just not my style to complain or ask unless I have read just about anything posted.
So if you'd care to try starting over on a better note, here are my points regarding your issues.
>>> Of course.
There is no real benefit to formatting something more than once.
>>> Got it. Now's that is at the core. That's exactly what I was looking for. Instead banging my head trying to understand how partitions are being formatted and the file system that is basically associated to the NIX for a long time . Basically what I posted is the workaround that I use for now.
Hopefully that helps. And fyi, I'm going by memory, but am pretty sure I've been fairly accurate.
>>> Correct.
But also keep in mind that it's a combo of things, you do also need the insecure kernel.
>>> Appreciate your time Dr.
Statement below is my initial love your developers. That has not changed. Just "kang" members that I do find .... well.... you got my drift.
"I do appreciate every single one of the developers who spends countless hours to make the word "FREE" as free as possible."
Whenever you two do find your way to America Finest City... ring me up. A few rounds on me, if not all.
Again, thanks.

mrbackdoor said:
you will find out that I have been here for a while, and it just not my style to complain or ask unless I have read just about anything posted.
Whenever you two do find your way to America Finest City... ring me up. A few rounds on me, if not all.
Click to expand...
Click to collapse
Actually your join date of May '11 is the first thing I noticed. Pretty big time Reading on your part if you didn't ask before.
I am afraid we are still missing the problem you posted for aren't we ? Or what steps Doc suggested about the leak solved your problem ?

I'm on the app most of the time, so I can't readily see post counts, join dates, junior/senior member status, etc. But anyway, thanks for the reply op. I lurked around the forums for about a year before my first post, reading and learning all I could, so I can appreciate that you seem to have done so as well!
I was slightly off earlier, when you find those files, change this:
/system/xbin/daemonsu --auto-daemon &
To this:
/system/xbin/daemonsu --daemon &
Had to go look it up again. Sorry bout that!
@Perseus71
I'm pretty sure his main issue was that root wouldn't always work. After a little while sometimes root apps will lose their root access, which can be annoying, obviously! Some have just resorted to opening and closing the app a bunch of times till it regained root.
If I'm not mistaken it's due to seLinux blocking root. And by removing auto from the script, it forces the daemon to run persistently, as opposed to just when it's called, thereby helping to retain root access.
Another workaround I read somewhere was to tell SuperSU to ignore the apps permissions, or something like that. Not positive on what they meant right now, I'll have to try and find it again to be sure.
The other part of this is the insecure kernel. This will set seLinux status from enforcing to permissive. You may have to reboot or even reflash the kernel if it doesn't change from what I hear. I've not seen this myself though.
And then there's Knox. If it's not removed it can also cause problems with root access.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
@Perseus71
I'm pretty sure his main issue was that root wouldn't always work. After a little while sometimes root apps will lose their root access, which can be annoying, obviously! Some have just resorted to opening and closing the app a bunch of times till it regained root.
If I'm not mistaken it's due to seLinux blocking root. And by removing auto from the script, it forces the daemon to run persistently, as opposed to just when it's called, thereby helping to retain root access.
Another workaround I read somewhere was to tell SuperSU to ignore the apps permissions, or something like that. Not positive on what they meant right now, I'll have to try and find it again to be sure.
The other part of this is the insecure kernel. This will set seLinux status from enforcing to permissive. You may have to reboot or even reflash the kernel if it doesn't change from what I hear. I've not seen this myself though.
And then there's Knox. If it's not removed it can also cause problems with root access.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Oh I see. Honestly on my 4.3.1 rom that I had, I never experienced this problem. Possible its related to the leaked Rom's implementation of SELINUX?

I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers. The developers do they developing, and we do modifications to make things how we want them and hopefully others enjoy it too, that's all.
To OP, we're aware this SuperSU problem was annoying, we were one of the first few dealing with non-stop before bringing the leak from AT&T and debloating it over here.
enewman17 and his infinite knowledge did some poking around in the files and found a way to make root more persistent, albeit this is a leak, and we have Samsung KNOXing at our door. Things are bound to be broken, and especially because myself and others working on the leak are not professional Android developers nor do we ever claim to be, more like hobbyists who try to learn on their own by reading, or their own personal knowledge of NIX' and shell scripting.
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder.

All
Dr. has it right about the issue (I'm pretty sure his main issue was that root wouldn't always work.). I can work around it. No biggie. Will try the recommended method.
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers.
>>> Sir, I am not angry. I did explained couple times on previous posts. I just find certain rules and their enforcers hinder members' contributions. Whether that is just saying thanks or report something back. .The process in my opinion alienates the excitement of new members who are willing to do what it takes in hope to return something back. And so I did vent about it, Probably on the wrong forum. And I did apologize. If you want we can table this offline to show you what I meant.
nor do we ever claim to be
>>> Nor did I
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder
>>> I wouldn't doubt you. I've seen your work.
>>> The point is not about developers, contributors, members. Just rules and the re-reinforcement. I personally believe any voice is constructive and beneficial. I am not a NIX person, but I do find the creation of the linux kernel and its distributions since then fascinating. Awesome technologies have been built due to the collaboration of community sharing and giving back. I am almost certain xda was also created on the same principle.

mrbackdoor said:
All
Dr. has it right about the issue (I'm pretty sure his main issue was that root wouldn't always work.). I can work around it. No biggie. Will try the recommended method.
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers.
>>> Sir, I am not angry. I did explained couple times on previous posts. I just find certain rules and their enforcers hinder members' contributions. Whether that is just saying thanks or report something back. .The process in my opinion alienates the excitement of new members who are willing to do what it takes in hope to return something back. And so I did vent about it, Probably on the wrong forum. And I did apologize. If you want we can table this offline to show you what I meant.
nor do we ever claim to be
>>> Nor did I
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder
>>> I wouldn't doubt you. I've seen your work.
>>> The point is not about developers, contributors, members. Just rules and the re-reinforcement. I personally believe any voice is constructive and beneficial. I am not a NIX person, but I do find the creation of the linux kernel and its distributions since then fascinating. Awesome technologies have been built due to the collaboration of community sharing and giving back. I am almost certain xda was also created on the same principle.
Click to expand...
Click to collapse
Glad to know we could be of assistance. Glad to clear that up with you. Feel free to post more, don't be such a lurker!