Develop Bugs

[N2E][1.0][1.0.1] TouchNooter 1.6.24

This will officially not work for 1.1
What it does:
Enables ADB via uRamdisk
Installs su and Superuser.apk
Installs Busybox
Installs Button Savior
Installs Go Launcher
Installs NookColor Tools (To Enable Non-Market Installs)
Installs Gapps (Gmail, Market, Youtube, Others)
System Files that get Modified:
/system/build.prop - Enabling Google Check In
packages.xml - Allows Gapps to install properly.
framework.jar - Should allow a proper Android ID to generate.
Changes:
June 24, 2011 -
Removed: Multitouch Permission
Added: Modified framework.jar
June 22, 2011 - Fixed: Script not running at boot.
June 20, 2011 - Initial Release
Before you begin:
You must already have a registered Nook Simple Touch
You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
You must either have dd (Linux) or WinImage (Windows) software.
You must have an external microSDCard reader or this will not work. Do NOT use the Nook Simple Touch.
You must have enough intelligence to follow instructions.
Let's get started:
Download TouchNooter from here: touchnooter-1-6-24.zip
Linux: Unzip and use dd if=touchnooter-1-6-24.img of=/dev/sdcard
Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
Windows Alternative: https://launchpad.net/win32-image-writer/+download
Power off your Nook Simple Touch.
Insert TouchNooter SDcard into your Nook Simple Touch.
Power on your Nook Simple Touch.
You should see the screen "Rooted Forever".
It will boot like normal and you should be asked to select a launcher now. (If not use Button Savior to go home. This will bring up the launcher chooser.)
That was the hard part, now to the simple stuff.
Upon boot unlock your screen.
At the Android Welcome Screen skip Sign In.
Enable Location Services when given the option.
Connect to Wifi and launch Youtube from Go Launcher's App Drawer (Or the App Drawer of your Choice).
Click the Menu button (The right one in the middle of the status bar).
Select "My Channel" and Login using your Gmail Account.
Exit Youtube and Launch Gmail from "Extras".
Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
Enable Non-Market Installs by running the NookColor Tools App.
If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
Go to Settings > Device Info > SdCard > UnMount > Format
Thanks To:
Arnold Snarb - modified framework.jar
nemith - helping me figure out getting it to run at boot.
JesusFreke - For getting root.
MrMuffin - For the original Market Hack that we're using.
Currently Working On: TouchNooter 1.11.x

I've probably screwed up, but perhaps not too badly. Tried to follow all the steps and got the system files copied to media, and then to replace the main system files, but there I got confused. I ended up rebooting without attempting to install the youtube app, which I didn't find in the download. Even now, a lot looks like it is working, but I can't even attempt to sign in to google cause I can't get a keyboard to come up to allow me to enter my user name and password. Is there any help for me, or am I a total dunce needing to start over? thanks!
EDIT: I see I am screwed -- no keyboard is coming up for me anywhere. I guess I can go through a major reset but if anyone has a suggestion to just get the keyboard back I will appreciate it.
EDIT2: Well I got past that, simply chose multitouch keyboard instead of Gingerbread in NookColor Tools.
EDIT3: But now I am stuck again as I can't sign in to a google account... says can't establish a reliable data connection to the server, even though my wifi is fine. But at least at the moment everything else is fine, though the keyboard isn't working very well (but it does work; lots of ghosting)

An .img file is being uploaded for TouchNooter 1.6.20 It'll do all the copy and edit stuff, the only thing it can't do is create an android ID.
In the "GappsAndMore" there was some keyboards which were from the NC it was just a raw pull from AN. This is more refined with things that could cause issues removed. (Like Keyboards, Framework.jars from the NC, etc.)

william1853 said:
I've probably screwed up, but perhaps not too badly. Tried to follow all the steps and got the system files copied to media, and then to replace the main system files, but there I got confused. I ended up rebooting without attempting to install the youtube app, which I didn't find in the download. Even now, a lot looks like it is working, but I can't even attempt to sign in to google cause I can't get a keyboard to come up to allow me to enter my user name and password. Is there any help for me, or am I a total dunce needing to start over? thanks!
EDIT: I see I am screwed -- no keyboard is coming up for me anywhere. I guess I can go through a major reset but if anyone has a suggestion to just get the keyboard back I will appreciate it.
EDIT2: Well I got past that, simply chose multitouch keyboard instead of Gingerbread in NookColor Tools.
EDIT3: But now I am stuck again as I can't sign in to a google account... says can't establish a reliable data connection to the server, even though my wifi is fine. But at least at the moment everything else is fine, though the keyboard isn't working very well (but it does work; lots of ghosting)
Click to expand...
Click to collapse
I'd suggest a wipe and running TouchNooter... GappsAndMore had Keyboards and stuff in it and removed the stock keyboard =\

is a wipe in the nook touch holding down the power for 20 seconds?

No you need to do a complete wipe by triggering recovery, but I don't know how to trigger recovery yet.

oh well the perils of early adoption. I'll follow the thread with anticipation!

william1853 said:
oh well the perils of early adoption. I'll follow the thread with anticipation!
Click to expand...
Click to collapse
You could try 8 failed boots. Basically you power it on and then power it off before it fully boots. Do that 8 times and it might trigger recovery.

Confirmed this works great. I'm going to find a fix for the calendar.

GabrialDestruir said:
You could try 8 failed boots. Basically you power it on and then power it off before it fully boots. Do that 8 times and it might trigger recovery.
Click to expand...
Click to collapse
Recovery is holding the power button for 20+ seconds it will trigger recovery

xboxexpert said:
Recovery is holding the power button for 20+ seconds it will trigger recovery
Click to expand...
Click to collapse
Really? Is that from when it's off?

GabrialDestruir said:
Really? Is that from when it's off?
Click to expand...
Click to collapse
Not sure I have yet to try it but someone in the other thread said he called BN and they told him that and he did it.

xboxexpert said:
Not sure I have yet to try it but someone in the other thread said he called BN and they told him that and he did it.
Click to expand...
Click to collapse
I tried it and all I could get was it turning on and off

TouchNooter 1.6.20
This doesn't seem to work for me at all... I tried restoring the backup image and starting from scratch and it still will not work. I tried enabling Google Apps manually and it won't work for me either.
I think I'm done, if the 7th time wasn't the charm then I'm giving up for now...

MystaWright said:
This doesn't seem to work for me at all... I tried restoring the backup image and starting from scratch and it still will not work. I tried enabling Google Apps manually and it won't work for me either.
I think I'm done, if the 7th time wasn't the charm then I'm giving up for now...
Click to expand...
Click to collapse
I ran this on my Nook Touch and it worked just fine. Are you getting the "Rooted Forever" boot screen?

GabrialDestruir said:
I tried it and all I could get was it turning on and off
Click to expand...
Click to collapse
Didn't work for me either. 8 interrupted boots did.

i'm getting the rooted forever screen and then it just goes to the default stock home
any thoughts?
GabrialDestruir said:
I ran this on my Nook Touch and it worked just fine. Are you getting the "Rooted Forever" boot screen?
Click to expand...
Click to collapse

Same problem here... tried to return EVERYTHING to stock too.
yugoliang said:
i'm getting the rooted forever screen and then it just goes to the default stock home
any thoughts?
Click to expand...
Click to collapse
I did a reset of the device back to the out of the box experience, registered with my BN account, shut down and followed the directions to the letter. I had no luck at all. It just shows the Rooted Forever screen, then boots normally is if nothing happened.

Sorry Guys and Gals. Entirely my fault. It seems a combination of my own forgetfulness and bad scripting (I forgot proper codes and methods used in AN) caused this just to do nothing. I'm uploading a version as I'm typing this and will remove "BROKEN" from the title when it's up.

Still broken. init.rc isn't running it's script properly.
Script can be ran manually with:
Code:
adb shell sh /sdcard/nooter/tmp/scripts/Nooter
Will be working on getting it to trigger properly

[ROM][CM7] Defy Pro XT560 Support Thread

This is a support thread for the ROM posted here.
http://forum.xda-developers.com/showthread.php?p=49394355
* It is very important to clear factory data/cache after installing the CM7 rom.
* If your stuck on the android boot screen, connect usb and do a logcat to see what it is crashing on.
* The battery_charger has been replaced in this build as a safety backup to get into bootmenu. Anytime the phone is powered off and then plugged in it will boot to bootmenu instead of the charging screen.

* It is very important to clear factory data/cache after installing the CM7 rom.
Click to expand...
Click to collapse
I make all wipe data/cache and even Dalvik cache before and after install CM7 - but I stuck on the android boot screen.
But note: I made all wipes from CWM, because stock recovery is not works on my phone (only green robot and yellow triangle and that's all - nothing key works, only pull battery helps).
* If your stuck on the android boot screen, connect usb and do a logcat to see what it is crashing on.
Click to expand...
Click to collapse
How can I make this (run logcat)?
Thanks for the advices.

Im not sure the clear data/cache works right in CWM. I have not tested it. To access the menu in the stock recovery hit the Home key.
To output a logcat open a command prompt and run "adb logcat"
If you want to output it to a file use "adb logcat > filename.txt"

so there is some querrys:
- torch app does not work as a flashlight, while it stay in status bar and even task killer wont help
- led notification light does not work at all, i guess there is no app for that and original is missing
- it wont unlock sim card, or lock it while it's unlocked. message is "incorrect pin". previously unlocked on other phone sim works fine. pin correct.
- the reboot menu list wont operate with joystick, only touch.
- both cameras wont work in skype, when forced induce crash.
- dev tools options become a force close
- voice dialer started by long press call button opens in wrong screen orientation and does not work. it work if started from all apps.
- superuser does not ask about allowing su permissions, there is no app listed as allowed su perm. while all super su apps works fine as usual.
- yandex maps app issue. rendering map result is quite not what it should be

I did it! Thanks for stock recovery main key (Home) .
And now some my notes (first, I use Russian language and CM7 has it).
- torch app doesn't work - this right for me too;
- about led - not work too;
- about sim - not check this yet;
- the reboot menu OPERATE for me with D-Pad;
- I don't use Skype;
- dev tools work in full for me;
- all correct about voice dialer;
- it's right too;
- don't install yandex maps yet.

wifi is not work

clxer said:
wifi is not work
Click to expand...
Click to collapse
was't been working for me too, but first reboot solved it
a lot of apps that uses the hardware gpu does not work properly, i guess this is same as camera driver problem and it can't be resolved till motorola releases it freely(only if)
also i am having issue with call ringtone - it rings for fraction of a second and then goes silent

I missed some egl librarires in the build, copying the attached files to /system/lib/egl should correct some of the graphic issues.
retr13 said:
was't been working for me too, but first reboot solved it
a lot of apps that uses the hardware gpu does not work properly, i guess this is same as camera driver problem and it can't be resolved till motorola releases it freely(only if)
also i am having issue with call ringtone - it rings for fraction of a second and then goes silent
Click to expand...
Click to collapse

superdave said:
I missed some egl librarires in the build, copying the attached files to /system/lib/egl should correct some of the graphic issues.
Click to expand...
Click to collapse
antutu now running, mx harddecoding on the other hand dont
yandex. maps still weird

Good Job, and thank you
By the way, Pls tell me how to root defy pro.
I had tried many tools but both fail.

jimway said:
By the way, Pls tell me how to root defy pro.
I had tried many tools but both fail.
Click to expand...
Click to collapse
With poot.apk
http: / / ofimatica-programacion[dot]blogspot[dot]com/2014/02/rootear-telefonos-android-sin-necesidad[dot]html

Any updates?
edit- specifically, does CM7 fix the poor bluetooth A2DP quality of the stock ROM?
Sent from my XT560 using xda app-developers app

[4.4.4][15 Mar 2015] Slim&Beauty Cyanogenmod 11 1.1 [Only 96 MB]

#Cyanogenmod 11 Slim is a custom rom based on Cyanogen 11 Final for Galaxy Gio.
Bugs
Cyanogenmod 11 Bugs
Changelog
Version 1.0 Beta:
-Initial Release.
Version 1.1 (15 Mar 2015);
-Hola Launcher;
-Classic Keyboard;
-Lightning Browser;
-Z Camera;
-3D & HD Gallery;
-Material Calculator;
-Some Tweaks;
-1 Mb Lighter.
Features
-CM launcher(beauty, slim and faster than Trebuchet);
-Opera Mini browser(Very fast);
-ES file manager;
-10 MB lighter than original;
-Rooted;
-Only one ringtone;
-Improvements;
And more others to come...
ROM
Version 1.1:
https://mega.co.nz/#!2QxClK6K!8XFcHY04jqHTS3riX7IYw5RJP7RgW6lTfPijae_k7H8
CWM 6.0.5.3: https://mega.co.nz/#!fBRx3CQI!nRQly7MyyPZUxK-ZxPoh702Oo0X1Du7bR32i-H3L4dQ
Installation
1.Root your device and install ClockworkMod Recovery 6.0.5.3;
2.Reboot into recovery using the 3 button combination(power+home key);
3.I recommand to do a nandroid backup!;
4.Wipe data/factory reset+ wipe cache partition+wipe system(in mounts&storage);
5.Install the rom from internal sdcard.
After you install the rom I recommand go to settings, about device and press seven times on build number. You will unlocked performance & developer options. In performance go to processor and set the maximum cpu frequency to 825 mhz and checked the set on boot box.
Thanks to:
-androidarmv6 team;
-Meraki Apps, Hola Team, A.C.R. Development, GrikZor Studio , Zero Team and Leopard V7(Developers of the apps);
-Google;
-Cyanogenmod;
-Samsung;
-XDA;
-All people that are in my life;
-And me.
Screenshot in attachments.
I am not responsible for bricked devices, dead SD cards,...
TEST AT YOUR OWN RISK!
YOU NEED CWM 6.0.5.3 FOR GIO

is camera working?

trebla459 said:
is camera working?
Click to expand...
Click to collapse
Yes

Oh, I think I made a mistake.
I was on a enhanced 2.3.6 on my S5660, with a CWM 5.0.27 but I wanted to try this ROM.
So I downloaded the CWM 6053_1 from here: http://forum.xda-developers.com/gal.../dev-cwm-recovery-upd-20140630-t2799784/page2
And try to flash it from the recovery 5.0.27.
Then rebooted in recovery with power and home key and it seems is in boot loop.
Samsung logo appears, then screen goes white, and then black again, and restarts.
How can I solve?
---------- Post added at 10:40 AM ---------- Previous post was at 10:09 AM ----------
Also trying to install CWM 5.0.27 again via Odin, it stucks on setup connection.
Oh ****. What else can I try?
---------- Post added at 11:18 AM ---------- Previous post was at 10:40 AM ----------
Temporarily solved thanks to one try to get into Download mode (yellow font) and the with Odin everything works.
Now, What i was wrong?
Did I installed a wrong CWM?

HerroYou said:
Yes
Click to expand...
Click to collapse
what are its bugs? Can I edit pictures in instagram?

The rom is stable. I think the only bug is a little autofocus problem. Probably I will post 1.1 version this weekend and I will post in attachements the CWM 6.0.5.3.

Radu27 said:
The rom is stable. I think the only bug is a little autofocus problem. Probably I will post 1.1 version this weekend and I will post in attachements the CWM 6.0.5.3.
Click to expand...
Click to collapse
Yes Thanks, but, could you tell me what I was wrong?
I'm back to a 2.3.6 but I really would like to try this ROM.

install this rom and works like a charm love it , keep it up a good work love the notif panel but the launcher kinda laggy but love this rom , Thank you

paolomatador said:
Yes Thanks, but, could you tell me what I was wrong?
I'm back to a 2.3.6 but I really would like to try this ROM.
Click to expand...
Click to collapse
You Installed Cwm for galaxy ace, not gio!

Great, ROM Installed, but no Play Store?
How do I install any APP?
:crying::crying:
Also, little bug, when screen is locked, it says "NO SIM inside", but obviously the SIM is inside.
Could you please post ggapps package for this ROM?
I tried download the small package from here: http://wiki.cyanogenmod.org/w/Google_Apps
But it doesnt works.
At leasts I just need the Play Store!
I Just found a Play Store apk for cm11, downloaded and installed but it doesnt works.
Also, ROM it seems really laggy, dont know why...
Going back to my backup of 2.3.6, sorry.
Waiting for a gapps package that works with this Rom.

Failed to go back to 2.3.6, it was stuck on boot logo and nothing else.
So I tried to reinstall again this CM 11.
It seems is working but for me is pretty unusable without Play Store or Gapps.
Could you please help me?
Thx

paolomatador said:
Failed to go back to 2.3.6, it was stuck on boot logo and nothing else.
So I tried to reinstall again this CM 11.
It seems is working but for me is pretty unusable without Play Store or Gapps.
Could you please help me?
Thx
Click to expand...
Click to collapse
Don't be lazy, use the search to find mini gapps by Mardon for cm11

belyava said:
Don't be lazy, use the search to find mini gapps by Mardon for cm11
Click to expand...
Click to collapse
Thanks.
I was not that lazy, just searched for gapps for CM11 but found other packages that doesnt works.
Anyway, I think I'll stay with my 2.3.6, its just for few weeks until my N4 came back from repair!

first impressions
Just installed this rom and here's what i found at a glance:
Positive:
- rom is stable, snappy and all in all behaves very well
- the folder management for icons is just what i needed
Neutral:
- changing the network signal icon to dB makes it so you can't know when you have data on or not at a glance. i like to know how much radiation i'm exposed to and find the best spot for signal when it's very low, but the text should turn brown or show some arrows or something when data is on. i have seen this however on all other roms, so i don't know if you can change that
- phone should start with 2G mode, no sync, data off, location off - if the user doesn't have any data left, the first time i run the rom it will just cost cost him money for nothing. 3G signal (in Romania at least) is a lot worse than 2G one, so why make the user take extra steps? - 2G/3G mode should also be on quick panel, as well as sound
- the Heart App has a Google Play icon in upper right corner - click on it and it opens lightning browser which "is no longer compatible", i get a link below which is "not available"
- maybe you could include a quick tile icon for turning the display into flashlight (like in CM12)
- no out of the box blank background. however i cound install from PlayStore black backgroud (13KB) and the option appeared. maybe you include this in next build and cut some of the other live wallpapers to reduce size even more
- while booting, until hola screen appears, the display is on maximum brightness - this is an unnecesary power drain
- on first boot there is a some sort of an error message regading hola launcher and the inability to set it as default laucher. "try again" brings again the message, "later" dismisses it
Negative:
- camera fails to focus correctly. best clarity i found for gio was in LeWa port , however that rom is based on CM7 and i don't know if you can just take from there and port it here
- WiFi signal is rather low and sometimes although it finds the network, does not connect to it. Again, the chinese port somehow manages to connect to wifi in 3-4 seconds after i turn wifi on with better signal
- I'm using S2E (as i find it better than link2sd) but moving the Dalvik cache seems to break some system functions. i only tested it with wifi that failed to turn on afterwards, but as this function is very important i moved back the Dalvik, checked only the other boxes in S2E and now it's all good
All in all a solid work, well done !
P.S. You should post a link in the first post to a recommended gapps, as i find the Mardon gapps quite large (about 30MB) and maybe some users just want the Play app (without all that other data sent to Google), which is about 8MB

andrei.nica said:
Just installed this rom and here's what i found at a glance:
Positive:
- rom is stable, snappy and all in all behaves very well
- the folder management for icons is just what i needed
Neutral:
- changing the network signal icon to dB makes it so you can't know when you have data on or not at a glance. i like to know how much radiation i'm exposed to and find the best spot for signal when it's very low, but the text should turn brown or show some arrows or something when data is on. i have seen this however on all other roms, so i don't know if you can change that
- phone should start with 2G mode, no sync, data off, location off - if the user doesn't have any data left, the first time i run the rom it will just cost cost him money for nothing. 3G signal (in Romania at least) is a lot worse than 2G one, so why make the user take extra steps? - 2G/3G mode should also be on quick panel, as well as sound
- the Heart App has a Google Play icon in upper right corner - click on it and it opens lightning browser which "is no longer compatible", i get a link below which is "not available"
- maybe you could include a quick tile icon for turning the display into flashlight (like in CM12)
- no out of the box blank background. however i cound install from PlayStore black backgroud (13KB) and the option appeared. maybe you include this in next build and cut some of the other live wallpapers to reduce size even more
- while booting, until hola screen appears, the display is on maximum brightness - this is an unnecesary power drain
- on first boot there is a some sort of an error message regading hola launcher and the inability to set it as default laucher. "try again" brings again the message, "later" dismisses it
Negative:
- camera fails to focus correctly. best clarity i found for gio was in LeWa port , however that rom is based on CM7 and i don't know if you can just take from there and port it here
- WiFi signal is rather low and sometimes although it finds the network, does not connect to it. Again, the chinese port somehow manages to connect to wifi in 3-4 seconds after i turn wifi on with better signal
- I'm using S2E (as i find it better than link2sd) but moving the Dalvik cache seems to break some system functions. i only tested it with wifi that failed to turn on afterwards, but as this function is very important i moved back the Dalvik, checked only the other boxes in S2E and now it's all good
All in all a solid work, well done !
P.S. You should post a link in the first post to a recommended gapps, as i find the Mardon gapps quite large (about 30MB) and maybe some users just want the Play app (without all that other data sent to Google), which is about 8MB
Click to expand...
Click to collapse
I appreciate your opinion about this rom. I am a teenager and I want to learn a lot about the custom rom. For me it's a new "territory", In vacation I will try to learn more. I'm also from Romania. Thank you for trying my rom. A good day!

keyboard Caps
great to hear that!
i played around a bit more with the rom and found a small but annoying issue, especially when sending sms: in the preinstalled keyboard app "classic keyboard", instead of Shift that buttons works as Caps Lock, turning all letters to uppercase. Also after . keyboard turns to uppercase as it's supposed to, but forgets to turn to normal case after first letter (i don't use word prediction).
Not only that, but the app has FULL NETWORK ACCESS, which a keyboard app should NOT, as it could send account credentials to the devs. The entire XDA project started as a way to offer a safe alternative to what corporations force on us and their "well known" policies. If you want a lightweight keyboard app with as few permissions as possible and great functions, i recommend the good old Hacker's Keyboard, from PlayStore. It's only 2.4 MB (compared to 1.8) but has no bugs and offers Ctrl and Alt in Landscape.
spor!

gapps problem
Hi,
The ROM is superb! very nice work I only have one big problem...
When I install gapps I get a load of messages "unfortunately xx. has stopped working" with xx being google play services among other things.
I have tried various gapps packages including mardons latest and tried with and without the accounts zip.
I have:
-carry out full wipe
-flash cwm 6.0.5.3.
-reboot to recovery
-Flash ROM
-Restart to OS, play about a bit, restart to recovery
- Flash gapps, flash account.zip
-reboot to OS
Thanks in advance

orangejuice43 said:
Hi,
The ROM is superb! very nice work I only have one big problem...
When I install gapps I get a load of messages "unfortunately xx. has stopped working" with xx being google play services among other things.
Thanks in advance
Click to expand...
Click to collapse
I have found somewhere on xda a while ago some gapps that work flawlessly with this rom (less than 8 MB).
There's only PlayStore but all the rest you install from there on.
Hope the attachment helps !

Thanks @andrei.nica, I've tried it and still get the same problem. On installing gapps I don't actually see the playstore appear at all. Cyanogen account crashes gives the 'stopped' message, so does whisperpush. But this only happens after installing gapps...

reinstall
orangejuice43 said:
Thanks @andrei.nica, I've tried it and still get the same problem. On installing gapps I don't actually see the playstore appear at all. Cyanogen account crashes gives the 'stopped' message, so does whisperpush. But this only happens after installing gapps...
Click to expand...
Click to collapse
Here's how i do: as i'm not a fan of nand backup, i back my contacts (by exporting to SD) and whatever apps on SD (not their data) with apkshare and then from CWM: wipe data/factory reset+ wipe cache partition+wipe system(in mounts&storage)+wipe dalvik cache (in advanced) - install the rom.zip, boot the rom to see how it behaves, then install gapps.zip.
However i have a SD that i've partitioned in 2 as it helps with the number of apps i can install: one fat and one ext2 (i think, about 500MB) - you can do it from CWM or Ubuntu - so that i move apps to second partition using S2E. For this rom however, i've had some errors when selecting also moving Dalvik cache, so I untick last option in S2E.

AOSP 7.1 ROM/Discussion

Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
What is this ROM/thread?
This is a port to the i9000 of my work for the SGH-T959P which is the Telus version of the Galaxy S. I initially started work on AOSP to see what exactly needed to be changed from AOSP to work on my device. I had a request for access to an i9000 build hence I created this thread. This is also a place to discuss using my source code to build other ROMs and/or improve it. This is not a place for a general development "How do I build a ROM?" questions - there are plenty of guides on XDA and elsewhere that say how to do this. Since I don't have an i9000, I probably can't reproduce your bug unless it is common on my device as well. As such, I will be able to provide very limited support, so if you have any concerns about your phone bricking, do not flash anything from this thread!!
Installation Instructions
You should be able to flash this from any MTD rom, but it probably works best from a 6.0 or 7.x based ROM. Root does not come pre-installed, instead you need to manually install. Due to our odd partition system, please see http://forum.xda-developers.com/showpost.php?p=69245956&postcount=3 for instructions.
Things to Take Note Of
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
This build is very close to the official AOSP source code. Recovery is TWRP but otherwise there aren't any added "features" - nor will I add any as this is
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully. Opengapps pico should work just fine but are untested
Backup Backup Backup! I'm not responsible for you losing any data or anything else that could go wrong.
Working on my variant
Camera (built-in app needs workaround, see below)
RIL
SMS
Wifi
Vibration
Automatic Brightness
Compass
GPS on T959P
Headset Buttons
Partially working
Bluetooth - first time trying to enable won't work, back out of the Settings page, re-enter it and try enabling again. It should work this time...
Camera and Browser apps need to have all their permissions manually enabled through settings for full functionality. This is because I've used the older Camera app (which hasn't been updated for dynamic permissions) and the older Browser app as the new one is simply a test shell with no features (thanks Google!)
What doesn't
TWRP build is currently broken. To work around this, replace the ramdisk-recovery.img in the zip with the one from CM14.1
SElinux is currently in permissive mode. Still missing are the GPS sepolicies plus the LVM ones. If someone sends me a dmesg, I might be able to change this...
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+ Please do not ask me to implement this, I've tried several times and failed miserably each time.
I haven't actually verified that this boots as I don't have this specific variant!!!
XDA:DevDB Information
AOSP 7.1 ROM/Discussion, ROM for the Samsung Galaxy S I9000
Contributors
xc-racer99, Coldwindofnowhere
Source Code: https://github.com/xc-racer99/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Android 6.0
Based On: AOSP
Version Information
Status: Testing
Created 2016-12-21
Last Updated 2016-12-20

Please have a look at the thread I created for my variant at http://forum.xda-developers.com/galaxy-s-4g/development/rom-aosp-7-x-galaxy-s-4g-t3485237
Build your own!
All the device-specific source code is on my github at https://github.com/xc-racer99/. The branch I've used for the build posted below is the aosp-7.1 branch. The aosp-7.1-ddk-1.19 is test branch that uses the latest DDK 1.19 PVR blobs for OMAP devices. Unfortunately, it breaks hardware decoding (and you would need to compile the correct kernel as it uses a different PVR kernel driver). It is more of interest than of actual use.
Follow https://source.android.com/source/initializing.html. The branch you want when you run repo init is the latest tag from https://source.android.com/source/build-numbers.html#source-code-tags-and-builds of 7.1. Before you run repo sync, from the WORKING_DIRECTORY/.repo folder, run "git clone https://github.com/xc-racer99/local_manifests -b 7.1". Continue on with the build guide, the device codename you want is "galaxysmtd".
If you want to build the kernel, follow the instructions in WORKING_DIRECTORY/kernel/samsung/aries/AOSP_README. Put the resulting arch/arm/boot/zImage in device/samsung/galaxysmtd
Other aries devices (captivate, i9000B, vibrant) should be fairly easy to do (ie the galaxysmtd on my github as well as the captivate trees work). The fascinate and p1 would need a fair bit of work. There is an i9000B kernel uploaded to https://www.androidfilehost.com/?fid=457095661767123305 - simply replace the boot.img in the i9000's zip with this one and it should work (except that in Settings you will appear as an i9000 instead of an i9000B).
For porting to other ROMs, please take note of https://github.com/xc-racer99/android_patches - these are the patches that the custom ROM and/or you must implement to have a successfully booting and functional device. You also need to have busybox and TWRP as part of the build tree.
Download Link and Changelogs
A reminder - I've not personally tested any of these builds...
2017-01-19 Build
Updated interactive governor - should result in fewer slowdowns if you use this governor
Changed low memory killer parameters so it kills a little quicker (ie before it runs out of memory)
Disabled a bit more background stuff to hopefully free a bit more memory
Fixed/cleaned up the shims that are used for the RIL - should prevent SSL issues (eg with Hotmail accounts) as well as being slightly faster and more reliable
Selinux is still in permissive mode (a dmesg could possibly help me in putting this to enforcing, if people are interested). I still don't know if the TWRP included in it is functional or not (someone can let me know, I guess )
Older Builds
2016-12-26 Build
Home button should now work
SD card/internal storage should work properly
Added ability to have /data on microSD (see here for info)
2016-12-19 Build

Anyone can test this build to see if data is working properly on his build ? RIL seems to crash randomly for some reason in 7.1.1 with cm 14.1 ...

Coldwindofnowhere said:
Anyone can test this build to see if data is working properly on his build ? RIL seems to crash randomly for some reason in 7.1.1 with cm 14.1 ...
Click to expand...
Click to collapse
Despite the fact that i have used all my mb to my phone,data opens normally and don't have any problem with crashes etc.
edit:Lost RIL all of a sudden with x on network.rebooted and it laid to TWRP saying no OS is installed.Starting all over again with odin etc.

ioannis_m said:
Despite the fact that i have used all my mb to my phone,data opens normally and don't have any problem with crashes etc.
edit:Lost RIL all of a sudden with x on network.rebooted and it laid to TWRP saying no OS is installed.Starting all over again with odin etc.
Click to expand...
Click to collapse
Hmm, ok. Thanks for testing. I guess that means it boots Did the sdcard(s) get detected properly? In my earlier builds of AOSP I had difficulties with this.
It's possible that my TWRP build is non-functional. Try replacing the ramdisk-recovery.img in the zip with one from @Coldwindofnowhere CM14 build.
Thanks for testing.

First of all thanks for bring AOSP NOUGHT.everything work fine.like
Camera,storage,WiFi, hotspot,Bluetooth, ril.
But I found some issues.
1.browser working but couldn't browse
But third party browser work fine.
2.outgoing call fine.but when come incoming call
Device not wakeup also get hanging till incoming call cut.also network gone.after reboot it work fine.

udhy said:
First of all thanks for bring AOSP NOUGHT.everything work fine.like
Camera,storage,WiFi, hotspot,Bluetooth, ril.
But I found some issues.
1.browser working but couldn't browse
But third party browser work fine.
2.outgoing call fine.but when come incoming call
Device not wakeup also get hanging till incoming call cut.also network gone.after reboot it work fine.
Click to expand...
Click to collapse
Hmm, did you install gapps? I'm assuming by what you mean for "couldn't browse" is that a white screen appeared instead of content. This is likely due to a different webview provider being installed which removed the AOSP one.
Odd that you're getting incoming call issues. Do these happen with @Coldwindofnowhere CM14 build? There are a couple of things I could try to fix but I'm not sure. I rarely if ever make calls on my phone so I don't know what all issues exist.

xc-racer99 said:
Hmm, did you install gapps? I'm assuming by what you mean for "couldn't browse" is that a white screen appeared instead of content. This is likely due to a different webview provider being installed which removed the AOSP one.
Odd that you're getting incoming call issues. Do these happen with @Coldwindofnowhere CM14 build? There are a couple of things I could try to fix but I'm not sure. I rarely if ever make calls on my phone so I don't know what all issues exist.
Click to expand...
Click to collapse
Umm no never had this issue with cm 14.1, but in the latest build sometimes ril just crashes for no apparent reason then it's back one I reboot.

Coldwindofnowhere said:
Umm no never had this issue with cm 14.1, but in the latest build sometimes ril just crashes for no apparent reason then it's back one I reboot.
Click to expand...
Click to collapse
Have you (or anyone else) managed to get a log (radio logcat, dmesg and regular logcat)? Just wondering what exactly is crashing. Likely rild - and there's a bug in our libsec-ril.so so that it won't restart automatically because then it crashes the system...

xc-racer99 said:
Hmm, did you install gapps? I'm assuming by what you mean for "couldn't browse" is that a white screen appeared instead of content. This is likely due to a different webview provider being installed which removed the AOSP one.
Odd that you're getting incoming call issues. Do these happen with @Coldwindofnowhere CM14 build? There are a couple of things I could try to fix but I'm not sure. I rarely if ever make calls on my phone so I don't know what all issues exist.
Click to expand...
Click to collapse
No.i didn't install gapps and not appeared white screen in browser anything browse in browser(sys app) its loading,loading, loading.....
Incoming call working but delay to wakeup when incoming call come.
I used one day full.my device good. Rarely crash ril. These few issues only problem in the otherwise this rom so good.
Sorry for bad english.

Thanks xc-racer99 for making AOSP Android 7.1 .
I just installed it on I9000B with the kernel that you made available for this device. I felt that the time of first boot after installation is faster than cm14.
I found some problems:
1) The home button does not work.
2) The android is having problem with internal storage (Data and Internal Memory). It is displaying strange values of used and available space. Camera can not save photo or video.
I'm not using SD Card External.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) Randomly is freezing or restarting.
I'm glad that you have made the kernel available to build.
I have a question, in this code is there the patch needed to work the touchscreen of the I9000B?
Thanks,
Daniel

DanielBR911 said:
Thanks xc-racer99 for making AOSP Android 7.1 .
I just installed it on I9000B with the kernel that you made available for this device. I felt that the time of first boot after installation is faster than cm14.
I found some problems:
1) The home button does not work.
2) The android is having problem with internal storage (Data and Internal Memory). It is displaying strange values of used and available space. Camera can not save photo or video.
I'm not using SD Card External.
View attachment 3976988
3) Randomly is freezing or restarting.
I'm glad that you have made the kernel available to build.
I have a question, in this code is there the patch needed to work the touchscreen of the I9000B?
Thanks,
Daniel
Click to expand...
Click to collapse
Right, that kernel is designed for 7.0 and doesn't have the patch to fix the freezes present in 7.1. Try the one from https://www.androidfilehost.com/?fid=673368273298918331
Home button doesn't work - as in doesn't wake the device or doesn't work period? AOSP doesn't support the home button waking the device (OEMs and most custom ROMs implement this).
Internal storage - now that is interesting. In my earliest test builds of 7.0, that was a feature there. I don't know why it's reappeared. Perhaps a data wipe will fix the issue??? The Camera issue is related to this IMO. You could try using OpenCamera as I've had success with it on my device.
udhy said:
No.i didn't install gapps and not appeared white screen in browser anything browse in browser(sys app) its loading,loading, loading.....
Incoming call working but delay to wakeup when incoming call come.
I used one day full.my device good. Rarely crash ril. These few issues only problem in the otherwise this rom so good.
Sorry for bad english.
Click to expand...
Click to collapse
Ok, thanks for the clarification.

xc-racer99 said:
Right, that kernel is designed for 7.0 and doesn't have the patch to fix the freezes present in 7.1. Try the one from
Home button doesn't work - as in doesn't wake the device or doesn't work period? AOSP doesn't support the home button waking the device (OEMs and most custom ROMs implement this).
Internal storage - now that is interesting. In my earliest test builds of 7.0, that was a feature there. I don't know why it's reappeared. Perhaps a data wipe will fix the issue??? The Camera issue is related to this IMO. You could try using OpenCamera as I've had success with it on my device.
Ok, thanks for the clarification.
Click to expand...
Click to collapse
Thank you. Now the android is not freezing anymore.
About the Home Button , no function is working. Usually when it's pressing the apps are closed.
Something strange happened to the internal storage. I performed the Wipe Data.
Now I can not format any other partitions (System, Data, Cache).
I will run Odin with the partition map and Android 2.2.
To install AOSP 7.1 is it necessary to have Android 6 installed before?
Thanks
Daniel

I did some experiences:
1) If I use ramdisk-recovery.img and ramdisk.img from CM 14 or Cm 14.1. In TWRP, the size of the System and Data partitions is usually recognized and I can format them both in EXT4.
But the Android shows that the internal memory is corrupted. Not being able to record anything in memory.
2) If I use the original ramdisk-recovery.img and ramdisk.img from AOSP 7.1, TWRP does not recognize the size of the System and Data partitions and I can not format them.
The android shows that the internal memory is corrupted. Not being able to record anything in memory.

DanielBR911 said:
Thank you. Now the android is not freezing anymore.
About the Home Button , no function is working. Usually when it's pressing the apps are closed.
Something strange happened to the internal storage. I performed the Wipe Data.
Now I can not format any other partitions (System, Data, Cache).
I will run Odin with the partition map and Android 2.2.
To install AOSP 7.1 is it necessary to have Android 6 installed before?
Thanks
Daniel
Click to expand...
Click to collapse
DanielBR911 said:
I did some experiences:
1) If I use ramdisk-recovery.img and ramdisk.img from CM 14 or Cm 14.1. In TWRP, the size of the System and Data partitions is usually recognized and I can format them both in EXT4.
But the Android shows that the internal memory is corrupted. Not being able to record anything in memory.
2) If I use the original ramdisk-recovery.img and ramdisk.img from AOSP 7.1, TWRP does not recognize the size of the System and Data partitions and I can not format them.
The android shows that the internal memory is corrupted. Not being able to record anything in memory.
Click to expand...
Click to collapse
Ok, so it looks like the TWRP included with the ROM is non-functional. I'll make a note of that in the OP.
It is probably necessary to go to Android 6 (or at least 5.1) before going on to 7.1, but I haven't tested. It's just whether or not the package name is correctly detected by updater.sh. Since I don't have the device, I can't test...
With the home button, could you please get me a logcat? See http://forum.xda-developers.com/showthread.php?t=2185929 if you need instructions. A dmesg from the broken recovery would also be useful if you get a chance.
Thanks.

xc-racer99 said:
Ok, so it looks like the TWRP included with the ROM is non-functional. I'll make a note of that in the OP.
It is probably necessary to go to Android 6 (or at least 5.1) before going on to 7.1, but I haven't tested. It's just whether or not the package name is correctly detected by updater.sh. Since I don't have the device, I can't test...
With the home button, could you please get me a logcat? See http://forum.xda-developers.com/showthread.php?t=2185929 if you need instructions. A dmesg from the broken recovery would also be useful if you get a chance.
Thanks.
Click to expand...
Click to collapse
Here my logcat:
View attachment logcat.log
I had a problem to get Kernel log. When i run this command: adb shell su -c dmesg > dmesg.log. I got : su: invalid uid/gid '-c'.
I'm confuse. TWRP (ramdisk-recovery.img and ramdisk.img from AOSP 7.1.1) is now recognizing the System and Data partitions with their correct sizes.
But Android is still showing "SD Internal Corrupt" .
When I click in " SD Card Corrupt" a screen for formatting is opened. When I command to format the internal sd, an error message appears quickly and the screen closes. When I enter in TWRP, it does not recognize the size of the system and date partition.
I should not have done it
Now I'm going to have to run the odin to recover partition again :crying:.

DanielBR911 said:
Here my logcat:
View attachment 3977611
I had a problem to get Kernel log. When i run this command: adb shell su -c dmesg > dmesg.log. I got : su: invalid uid/gid '-c'.
I'm confuse. TWRP (ramdisk-recovery.img and ramdisk.img from AOSP 7.1.1) is now recognizing the System and Data partitions with their correct sizes.
But Android is still showing "SD Internal Corrupt" .
View attachment 3977629
When I click in " SD Card Corrupt" a screen for formatting is opened. When I command to format the internal sd, an error message appears quickly and the screen closes. When I enter in TWRP, it does not recognize the size of the system and date partition.
View attachment 3977630
View attachment 3977631
I should not have done it
Now I'm going to have to run the odin to recover partition again :crying:.
Click to expand...
Click to collapse
Hmm, I think we have two separate problems. I think Android having the issues is probably due to me removing https://github.com/Coldwindofnowher...overlay/frameworks/base/data/etc/platform.xml as I thought this was outdated and unnecessary (as I didn't need it on my device).
TWRP issue is probably different, don't use the one built into the ROM. I'll have another look through the config and try to fix it.
I didn't see any mentions of any buttons (home and/or volume) in the logcat, so we'll figure that problem out later. I'll add some debugging to the next kernel I upload.
Not surprising that the dmesg failed - try instead "adb shell dmesg > dmesg.log" - since we're not CM based we don't need the "-c" part.

xc-racer99 said:
Hmm, I think we have two separate problems. I think Android having the issues is probably due to me removing https://github.com/Coldwindofnowher...overlay/frameworks/base/data/etc/platform.xml as I thought this was outdated and unnecessary (as I didn't need it on my device).
TWRP issue is probably different, don't use the one built into the ROM. I'll have another look through the config and try to fix it.
I didn't see any mentions of any buttons (home and/or volume) in the logcat, so we'll figure that problem out later. I'll add some debugging to the next kernel I upload.
Not surprising that the dmesg failed - try instead "adb shell dmesg > dmesg.log" - since we're not CM based we don't need the "-c" part.
Click to expand...
Click to collapse
Thanks.
Here my dmesg:
View attachment dmesg.log

Thanks for your work!
I've got a few problems with your ROM.
RIL is unreliable at best. Surprisingly I had correct 3G performance at first flash and first boot, but then after subsequent reboots and then newer flashes / wipes, it totally stopped working. I have cell phone reception even though it's slow to get it, but no data at all. About plane mode, it doesn't cut the basic (non-data) cellphone service which is probably a bug too. P.S. : Got back data, see below.
After boot there is a notification about sdcard being corrupt, either when I have a sdcard or not. I cannot access /sdcard.
Home button doesn't work at all, period.
Wifi doesn't work at all, either from quick access or settings. In settings, when I tap to activate wifi, it stays stuck at "Activating wifi..." and doesn't change anything else except the button I tapped. This button reverts to off when I exit.
Bluetooth doesn't work at all, either from quick access or settings. In settings, when I tap to activate bluetooth, it doesn't change anything except the button I tapped. This button reverts to off when I exit. Well, after numerous tries, when I decided to generate my logcats (see below), tapping on "Bluetooth on" actually activated it successfully...and also made 3G work. Wtf?
Logs are attached to this message. Methodology for acquiring them :
Wiped everything. (Re-)flashed this ROM. Wiped data / cache.
Booted system a first time. Acquired LogcatFirst.log.
Rebooted system.
Tryed to toggle Wifi (from settings) on at aprox 02:50:04. Then exited.
Tryed to toggle Blutooth (from settings) on at aprox 02:51:25. Then exited. Please note that at this very moment, Bluetooth started working and I got back a 3G connection. Wtf?
Used home button from settings app at aprox 02:55:??. This does produce zero output to logcat.
Set plane mode from quick panel on at aprox 02:56:30, then off at aprox 02:58:36.
Acquired LogcatSecond.log, Dmesg.log and Radio.log
EDIT : After plane mode, I lost Bluetooth and data again.

Ano59 said:
Thanks for your work!
I've got a few problems with your ROM.
RIL is unreliable at best. Surprisingly I had correct 3G performance at first flash and first boot, but then after subsequent reboots and then newer flashes / wipes, it totally stopped working. I have cell phone reception even though it's slow to get it, but no data at all. About plane mode, it doesn't cut the basic (non-data) cellphone service which is probably a bug too. P.S. : Got back data, see below.
After boot there is a notification about sdcard being corrupt, either when I have a sdcard or not. I cannot access /sdcard.
Home button doesn't work at all, period.
Wifi doesn't work at all, either from quick access or settings. In settings, when I tap to activate wifi, it stays stuck at "Activating wifi..." and doesn't change anything else except the button I tapped. This button reverts to off when I exit.
Bluetooth doesn't work at all, either from quick access or settings. In settings, when I tap to activate bluetooth, it doesn't change anything except the button I tapped. This button reverts to off when I exit. Well, after numerous tries, when I decided to generate my logacts (see below), tapping on "Bluetooth on" actually activated it successfully...and also made 3G work. Wtf?
Logs are attached to this message. Methodology for acquiring them :
Wiped everything. (Re-)flashed this ROM. Wiped data / cache.
Booted system a first time. Acquired LogcatFirst.log.
Rebooted system.
Tryed to toggle Wifi (from settings) on at aprox 02:50:04. Then exited.
Tryed to toggle Blutooth (from settings) on at aprox 02:51:25. Then exited. Please note that at this very moment, Bluetooth started working and I got back a 3G connection. Wtf?
Used home button from settings app at aprox 02:55:??. This does produce zero output to logcat.
Set plane mode from quick panel on at aprox 02:56:30, then off at aprox 02:58:36.
Acquired LogcatSecond.log, Dmesg.log and Radio.log
EDIT : After plane mode, I lost Bluetooth and data again.
Click to expand...
Click to collapse
Alright, thanks for the complete rundown on errors. I'll try to go through them:
Bluetooth - having difficulty activating is not surprising. Android technically doesn't support non BT LE devices such as ours - I had to hack in support for no LE/SMP/GATT (the supporting parts of the BT stack AFAIK) with the patch https://github.com/xc-racer99/android_patches/blob/aosp-7.1/system_bt.patch. There's nothing I can really do about this. If you read the OP, it says
first time it won't enable if enabling through settings, back out and then second time it will. Works just fine from status bar pulldown
Click to expand...
Click to collapse
This was for 7.0, I guess it's changed slightly in 7.1 so I'll update the OP.
Data - this sounds totally bizarre. I wish I had an i9000 to test this. One of the big differences between the i9000 and my device, the SGH-T959P, is that you guys use the (infineon?) XMM616 for your modem while mine uses the M5720 by STE. I have yet to have an issue with data when I've tested it on my variant. Again, I'm afraid I can't do too much about this
Wifi - this sounds weird. There's some noise in the logcat, ie "12-24 02:50:04.778 W/CommandListener( 164): Failed to retrieve HW addr for wlan0 (No such device)". This is very surprising, I have nothing like this in a logcat on my device. I'm thinking perhaps that the MAC address wasn't properly setup. Could you please run "adb shell getprop | grep macaddr"? The RIL actually sets the macaddr so these two issues might be related. Did you check the md5 of the zip after downloading? It almost sounds like a bad download/ flash. The other thing is that yours is a special hardware model which doesn't like having the wifi driver built into the kernel (I did see a reference to this in a commit from the CM10.1 days). @Coldwindofnowhere's CM14 has it as a module so it might be working there.
Home button - I probably messed up the keylayout somewhere. My device has a capactive home button as opposed to a hard button. Please try pushing the attached files to /system/usr/keylayout after removing the ".img" at the end of the filename (to get around XDA's filetype filter).
Corrupt SDCard is probably my fault. Please try the new build at https://www.androidfilehost.com/?fid=529152257862690355 as I think I've found and corrected the issue.
Unfortunately, your logcat is very "chatty" - basically android prevents things from creating too much logspam. This sucks for debugging as we lose many lines, so to turn it off run
Code:
adb logcat -P ""
right at boot
Since we're having so many issues with mobile network/wifi/bluetooth, I'm wondering if our netfilter code in the kernel isn't working properly.... The thing against this theory is that things work on my variant.

Just tweak it [Tab S4] - debloat, root, plugins, battery...

Tab S4 stock cleanup actions
phablet guide fest continues V30->Note9->6T->Mi9->S10->7T->Tab S6->Tab S4, time to provide some thoughts, easy to click links and guides. Goal is to have a clean device after each update, and have a helper script running at boot or on demand. This is a tablet, we want to achieve flat battery graphs when it is unused (picture attached), hopefully charge once a week with slight usage.
Debloat
What the script does:
* choose 8 categories of app removal, in the beginning of the file
for each say 0=skip 1=remove 2=revert back
* use more switch to disable some questionable/helpful stuff
* disable up to 80 apps with possibility to revert back
* remove usage access for google (do manually)
* remove device admin backdoor "Find My Mobile", you won't recover stolen device this way lol, it doesn't work with Secure Startup! it's useful for Govt.
* remove proca (which was slowing down tablet after rooting), if it doesn't work from your shell, edit the file as below
Tested ok on March stock Pie firmware. Samsung has too much bloatware installed, and requires shocking permissions to run some basic services. We will further need to reclaim privacy. As for debloat list, i've cooked the list based on knowledge of each process, its current presence in the Pie firmware, and what would fit the tablet usage. In this case, i'm leaving Samsung account, Galaxy shop and few pen apps and we assume XPrivacy is sending these snitch services bogus personal details.
Download: (file attached)
Installation:
- run in su terminal once or add to any startup script (3C\Device mgr\Scheduler can assign scripts from /storage/emulated/0/Android/data/ccc71.at/scripts), or to magisk
Rooting
We want encryption. There are no ROMs, and TWRP can be used for many other tasks without access to your files.
OEM unlock in dev settings
when turned off and rather plugged it to your PC with drivers installed, hold Power & Vol+ & Vol- til you see download screen, confirm with Vol+
in ODIN, slap TWRP into AP while "Auto reboot" is unchecked
hold Power & Vol- to exit download mode, then Power & Vol+ to enter recovery
in TWRP, slap kernel and Magisk into tablet from SD card or USB (can be usb flash, can be other mobile, can be adb)
in TWRP, say boot to system and wait 5min
check Magisk app status, enable USB debugging in dev settings
kernel: WETA recovery: TWRP 3.3.1 for PIE SM-T83x
watch kernel log for 20sec
Code:
dmesg -Tw|grep proca
if proca messages appear open /vendor/etc/init/pa_daemon_qsee.rc and comment the lines
You should enable "Secure startup" in "Biometrics and security" settings. Recovery should fail reading encrypted drive sda27 because of its crypto flags and logical mapping.
Which plugins to use
Similarly to Mi9, collecting what i think is useful to keep on stock rooted firmware.
Magisk plugins:
* Riru - Core, Riru - Ed Exposed -- brings XPosed to Pie. Need also installer. Make a choice SandHook/Yahfa bipolar release, i never found out which one is better.
* libsecure_storage companion -- helps us keep the bluetooth pairings
* (optional) YouTube Vanced black themed -- brings usable YouTube experience. Unfortunately it's now a horror to install (v15), but v14 from Magisk still works.
* (optional) Move certificates -- perhaps
* (impossible) QuickSwitch -- there's no pill but Samsung custom recents... oh how glad i am for it now! Android10 cancelled this fantastic Pie pill already and you can scroll apps in OneUI!
XPosed plugins:
* Xposed Edge Pro -- a must have and best plugin
* XPrivacy -- Screw the big brother. Must have of the century. Disabling analytics, tracking, telephony, network, identification for all visible apps and all Google and Samsung apps with some exceptions.
* Firefds kit -- so this is our main customization app irrelevant here: ..and enables the very important call recording, which is beutifully integrated into call history. Bye bye external apps. Also for Samsungs it forces Restart "recovery"
* (optional) Xposed Dex -- some tweaks
* (optional) afWall -- Problems with this firewall and some VPN clients for years. Using AdGuard now and happy. It can even control DNS, no need one of those paid lausy apps. This plugin should by disabled in Xposed.
* (optional) Exi for Swiftkey -- you can make Swiftkey great again, GBoard is still the best, Samsung keyboard is very good, but too tall and leaves gap in fullscreen mode
Root apps:
* TitaniumBackup -- a must since Android was born
* Adaway -- a must but with AdGuard not so.. but i use both
* AdGuard -- can filter more and can amend requests.. that's a game changer. You can have a efficient proxy when rooted.
* 3C toolbox -- too helpful not to pay for the biggest package
* (optional) Root Essentials -- a multitool, have a look
* (optional) MiXplorer -- best file manager, replaces spyware ES File explorer you had before. Edits root files comfortably even when other editors don't
* (optional) FolderSync -- best sync tool
Battery
Battery saving:
- tablet should not be neccessarily always connected, receive notifications, so why not keep it dead when the screen is off
- the key is to disable background network activity:
disable it overall by Medium Power Saving mode
disable background network for individual apps (there's "Allow background data usage" and also nice "Allow background activity" checkbox)
force it with 3C (Device Mgr\Profiler) or Adguard (App Management)
- can't see wifi switch.. to turn wifi off when screen off. no wifi scanning drainer or other "intelligent" bs functions there either. just "Hotspot 2" - turn off.
- nearby scanning should be off, what a useless function of finding unknown devices - once you pair the known, what's the sense? or you keep connection 10 new bt devices each week? just a drain and endless beacon
- location can be off, and again it can be scripted by turning on only when screen is on by 3C
- not installing {LSpeed, Naptime, Servicely, FDE, LKT, Universal GMS Doze, Sysconfig patcher} here
- no signifficant doze functions here {AOD, fp icon, dt2wake, raise2wake} to speak off
- we want battery to remain flat when screen off, last tablet i had could do -1% per week! let's do it here
Other
- i like tender boot screen indicating knox off status, no need to flash boot logos
- no boot keys needed like on Tab s6
- not using multidisabler as i'm on stock and i do want encryption on every device ever
- how to launch camera quickly?? still dind't find out
- don't be afraid to use another device (mobile) as USB drive.. this way you can restore your apps directly via TitaniumBackup without copying it first! also Smart Switch can be used from non-Samsung phones, but it is as weak as Google backup ever was - no data restore

What do you do to run this exactly?

copy the file to storage. open su terminal. Get any root terminal app (ConnectBot, 3C Toolbox, or adb shell) and run as root. I run this script as autostart on each of my devices.
wifi_standby_test: first battery standby test: 37 hours to 91%, i've 'charging protection' so approx 93% that give us 0.19%/hr drain with wifi and bluetooth on. 10x less then a mobile (S10). Good start, nice 3 weeks of standby potential, but let's try medium power saving mode to squeeze it to over month of standby.

Will i loose my data while rooting? Im on Build number PPR1.180610.011.T835DDS4BSL2

doggydog2 said:
Tab S4 stock cleanup actions
phablet guide fest continues V30->Note9->6T->Mi9->S10->7T->Tab S6->Tab S4, time to provide some thoughts, easy to click links and guides. Goal is to have a clean device after each update, and have a helper script running at boot or on demand. This is a tablet, we want to achieve flat battery graphs when it is unused (picture attached), hopefully charge once a week with slight usage.
Debloat
What the script does:
* choose 8 categories of app removal, in the beginning of the file
for each say 0=skip 1=remove 2=revert back
* use more switch to disable some questionable/helpful stuff
* disable up to 80 apps with possibility to revert back
* remove usage access for google (do manually)
* remove device admin backdoor "Find My Mobile", you won't recover stolen device this way lol, it doesn't work with Secure Startup! it's useful for Govt.
* remove proca (which was slowing down tablet after rooting), if it doesn't work from your shell, edit the file as below
Tested ok on March stock Pie firmware. Samsung has too much bloatware installed, and requires shocking permissions to run some basic services. We will further need to reclaim privacy. As for debloat list, i've cooked the list based on knowledge of each process, its current presence in the Pie firmware, and what would fit the tablet usage. In this case, i'm leaving Samsung account, Galaxy shop and few pen apps and we assume XPrivacy is sending these snitch services bogus personal details.
Download: (file attached)
Installation:
- run in su terminal once or add to any startup script (3C\Device mgr\Scheduler can assign scripts from /storage/emulated/0/Android/data/ccc71.at/scripts), or to magisk
Rooting
We want encryption. There are no ROMs, and TWRP can be used for many other tasks without access to your files.
OEM unlock in dev settings
when turned off and rather plugged it to your PC with drivers installed, hold Power & Vol+ & Vol- til you see download screen, confirm with Vol+
in ODIN, slap TWRP into AP while "Auto reboot" is unchecked
hold Power & Vol- to exit download mode, then Power & Vol+ to enter recovery
in TWRP, slap kernel and Magisk into tablet from SD card or USB (can be usb flash, can be other mobile, can be adb)
in TWRP, say boot to system and wait 5min
check Magisk app status, enable USB debugging in dev settings
kernel: WETA recovery: TWRP 3.3.1 for PIE SM-T83x
watch kernel log for 20sec
Code:
dmesg -Tw|grep proca
if proca messages appear open /vendor/etc/init/pa_daemon_qsee.rc and comment the lines
You should enable "Secure startup" in "Biometrics and security" settings. Recovery should fail reading encrypted drive sda27 because of its crypto flags and logical mapping.
Which plugins to use
Similarly to Mi9, collecting what i think is useful to keep on stock rooted firmware.
Magisk plugins:
* Riru - Core, Riru - Ed Exposed -- brings XPosed to Pie. Need also installer. Make a choice SandHook/Yahfa bipolar release, i never found out which one is better.
* libsecure_storage companion -- helps us keep the bluetooth pairings
* (optional) YouTube Vanced black themed -- brings usable YouTube experience. Unfortunately it's now a horror to install (v15), but v14 from Magisk still works.
* (optional) Move certificates -- perhaps
* (impossible) QuickSwitch -- there's no pill but Samsung custom recents... oh how glad i am for it now! Android10 cancelled this fantastic Pie pill already and you can scroll apps in OneUI!
XPosed plugins:
* Xposed Edge Pro -- a must have and best plugin
* XPrivacy -- Screw the big brother. Must have of the century. Disabling analytics, tracking, telephony, network, identification for all visible apps and all Google and Samsung apps with some exceptions.
* Firefds kit -- so this is our main customization app irrelevant here: ..and enables the very important call recording, which is beutifully integrated into call history. Bye bye external apps. Also for Samsungs it forces Restart "recovery"
* (optional) Xposed Dex -- some tweaks
* (optional) afWall -- Problems with this firewall and some VPN clients for years. Using AdGuard now and happy. It can even control DNS, no need one of those paid lausy apps. This plugin should by disabled in Xposed.
* (optional) Exi for Swiftkey -- you can make Swiftkey great again, GBoard is still the best, Samsung keyboard is very good, but too tall and leaves gap in fullscreen mode
Root apps:
* TitaniumBackup -- a must since Android was born
* Adaway -- a must but with AdGuard not so.. but i use both
* AdGuard -- can filter more and can amend requests.. that's a game changer. You can have a efficient proxy when rooted.
* 3C toolbox -- too helpful not to pay for the biggest package
* (optional) Root Essentials -- a multitool, have a look
* (optional) MiXplorer -- best file manager, replaces spyware ES File explorer you had before. Edits root files comfortably even when other editors don't
* (optional) FolderSync -- best sync tool
Battery
Battery saving:
- tablet should not be neccessarily always connected, receive notifications, so why not keep it dead when the screen is off
- the key is to disable background network activity:
disable it overall by Medium Power Saving mode
disable background network for individual apps (there's "Allow background data usage" and also nice "Allow background activity" checkbox)
force it with 3C (Device Mgr\Profiler) or Adguard (App Management)
- can't see wifi switch.. to turn wifi off when screen off. no wifi scanning drainer or other "intelligent" bs functions there either. just "Hotspot 2" - turn off.
- nearby scanning should be off, what a useless function of finding unknown devices - once you pair the known, what's the sense? or you keep connection 10 new bt devices each week? just a drain and endless beacon
- location can be off, and again it can be scripted by turning on only when screen is on by 3C
- not installing {LSpeed, Naptime, Servicely, FDE, LKT, Universal GMS Doze, Sysconfig patcher} here
- no signifficant doze functions here {AOD, fp icon, dt2wake, raise2wake} to speak off
- we want battery to remain flat when screen off, last tablet i had could do -1% per week! let's do it here
Other
- i like tender boot screen indicating knox off status, no need to flash boot logos
- no boot keys needed like on Tab s6
- not using multidisabler as i'm on stock and i do want encryption on every device ever
- how to launch camera quickly?? still dind't find out
- don't be afraid to use another device (mobile) as USB drive.. this way you can restore your apps directly via TitaniumBackup without copying it first! also Smart Switch can be used from non-Samsung phones, but it is as weak as Google backup ever was - no data restore
Click to expand...
Click to collapse
Bro. Is it possible to do this without losing data?

mayank_nigam said:
Will i loose my data while rooting? Im on Build number PPR1.180610.011.T835DDS4BSL2
Click to expand...
Click to collapse
backup, try and let us know the reason why usual root methods wipe data is to remove encryption, we don't need that.

doggydog2 said:
backup, try and let us know the reason why usual root methods wipe data is to remove encryption, we don't need that.
Click to expand...
Click to collapse
So if we do it without turning oem unlock, will it work?
---------- Post added at 04:41 PM ---------- Previous post was at 04:26 PM ----------
doggydog2 said:
backup, try and let us know the reason why usual root methods wipe data is to remove encryption, we don't need that.
Click to expand...
Click to collapse
Any suggestions on backup method?

mayank_nigam said:
So if we do it without turning oem unlock, will it work?
Click to expand...
Click to collapse
ah i see... you need this checkbox unlocked to flash. this device will wipe itself if you just toggle the checkbox. so in the end, data will be wiped in transition from unrooted state.
and regarding backup, just conventional methods like google backup or deeper cable backup by Helium which can partially substitute TitaniumBackup on unrooted device.

How did you get Weta running on the March firmware when it isn't supported?
NM, I see you just used the kernel part.
Running this script did very little for me - no options were given, just a few packages disabled before it errored out

Thank you for the script! It made a great difference on my tab s4, I was able to enable back Chrome and Google.
My device was lagging before... Thanks again for the write up...

Any suggestions on installing apps to sd card? The option under dev options, to force install apps to sd card is not really good.

I just purchased a refurb Tab S4, it should be arriving over the weekend. The seller notes that the S4 is on Oreo.
I noticed references to Pie here. Should boot and I let the tablet update to the latest release from Samsung, and then root / debloat as described in this thread after the Pie update?

¿GotJazz? said:
I just purchased a refurb Tab S4, it should be arriving over the weekend. The seller notes that the S4 is on Oreo.
I noticed references to Pie here. Should boot and I let the tablet update to the latest release from Samsung, and then root / debloat as described in this thread after the Pie update?
Click to expand...
Click to collapse
My Tab S4 arrived today. Should I allow any updates from Samsung be installed before I run through the rooting process described here, or should I do the rooting before getting the Samsung updates?

¿GotJazz? said:
My Tab S4 arrived today. Should I allow any updates from Samsung be installed before I run through the rooting process described here, or should I do the rooting before getting the Samsung updates?
Click to expand...
Click to collapse
yes..why rooting an old version.. no OTAs later so you'd have to update manually again.

doggydog2 said:
yes..why rooting an old version.. no OTAs later so you'd have to update manually again.
Click to expand...
Click to collapse
Thanks!
But, as it turns out ... I won't be able to root or debloat anyways. I purchased a refurb Tab S4 that appears to be in excellent like-new shape, but it was also mislabeled on Amazon.
Instead of getting a SM-T830, I received a SM-T837T (T-Mobile version). I plan on getting it unlocked so that I can use it on AT&T, but from what I understand, it's unrootable.
Thanks, tho!
¿GJ?

doggydog2 said:
yes..why rooting an old version.. no OTAs later so you'd have to update manually again.
Click to expand...
Click to collapse
I was wondering about this. So there is no way to update once rooted, other than a full clean flash and start again?

ghoulie said:
I was wondering about this. So there is no way to update once rooted, other than a full clean flash and start again?
Click to expand...
Click to collapse
later use Frija to get new firmware and update. cleaning is only on first root as we can't avoid it when switching the OEM lock.

This thread is really one of the best thread for tab S4
Thanks for that
Sent from my SM-T830 using Tapatalk

Question, now that 10 is out will you update the OP, some things change.
I am not sure things like exposed can be update? Tried and get some reboot.
Proca not present and other things.
Thank you for your work
Sent from my SM-T830 using Tapatalk

Looks like it is not working anymore on Android 10:
https://forum.xda-developers.com/galaxy-tab-s4/development/rom-t4137013