[ROM][I9305XXUFNI3][KK4.4.4] DLite Open Source Flavour - Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve

Hi,
i'd like to share my de-bloated & lite arrangement for GT-I9305 with you and hope some of you may like it, or even find it useful!
It all started as an experiment... for personal use only
I used an early alpha release of this tweaked ROM (system size < 1GB) to test hardware functionality
and power consumption of one of my devices.
After a while i thought it might be useful for others as well.
Some more words about my intention:
I thought about a stable stock ROM which is as close as possible to the official release but more essential.
As it all started on an experimental base and was focused on best effort, i decided not to start from scratch.
Of course this would have been the more elegant way, but basic work had already been done.
So special thanks go out to kenar2 for dumping, deodexing, zip-aligning and prepare the KK stock ROM for CWM flashing.
A lot of research has been done to seperate the essential parts from the extra stuff.
In the end i stripped of all apps which are not needed for the basic features of the system (tons of MBytes).
Additionally i tried to reduce the background traffic and services to the bare minimum.
Some basic addons (mainly apps) then got implemented to make the ROM at least usable.
I decided to choose mostly open source and non-playstore apps (there are some exceptions though)
and remove Google as far as possible.
The rest is barely as is, so no tweaks at apk level... at least for now.
The ROM is quite stable and you should check it out, if you...
... want good battery life
... like reduced background processes
... like some of the stock goodies (WiFi direct, MHL (HDMI) support, NFC)
... always wanted a good base to implement your own features
... like minimalistic ROMs
So here it is:
I9305XXUFNI3-DLite_V1
Size: 514 MB (539.169.629 Bytes)
MD5: bf481f11f7923f4c2f941a083700f587
- Based on kenar2's I9305XXUFNI3 KK 4.4.4
- Using kernel AGNi pureSTOCK V5.5 from psndna88
boot.img preconfigured and arranged by djb77 for TGP_I9305_XXUFNJ1_v20.20
UPDATE:
I created my own kernel based on psndna88 source branch pureSTOCK-I9305-4.4.4:
- applied offline charging patch
- removed f2fs support in config
- support for FTDI USB serial adaptors
- cleaned/shrinked down initrd
See attachment below!
Clean and mean... works very nice :victory:
- Implemented Superuser V2.45 from Chainfire
(formerly used GPL'd superuser from Koush, but unfortunately it's not ready for SElinux right now)
- Cleany removed KNOX (i don't use it)
- Removed Google apps and background services (not touching any jar files though, mainly for stability reason)
- Disabled and removed SetupWizard's at first boot (i don't need it)
- Added some open source apps mainly taken from http://f-droid.org
Firefox Version 35.0 (License: MPL2)
K-9 Mail Version 5.002 (License: Apache2)
Apollo Version 1.1 (License: Apache2)
Sound Recorder Version 1.0 (License: Apache2)
CM File Manager V1.0.2 taken from cm-11-20141030-NIGHTLY-i9305.zip (License: Apache2)
Hacker's Keyboard Version v1.37 (License: Apache2)
- I replaced Samsungs calendar app with a lightweight one, because I personally didn't like the look
of stock S-Planner and later versions are much too bloated.
Though my intention was to use open source apps, this one is simply the best and lightweight calendar app:
aCalendar V1.0.2 (Free version, Copyright Tapir Apps GmbH)
If you like a very basic calendar, look at f-droid.org again:
Standalone Calendar Version standalone-1.2 (License: Apache2)
Prerequisites:
- You'll need custom recovery installed first.
I recommend philz touch recovery 6.48.4 for i9305
Boot to recovery and do a clean wipe of cache and data partition.
Afterwards step to installation from external SDcard.
- If you're coming from an older version (e.g. 4.3) you'll need a KK modem firmware on your device to use this ROM.
I recommend I9305XXUFNI3 modem firmware to be installed before or directly after ROM has been written to flash.
Place the modem file and the ROM file on your SDcard and boot to recovery.
Get the modem files here:
http://sourceforge.net/projects/djb-tgp/files/CWM_Flashables/Modems/4.4.4 Modems/
http://sourceforge.net/projects/amchaprojekt/files/Modems/
Credits go to djb77 and kenar2 again for distributing these files!
- The ROM should work independent of the bootloader version...
... but has only been tested with old bootloader yet.
So as always... i am not responsible for anything you do with your phone. Please keep that in mind!!
Known issues:
- As i did not tweak any apk or jar files so far, there are rare things in the settings that may stop the process.
E.g. setting notfication sound of non existing Samsung Apps, as there are Samsungs Email and S Planner.
(Maybe this will result in a TODO list, if there's time and energy to tweak apk's)
- I decided to remove SetupWizard2013 (Samsung) & SetupWizard (Google) and blocked the processes
from being started by setting the build.prop variable ro.setupwizard.mode=DISABLED
I'm not sure about any flaws, though there might be some side effects (see next two issues).
- At some point i realized that the multiwindow mode has no effect anymore
- The edit button of the notification panel (upper right corner) is not working anymore
- You may notice some messages in logcat from McDaemon stating: Failed to obtain version info Mobicore...
This is a know issue on deodexed stock ROMs:
http://forum.xda-developers.com/showpost.php?p=43037197&postcount=9
Nfc payment will not work on deodex rom because of signature checks and looking for particular
odex and odex framework files.
(See 2nd post for a possible workaround)
Further advice:
- I really suggest to install VLC player from f-droid and check it out.
This app works pretty well and supports a lot of video formats.
It also serves video on an external monitor via MHL/HDMI!!
- Press the the menu button in the Data Usage settings and disable "auto sync data".
There's nothing to sync with and it will close some backup services running in background
- If you don't like background traffic or make the ROM even more "silent",
think about using a firewall like AFWall+ or restrict app access with Xposed+Xprivacy.
- You might easily encrypt email and files by using APG
Remark:
- There's nothing to worry about the pre-configured kernel image, but tweaking some of the init.*.rc files
would be a good thing to do .
- While using Koush's GPL'd Superuser i observed "Superuser granted to Shell" messages if an app is crashing.
Don't worry too much about it, the message will go away in a couple of seconds and i realized no strange issues.
From what i got so far is, that it might be related to kernel rights management or SElinux extension in specific.
https://github.com/nelenkov/cryptfs-password-manager/issues/5
- During testing i discovered a useful command to identify camera firmware.
On your dialer use *#34971539#
There are multiple threads covering secret codes already... i didn't knew this one before.
Further remarks:
- As Android "is" Google, it is not possible to block background traffic to Mountain View completely.
From time to time system apps use certain service ports to initiate transmissions.
I did not observe any Samsung related traffic anymore though.
Anyway, it was really interesting to observe the effects at certain milestones, while playing with this ROM.
- Users who like to share everything, like cloud services or like to sync all data with Google or Samsung,
should use another ROM.
- I don't like to disappoint you, but this ROM is only a shrinked down version of stock I9305XXUFNI3.
No blasting features, no extras, no special addons...
If you don't like it, tell me... but be polite.
If you like it, leave a comment or at least press thanks button!
O.k. enough talking.
CREDITS:
@kenar2 for his great work and modded Stock ROMs
@djb77 for some advice and also building awesome ROMs with a great user experience
@psndna88 for his extensive work on AGNi kernel
@Chainfire for developing a full featured Superuser
@Phil3759 for his work on PhilZ Touch CWM Advanced Edition and providing this great tool
Contributers at f-droid in general and all the curious and openminded people here at XDA forum.
Have fun!
scholbert

Additional stuff...
Look:
Screenshots
As requested...
Wallpaper shameless taken from here:
http://wallpaperswiki.org/wallpaper-lines-lines-stream/
You'll find no copyright notes on this page... so hopefully it's o.k. for the creator to use it in a ROM :angel:
Removals:
See the text file attached (removals.txt).
Looks a bit ugly though, because i'm too lazy to format it :silly:
Addons:
See the text file attached (addons.txt).
This is only a file listing, tweaks are not included...
Specials:
Mobicore error message workaround (not implemented and tested yet):
- Prevent the start of mobicore service in file init.smdk4x12.rc by comment out these lines:
Code:
# mobicoreservice
mcDriverDaemon /system/bin/mcDriverDaemon -r /system/app/FFFFFFFF000000000000000000000001.drbin -r /system/app/mcRegistry/ffffffffd0000000000000000000000a.tlbin
class core
user system
group system
Enjoy!
scholbert

Further info...
I'm not a paranoid person, but i like privacy.
It would be nice, if users are aware of things going on on their mobile devices.
Information about remaining services (will try to keep this updated):
ResourceManager
A.k.a MyScript ResourceManager is related to handwriting recognition and pen writing.
This service was not removed, but could easily be disabled in Settings -> Application Manager
Search for MyScript Resource Manager in all applications and disable this service.
I observed some connections to Amazon servers, maybe MyScript makes use of Amazon's cloud service.
Reference:
https://dev.myscript.com/technology/
FixmoISA and MDMApp
The Samsung Knox platform provides Application Programming Interfaces for use by third-party vendors to develop tools to enable security controls required by the Samsung Knox Android STIG. APIs include:
The Mobile Device Management API includes more than 500 policies and 1100 interfaces to be called by any MDM agent.
A vendor can implement an MDM solution that can meet or exceed requirements.
Vendors implementing MDM API include Mobile Iron, AirWatch, SOTI, and Fixmo.
The Integrity Services Layer (ISL) provides an interface that allows third party vendors to implement an Integrity Services Agent (ISA) to communicate with the on-device MDM agent.
The agent provides on-device scanning for integrity failures and reports results to the MDM server.
Solutions implementing the ISL include Fixmo ISA.
The MDM API includes VPN policies and interfaces to allow an administrator to configure third-party IPSec VPN solutions implementing the MDM interfaces.
This enables the device to connect to DoD networks using a FIPS 140-2 validated cryptographic module to protect data in transit.
Solutions that implement the MDM interface include Mocana KeyVPN and Inside Secure VPN.
The Smart Card API provides an interface that allows third party vendors to implement smart card reader functionality,
enabling Samsung Knox Android to support the DOD Common Access Card for PKI, including user authentication, S/MIME digital signatures, and device unlock.
Solutions that implement this interface include the Biometrics Associates Bluetooth Smart Card Reader.
Reference:
http://gcn.com/articles/2013/05/29/breakdown-dod-security-controls--ios-android.aspx?m=1
http://www.businesswire.com/news/ho...oration-Samsung-Enhanced-Support#.VNIIpSyhymw
OmaCP and OmaDrmPopup
OMA Client Provisioning is a device management protocol specified by the Open Mobile Alliance (OMA) Device Management (DM) Working Group.
The OMA CP protocol covers WAP provisioning with minimal user interaction, typically over-the-air or via SIM Card.
Reference:
http://en.wikipedia.org/wiki/OMA_Client_Provisioning
http://technical.openmobilealliance...-information/release-program/current-releases
Don't be evil...
scholbert

scholbert said:
I'm not a paranoid person, but i like privacy.
It would be nice, if users are aware of things going on on their mobile devices.
Information about remaining services (will try to keep this updated):
FixmoISA and MDMApp
The Samsung Knox platform provides Application Programming Interfaces for use by third-party vendors to develop tools to enable security controls required by the Samsung Knox Android STIG. APIs include:
The Mobile Device Management API includes more than 500 policies and 1100 interfaces to be called by any MDM agent.
A vendor can implement an MDM solution that can meet or exceed requirements.
Vendors implementing MDM API include Mobile Iron, AirWatch, SOTI, and Fixmo.
The Integrity Services Layer (ISL) provides an interface that allows third party vendors to implement an Integrity Services Agent (ISA) to communicate with the on-device MDM agent.
The agent provides on-device scanning for integrity failures and reports results to the MDM server.
Solutions implementing the ISL include Fixmo ISA.
The MDM API includes VPN policies and interfaces to allow an administrator to configure third-party IPSec VPN solutions implementing the MDM interfaces.
This enables the device to connect to DoD networks using a FIPS 140-2 validated cryptographic module to protect data in transit.
Solutions that implement the MDM interface include Mocana KeyVPN and Inside Secure VPN.
The Smart Card API provides an interface that allows third party vendors to implement smart card reader functionality,
enabling Samsung Knox Android to support the DOD Common Access Card for PKI, including user authentication, S/MIME digital signatures, and device unlock.
Solutions that implement this interface include the Biometrics Associates Bluetooth Smart Card Reader.
Reference:
http://gcn.com/articles/2013/05/29/breakdown-dod-security-controls--ios-android.aspx?m=1
http://www.businesswire.com/news/ho...oration-Samsung-Enhanced-Support#.VNIIpSyhymw
OmaCP and OmaDrmPopup
OMA Client Provisioning is a device management protocol specified by the Open Mobile Alliance (OMA) Device Management (DM) Working Group.
The OMA CP protocol covers WAP provisioning with minimal user interaction, typically over-the-air or via SIM Card.
Reference:
http://en.wikipedia.org/wiki/OMA_Client_Provisioning
http://technical.openmobilealliance...-information/release-program/current-releases
Don't be evil...
scholbert
Click to expand...
Click to collapse
Can you post screenshot of rom?
I don' have idea how it is

Hi andreazimba!
andreazimba said:
Can you post screenshot of rom?
I don' have idea how it is
Click to expand...
Click to collapse
I will add a screenshot in 2nd post tomorrow.
There's nothing special with the look... just stock TouchWiz and custom wallpaper
Cheers,
scholbert

Nice work on the ROM
The NI3 base is a bit old though. I can share with you a cleanly built NL1 if you would like to use that (with SU, BuxyBox, Deodexed + Zipaligned).
With that Mobicore fix, is that a kernel-related fix? If so I can patch my existing modded version of AGNi.

Hi djb77!
djb77 said:
Nice work on the ROM
Click to expand...
Click to collapse
Thanks a lot for this positiv feedback!
djb77 said:
The NI3 base is a bit old though. I can share with you a cleanly built NL1 if you would like to use that (with SU, BuxyBox, Deodexed + Zipaligned).
Click to expand...
Click to collapse
Yeah you're right, it's not the latest...
The reason i started with this release is quite simple.
I once extracted an EXT4-image from the original UFNI3 firmware and started investigation based on this ROM.
It's o.k. for me, because i did not realize any major bugs or malfunction.
The UFNI3 modem gave got quality as well.
But anyway, it's a nice offer and i may come back to it :fingers-crossed:
... and i'll try to find some change notes for the latest stock ROMs as well.
djb77 said:
With that Mobicore fix, is that a kernel-related fix? If so I can patch my existing modded version of AGNi.
Click to expand...
Click to collapse
We better not call it a fix... it is a ramdisk workaround and it was my best guess, that it might prevent the error message coming from McDaemon.
But if i look at the snippet in my post again, this entry is the call of mcDriverDeamon, which seems to be a different tool to load proprietary stuff before the upper service get's started
BTW it has to be checked if blocking the Mobicore service would harm NFC in any way.
If so it would be better to accept the errors in logcat or try to search for a real fix.
Do you know, if odexed and deodexed may live together in harmony?
Maybe it's worth a try to move the original NFC files (apk+odex) to the ROM and see what happens.
The signature of security check should match then...
Anyway this not my focus of work right now.
Thanks again for the feedback and have nice day!!!
scholbert

Deodexing sholdn't break files, but it would be often best to have all your files one way or another (odex or deodex)

djb77 said:
Deodexing sholdn't break files, but it would be often best to have all your files one way or another (odex or deodex)
Click to expand...
Click to collapse
Deodexing will not break files from a functional view, that's correct...
... but re-assemble odexed files (apk+odex) to a deodexed package (apk only) will do from the binary point of view.
So if there's an integrity check of apk+odex with some security mechanism/checksum before loading contents to memory a deodexed file will break this check. That's at least what i conclude from the thread i refered to in my first post.
Anyway i dont' know enough about the Mobicore Daemon, so it's just guessing how it interacts with all the proprietary files.
Another perhaps more simple question is about camera firmware:
I made a dump of camera firmware by dialing *#34971539# and press the dump button.
Does anyone know at which location this file gets stored afterwards???
And finally.. :
While looking into the init files of AGNi ramdisk, i stumbled over these mount commands in init.agnimounts.rc (snippet):
Code:
...
mount ext4 /dev/block/mmcblk0p13 /system ro wait noatime nodiratime nosuid nodev discard
mount f2fs /dev/block/mmcblk0p13 /system ro wait noatime nodiratime nosuid nodev discard,background_gc=off,inline_xattr,active_logs=2
...
I know that psndna88's pureSTOCK have f2fs support compiled in (that's at least what i assume after i looked into his config).
Is it common practice to mount f2fs over ext4 filesystem
... mmmh, think i'm going of topic a little bit
Best regards,
scholbert

Camera firmware gets dumped to /data/cfw if I'm correct.
My friend MaHo_66 has actually come up with a patch which can be included into ROMs Check out this post HERE, you should be able to use these files in your ROM (just give MaHo_66 credit obviously).
F2FS I can't help you with, never used it or really looked into it

Hey djb77,
thanks again for your help!
djb77 said:
Camera firmware gets dumped to /data/cfw if I'm correct.
Click to expand...
Click to collapse
Got that folder, but no dump inside... maybe i'll start some further investigation.
Apart from that my camera works very well, with this ROM, its just for educational purpose
djb77 said:
My friend MaHo_66 has actually come up with a patch which can be included into ROMs Check out this post HERE, you should be able to use these files in your ROM (just give MaHo_66 credit obviously).
Click to expand...
Click to collapse
Yeah thanks for the hint, i knew that patch/collection already... don't know if it's useful for me right now.
Depends on people's reports... if there are any
djb77 said:
F2FS I can't help you with, never used it or really looked into it
Click to expand...
Click to collapse
No problem, i guess i already found out.
Both filesystems need a single mount to be accessed.
Depending on the filesystem of the partition in use, one of the commands will succeed, the other one would always fail.
So this "double" entry will always match, wether you use ext4 or f2fs on your partitions.
Seems that psndna88 decided this would be the easiest way to support both filesystems.
Regards,
scholbert

Hi,
not sure if anyone even tested my release, might be a bit too stripped down for most.
Maybe i'm little late with this ROM and most people already jumped to Lollipop ROMs.
Anyway, i'm testing for a few weeks now and the ROM still behaves rock solid.
In the meantime i made an AnTuTu bench as well and reached a score of ~26394, which is not that bad for a stock based ROM i guess.
Battery time is still nice, while wireless networks (WiFi, 3G/LTE) are the most hungry suckers
Though there's less interest, i think about updating to the latest 4.4.4 release and give the ROM a few additional tweaks as well.
I guess i'll integrate my own boot.img with a customized kernel including the offline charging fix (kernel will be based on psndna88's sources).
No need to hurry though
Rock on!
scholbert

RazvanG said:
not on stock froyo, no
Click to expand...
Click to collapse
i am going to try this rom , man. seems very good rom.
how do you compare the battery life of your rom to the original stock rom?
Sent from my GT-I9305 using XDA Free mobile app

scholbert said:
Hi,
Though there's less interest, i think about updating to the latest 4.4.4 release and give the ROM a few additional tweaks as well.
I guess i'll integrate my own boot.img with a customized kernel including the offline charging fix (kernel will be based on psndna88's sources).
No need to hurry though
scholbert
Click to expand...
Click to collapse
as long as xposed is halway useless on LP, I'll personally stick to KitKats
if in doubt, I'm really interested in testing your new release - actually I'm pretty much tired with wealth of options in stock and stock derivated roms - when I was testing a CM11 build the only things I really missed from Touchwiz were stock multiwindow and stock camera

Hey thanks for your feedback!
anguslaw said:
i am going to try this rom , man. seems very good rom.
how do you compare the battery life of your rom to the original stock rom?
Click to expand...
Click to collapse
Mmmh, got no direct comparison.
Anyway as this is stock kernel, but with reduced background services and other stuff removed, there might be only a slight difference.
Background services may have significant influence on battery life if connected to the network.
Judge yourself... but keep in mind that Google services are completely removed in this ROM.
adamuadamu said:
as long as xposed is halway useless on LP, I'll personally stick to KitKats
if in doubt, I'm really interested in testing your new release - actually I'm pretty much tired with wealth of options in stock and stock derivated roms - when I was testing a CM11 build the only things I really missed from Touchwiz were stock multiwindow and stock camera
Click to expand...
Click to collapse
AFAIK multiwindow is non-functional in this release. You could set it in the settings, but the drawer is not showing up on home screen.
Tried to find out what happened or which part is missing, but no fix right now. Maybe HelpHub.apk is required, because i found some referals in the apk.
As i did not use MultiWindow it in the past, i don't miss it.
Anyway, camera works nice, found no flaws here :good:
Xposed for Lollipop has been created, but i guess you're looking for specific modules, which are not working right now...
Development for Xposed on LP has just begun :fingers-crossed:
Regards,
scholbert

i have tried it out this afternoon. very smooth and clean. but i find that i just cannot live without google. all my contact was sync to google. and i rely on google plus photos to autoback up my photos.
Sent from my GT-I9305 using XDA Free mobile app

is this rom continous update or not??

Related

Help! Cm6 rom is so close to perfection :'(

Once again I am here seeking the help from developers for my phone. Which is not the XT720 (XT701 instead), but I really don't know where else to turn.
I was restless again, so then I went and started looking for roms. I found this one:
Speed XT701 2.2.1版 beta7 搞掂wifi
This is really new and is running CM6 based moto blur extremely smoothly. Search on google and click the first few links to see the interface. Amazing as always, the CM roms. The touch sensitivity is ON PAR with the Iphone 4. I was so glad that everything was working - Camera, SDcard, SERVICE, SMS, CALLING, all working so perfectly. It was completely different from the CM 7 mod.
And honestly, It really seems even faster than the CM7 rom. I read from the translated description that it is using "smart200mhz to 600 mhz" processing for superb battery and so on. It really does have a lot of attractive features and usual and completely destroys the 2.1 rom.
Now comes the horrible, devastating part. No wifi. .
I did the 3 wipes, updated, and 3 wipes again, and it still had no wifi.
Right now I'm really leaning towards sticking to this rom. My solution is to keep my backup of the 2.1 stock, and nandroid over to it when I need to so that I can download new apps, back then up in SD, and then nandroid back.
Can anyone please help me figure out how to get wifi? I'll donate from paypal if someone can help me resolve this wifi issue. . Just terrible, this problem. So close.
firzen_net said:
Once again I am here seeking the help from developers for my phone. Which is not the XT720 (XT701 instead), but I really don't know where else to turn.
I was restless again, so then I went and started looking for roms. I found this one:
Speed XT701 2.2.1版 beta7 搞掂wifi
This is really new and is running CM6 based moto blur extremely smoothly. Search on google and click the first few links to see the interface. Amazing as always, the CM roms. The touch sensitivity is ON PAR with the Iphone 4. I was so glad that everything was working - Camera, SDcard, SERVICE, SMS, CALLING, all working so perfectly. It was completely different from the CM 7 mod.
And honestly, It really seems even faster than the CM7 rom. I read from the translated description that it is using "smart200mhz to 600 mhz" processing for superb battery and so on. It really does have a lot of attractive features and usual and completely destroys the 2.1 rom.
Now comes the horrible, devastating part. No wifi. .
I did the 3 wipes, updated, and 3 wipes again, and it still had no wifi.
Right now I'm really leaning towards sticking to this rom. My solution is to keep my backup of the 2.1 stock, and nandroid over to it when I need to so that I can download new apps, back then up in SD, and then nandroid back.
Can anyone please help me figure out how to get wifi? I'll donate from paypal if someone can help me resolve this wifi issue. . Just terrible, this problem. So close.
Click to expand...
Click to collapse
I'm sure our dev's would love to help as it might help with our phone as well. First can you post a link to this amazing ROM please? Thank you!
Look forward to seeing this, but...
firzen_net said:
The touch sensitivity is ON PAR with the Iphone 4.
Click to expand...
Click to collapse
...what's that supposed to mean? I've never had a problem EVER with the phone registering my touches and my touches can be me barely touching the screen (i.e. I can't imagine how anything can actually be better than that).
Maybe he meant responsiveness of the UI? Just a guess. And yes I agree the touches on the phone is already very good in your sense.
syrenz said:
Look forward to seeing this, but...
...what's that supposed to mean? I've never had a problem EVER with the phone registering my touches and my touches can be me barely touching the screen (i.e. I can't imagine how anything can actually be better than that).
Click to expand...
Click to collapse
Sent from my Milestone XT720 using XDA App
For the touch sensitivity thing, I'm pretty sure its because I'm running 2.1, which is why the IPhone seemed faster with tracking my finger movement when I compared them side by side. The XT701 itself is already blazing fast, because I'ved used overclocking, setcpu, and memory manager, but then when I upgraded to this rom called the "speed beta 7" it was just overwhelming. I've never seen the phone so reactive.
The rom is a CM 6.1.2, android 2.2, so it would explain everything so much faster. I always thought I couldn't get the phone to be any faster, but this rom proved me wrong again.
Here is the link to the rom. I'm also going to be copying and pasting the post that the developers have along with the rom. It's going to be translated from Chinese into English, so it'll be rough. But you'll get the jist of what its saying.
http://u.115.com/file/dn6dnp8n
I nandroided back to my stock rom again =/. Apparently this Rom has close to daily updates so I'll wait a while. They started releasing it on the 7/18 and they're already on beta7.
Statement: As a consulting 2.2 version of the oil, therefore continue to provide useful new 2.2 ROM.
This ROM is not my production is transferred from the other forums, but I have used ever measured, easy to use just made up, hope you like
Version of the return to original author, has nothing to do with me ~
Mod Description:
This Mod is based on CM6.1.2 production, with Moto-style 2.2.1 version of the official 2.1 ROM, with a great memory, experience, ensuring smoothness and stability, and has a very strong memory recall mechanism.
And with improved functionality and greater ease of use, without adding redundant features.
This ROM native support APP2SD, support both computer and cell phone card reader (connected to a computer can not afford to card), NICAM excellent results.
CPU clocked Smart250Mhz to 600Mhz, power efficient correct, let your XT701 has a stronger fighting at the same time have sustained life.
ROM renamed Speed ​​XT701, translated as "rapid XT701", reflects the ROM features.
This Mod is currently only for a kernel customization, the future will be to consider other kernels, so there will be more than one branch.
Please note: Some functions can not achieve because the kernel is the reason, in the absence of perfect Neihe 前, Mod can not solve the problem.
701 began to decay ...
Speed ​​XT701 Beta7 stage is a more stable version, while faster than Beta1 has been greatly improved, A-GPS issues still need to look at, here adopted a compromise;
FM repair just around the corner, recommended update to this version.
Interface is slightly flawed, the next version of the repair.
2011.7.27 3:00 Updated Beta7
- New Atrix 4G interface; (blur Starter: Launcher.apk (2.39 MB) option, choose blur interface)
- Fixed dynamic Wi-Fi connection (thanks to S);
- Fixed Google Search FC;
- Streamlining the volume size;
- Increase stability;
- Add more beautiful Google Video;
- Support for 4-point touch; (thanks S)
- OC 800Mhz, standby frequency reduced to 125Mhz, more power, smoother!
- Strengthening the capacity of the hard decoding;
2011.7.26 update Beta6 Remastered 0:00
- Fixed browser FC;
- Update to the latest 3.0.27 version of the electronic marketplace;
- Update patch version of the power and temperature;
- Increase stability;
2011.7.25 0:30 Updated Beta6
- Solve the vibration problem to unlock;
- Because the library file repair Dlna caused errors;
- New dial-up interface and contact interface;
2011.7.24 10:30 update Beta5 Remastered (this can be ignored without the requirements of a friend)
- Replace defy the keyboard file, keyboard, power button and all other issues hang perfect solution
2011.7.23 10:30 update Beta5
- Replace the latest 113 version of the font, smaller, better display;
- Repair Beta4 problems (set English Bug, Android keyboard error, etc.);
- Extracted from the MOTO 4G distinctive ring;
- Add to unlock the other core vibration setting; (thanks to friends chj334499) (stability unknown)
- Replace the display of attribution in text; (thanks to friends fdwxd) (stability unknown)
- Replace the Chinese version of "MOTO mobile portal"
2011.7.22 10:30 update Beta4
- Optimize the network settings, better support for WCDMA networks, and enhance the connection speed and quality;
- The new configuration of GPS and speed;
- Force on A-GPS, to enhance positioning speed;
- Draw all the android machine configuration, integration into a machine with the XT701, collect all the network location server as a backup link;
- Configuration files using the latest CM6 0.11;
- Add cold patch, effectively reduce the temperature more than 20%; (please use this method with h ttp: / / bbs.gfan.com/android-2089915-1-1.html)
- Integrated Performance patch tested to enhance CPU performance to run sub-10%;
- Integrated the latest version of the DSI from CM6 0.11 patch, XT701 continue to increase endurance;
- Reduce the Wi-Fi scanning frequency, Wi-Fi throughout the day as more power;
- Replace CM6 0.11 the latest version of Wi-Fi and configuration files. (Not sure whether to fix dynamic)
- Completely remove the overclocking module, to save space;
- The kernel is locked, overclocking is invalid, it is deleted;
- Optimized version of the baseband added, the latest version from CM6 0.11;
- Add audio library, you can use third-party audio controller;
- Updated built-APP version;
- Add high-quality broadband talk configuration;
2011.7.21 10:30 Beta3 enhanced version update
- Added DLNA support;
- You can transfer data via WIFI and other equipment, or set up local area network to share streaming media, specifically refer to Baidu Baike.
- Repair software to download third-party market issues;
2011.7.20 10:30 update Beta3
- Re-optimize the configuration file of GPS and A-GPS files;
- In theory than in previous versions of the GPS version is better, basically reached the limit of Mod;
- Optimization of the hosts file, which greatly improve the google server connection speed; [thanks] to provide users 1179873587
- Improve the synchronization speed;
- Gmail and other google software to reduce latency;
- Replacement splash screen, more appropriate theme Moto, faster boot speed;
2011.7.19 10:30 Update Beta2
- Fixed error Android keyboard procedures;
- Streamlined some services for the Youtube upload and delete services;
- Add V @ P @ N service support;
- Streamlining the integration software, the production will follow after the official 2.1 version to make;
- Replaced with lower-resolution boot screen, improved boot speed;
- Replace the official 2.1 comes with wallpaper;
- Integrated the latest version of Moto input (from Motorola Atrix 4G);
- Change Root manager for the latest version, fix "is loaded as read-only" misplaced;
- Fixed several existing bug.
2011.7.18 18:30 update Beta1 Remastered
- Fixed multi-satellite GPS can locate the problem found;
Beta 1 update 2011.7.18 10:30
- Replace the landmark core library files, optimize media effectiveness.
- Replace the new version of CM software, a large amount of updated content, localization is not completely finished parts.
- Can be set not by third-party software to set maximum memory occupied by each program;
- Can change the screen mode and unlock the lock;
- By avoiding kernel crash DSI greatly reduces the chance of error;
- Has a more detailed set;
- Joined the GPS optimization patch, the original speed faster;
- Use of State Bank 2.1GPS configuration file, add add GPS module and the search speed so write the boot loader module list;
- Replace USB.apk the milestone comes the official Chinese version 2.2;
- Update to the latest versions of many programs;
- Add a contact interface numbers and call records to show ownership of the interface number to show ownership;
- Add to Google services pack version of the latest available version, download error correction;
- The electronic market is unable to update, talk can not update the map to the latest 5.7 version of China to speed up
- Increase Plus kit;
- You can replace the five versions of this toolbox baseband;
- Available through the Toolbox to streamline internal procedures;
- Can remove the camera sound camera;
- Can remove built-in multiple records;
- Easy to change the font;
- Minimum brightness breakthrough limit;
- Screening software function within the advertising;
...
- Streamlining the number of useless software;
- Replace the ADW as ADW.EX faster;
- Excluding services provided by voice prompts, and many other services;
- Use the native theme files, and add the mot-framework-res.apk (birth certificate);
- After extreme pressure test, the native theme with more stable characteristics, it is recommended that a friend like landscaping to restore native interface;
- With the birth certificate, you can install the software, the biological (moto software installation available)
Next Blur Beta 5 ready to try the latest version of its portable interface, please look forward to it!
Students do not envy MIUI, MIUI is based on the CM 0.1 development, and the current version has a lot of difference, and code optimization is not high.
Goal: present the mod of the already chaotic, mod rarely have their own style, hope this mod will enable students to experience the same as 2.2.1 to 2.1, and so restore the Moto mod style.
Known issues:
1. WIFI not dynamic;
(2) some special encoding video black;
3. FM is still not available;
4. Can not call recording;
(this part was in white text. I don't know if it means that its fixed or not. Because it does say that in the latest Beta7 wifi was fixed thanks to S or something)
(Note: points represent the normal running speed, running sub is the ultimate performance of a test, therefore, the common run from high up poor, but the machine is running;
For example: run the software needed to run sub-use lots of memory, ROM memory recovery efficiency is poor, will result in greatly reduced running speed after hours, but had no effect on the running sub-
So the actual speed will depend on the. )
Recommendation: To maintain the stability and speed, it is recommended to remove the JIT, of course, affect the reserves is small.
Recommended with the software: automated process killer from Kai Butler
Recommended with the script:
Swap 256M memory or more
beta 7 Download: http://u.115.com/file/dn6dnp8n
Please place this file to the root directory of cell phone coverage with the same name file (remove. Apk): init.choles.rc.apk (11.92 KB)
Downloads: 146
Yesterday, 03:47
Download the consumption of G coins 1
Brush Method: Download this package on the SD card OpenRecovery / Updates folder, the brush before you wipe 3 items.
Everything it says is true. It is fast as hell, no lag. The ONLY thing which is stopping me is the wifi, which bugs me even more, because it says here that Beta7 FIXED WIFI. I don't know why my wifi doesn't work!
interesting. I wonder what will happen if we apply this update to the running cm6 on xt720
Becarefull this could have a custom kernal that could bootloop or worst.
Sent from my Milestone using XDA Premium App
Really? I've been using this so far it's great. I've never seen my phone be so responsive ever. But there is still no Wifi. Everytime I try to connect it says, Connecting, and then Disconnected. Because of that I haven't even logged in with my account. No wifi causes the phone to run even smoother, cause a lot of background apps aren't runnning
mchlbenner said:
Becarefull this could have a custom kernal that could bootloop or worst.
Sent from my Milestone using XDA Premium App
Click to expand...
Click to collapse
firzen_net said:
Really? I've been using this so far it's great. I've never seen my phone be so responsive ever. But there is still no Wifi. Everytime I try to connect it says, Connecting, and then Disconnected. Because of that I haven't even logged in with my account. No wifi causes the phone to run even smoother, cause a lot of background apps aren't runnning
Click to expand...
Click to collapse
I think he's telling xt720 users to be careful.
Yes are kernal cant be messed
Thanks to moto locked bootloader.
Not for use it you have milestone xt720.
Sent from my Milestone using XDA Premium App
firzen_net said:
Can anyone please help me figure out how to get wifi? I'll donate from paypal if someone can help me resolve this wifi issue. . Just terrible, this problem. So close.
Click to expand...
Click to collapse
I just had a similar problem on the XT720 CM6. It turned out that wifi actually was working, but DNS lookup was not (I could use static IP in browser). I fixed it by replacing /system/xbin/busybox with a known-good version. You can test busyboxes with something like copying it to /tmp/busybox and then running (either via adb or terminal emulator):
/tmp/busybox nslookup android.com
Could you be a bit more specific Mioze7Ae. I have the busybox app; I don't think I have the terminal emulator. But I still don't understand what you mean.
I have Busybox app installed, and it says the "Status: Done!" after installing 1.18.4 :S.
As for the terminal emulator, I've heard of it but I don't have the app. So I install the app and then type that in the emulator?
EDIT: I just downloaded some Pro term emulator app. I turned on wifi, and then I typed in that code (cept I put xbin since I only installed it there) and it said:
Server: 8.8.8.8
Address 1: 8.8.8.8
nslookup: can't resolve 'android.com'
What does this mean? cause It just seems to me that my Wifi is still not working. Also, I've been seeing DNS around but I have no idea where to find it in my phone. Or DPN, something liek that but all I have in the Network settings is VPN and proxy, which is at default.
On a side note, could anyone help me find a working zip folder of Google apps for XT701/XT720/CM6? In the past I've installed them manually on android, and I've tried to use OR to flash the apps into my phone as well.
Look in the cm7 for the Motoroi thread & around post 50 there is a link to the cm website Google apps updates
With wifi connected try using the browser to go to a website via ip address instead of name. For example http://50.23.231.74/ worked, even though http://xda-developers.com/ did not. If ip addresses don't work then probably you have a different problem.
My problem right now is that I cannot even connect to the router at home (or anywhere else). It just keeps saying scanning connecting, and then looping back to scanning.
Sad thing is, just today I flashed another CM6 rom by the name of update-cm-6.1.2-XT701-Milestone-signed-by-s.zip today, and wifi worked. But then, a ton of other things stopped working so I nandroided back.
It just doesn't make sense that Wifi wouldn't work for some and not for others. I am still way too unexperienced for android.
I found it from this website, http://xt701.ghostry.cn which is sort of a jackpot for me. It has the latest releases of ROMS from China/world all uploaded onto that site. I don't know if it will be much help for XT720 developers, but that site is extremely updated.
Another slight problem which I am also overlooking for the sake of Speed is the LED being unusable. I always relied on it when my phone was on silent for texts, but now It is just gone. Any ideas how to get it back=/? Thanks for your input anyways!
So wifi is still not working. I've been reading around that it has to do with the Radio img??!? I don't get it.
I do know that this ROM doesn't have a FM radio yet, but I don't know if it has to do with my wifi.
I also tried replacing my tiwlan_drv.ko with other versions of it, but it ended up in an Error. Is it possible for me to flash a CM6 rom with a working wifi, copy the tiwlan_drv.ko file from there, and then use it on this current ROM that is not working? Like using root explorer to replace the .ko with the other roms one?
Sigh..
is this thread closed? nobody from august? i donwloaded some roms from http ://xt701.ghostry . cn and now i will install to my XT701 and see if any it's working so I can have android 2.2!!!
As long as you have xt701 your good to go.
Sent from my XT720 using XDA Premium App
i have now on my XT701 MIUI 1.12.30 Android 2.3.7 but i have some problems with network signal and when I try to call anybody the phone restarts! last night when I flased this ROM the calling was good. Strange!?!?

[APP][2.3+] PassLock 1.5.1

Since I have a lot of passwords I needed a password manager which will fit my needs. I did not want a manager that keeps my passwords safe on their servers but I want to export my db so I can have a backup! That's why I created PassLock password manager and I release it to the market for everyone.
PassLock keeps your passwords safe using AES-256bit and is free.
- You can group your passwords
- You can change/edit your records and also transfer them to an other group
- You can change your master pass
- You can import/export your database
Anyone that will give it a shot please leave feedback.
Since v1.0 I have changed some things that you can find below.
Changes in v1.5.1
Disabled auto-complete/auto-suggest words in passwords fields.(This might not work for all devices and all android versions.Trying to improve)
Changes in v1.5
-Show/Hide option when you type your master pass
-Lock database only and not exit
-Highly configurable password generator added
Devices Support
Unfortunately google does not release yet any documentation about 2.3.5 and also I can not create an AVD with this version for testing the app.
I have test it on 2.3.3(API 10) which is also has the same API with 2.3.4(API 10). If google changed the API level in 2.3.5 it might not work and I will fix it when released.
As far for the SGS2 I am not sure why is not working for some of you...Maybe it's the rom you are using?!As I can see 15 SGS2 has the app working fine!
For any other devices I have to search more so please post your device with the rom you are using and if it is working or not.
Thanks!
Note: The 3 permissions that required are just for the import/export of the database and for the ads!
Download from here
thanks, id much rather have a local manager then a cloud manager.
Showing as incompatible with my Thunderbolt. Running A05PTh30RY 1.3X which is Android 2.3.5
So why does the app need internet access?
If it's supposed to be a local pw manager i don't see the need for any network access at all, specially not internet.
Ads supported maybe
Wraios file Maybe you could add froyo support too? Very nice app.
None of my device supported, neither NI Adam nor Galaxy sII
Works great on Galaxy S XXJVP 2.3.4, Speedmod T5.
seems to work, but can I access it while on the browser to fill fields or is it strictly a look up your info in this program then go to the browser and enter it manually? (or copy paste)
Would be nice if there was an option to autofill
I just installed on my Atrix. Seems to be working okay. I will do some more testing with it later. Seems to work as advertised--good and simple. Thanks for the dev work.
Will not install to my Tmo Hd2 running Android
The app doesnt work on many phones I think you need to fix it to gain wide popularity.
But anyways Thanks
And after going to my blog, I think you will Thank me also.
See here http://www.techofweb.com/google/android-passwords-manager.html
But again I dint like its non-working on many Android devices.
Hope you will fix it soon.
@jwgizmo maybe you do not have a 2.3+ version?!
Thanks vostdev

[APP][2.3+] Encdroid - EncFS file manager w/ Dropbox/GoogleDrive integration

Hello xda-developers,
Been a follower of these forums for a while, but now its my turn to publish my own apps!
Encdroid (free)
https://play.google.com/store/apps/details?id=org.mrpdaemon.android.encdroid
Encdroid is a file manager application for Android devices to keep your files encrypted on Dropbox, Google Drive or the local storage of the device. It is compatible with EncFS so volumes created with Encdroid can be accessed on Windows/MacOS/Linux desktop and laptops and vice versa.
Hope its useful for someone out there... Any reviews/comments welcome. Oh, and its open source, so contributions welcome:
https://github.com/mrpdaemon/encdroid
Cheers, long live Android!
Thanks. Taking a look now.
Edit. You need to mention that the download on market is only for US users due to export regulations.
Sent from my HTC Desire using Tapatalk 2
jdstrydom said:
Thanks. Taking a look now.
Edit. You need to mention that the download on market is only for US users due to export regulations.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I just edited my OP.
Its because of the US export regulations around apps with encryption. I'm going through the process of notifying BIS to let me put it on all markets
Can now be downloaded from all countries.
mrpdaemon said:
Can now be downloaded from all countries.
Click to expand...
Click to collapse
Verified the downloading issue resolved. Thanks :thumbup:
Sent from my HTC Desire using Tapatalk 2
v1.1 is now available with improved layouts for phones and tablets.
Great app! just needs iv chain support in the future for the paranoid setting I'm so fond of
maniakx said:
Great app! just needs iv chain support in the future for the paranoid setting I'm so fond of
Click to expand...
Click to collapse
Thanks, I'm going to implement this sometime soon hopefully
This will protect my files, this is very good!
Installed here...
Thanks a lot!
v1.2 is out with external IV chaining support!
v1.2.2 is out with some bugfixes.
BTW, for anyone out there using Encdroid, which cloud storage service would you like to see supported next? I'm planning on implementing Google Drive first, but if a majority of folks would like to see something else I can be convinced
I would like to see on F-droid.org. Many cloud storage options don't work without API keys and unless those keys are in the source code they can't work in an F-droid.org-built app. Ubuntu One does work in the MobileOrg app so I think that may work . Anyway some kind of ssh option would be nice
mrpdaemon said:
v1.2.2 is out with some bugfixes.
BTW, for anyone out there using Encdroid, which cloud storage service would you like to see supported next? I'm planning on implementing Google Drive first, but if a majority of folks would like to see something else I can be convinced
Click to expand...
Click to collapse
UbuntuOne and Box.net would be great...
Sent from my Galaxy Nexus using Tapatalk 2
dabl8 said:
I would like to see on F-droid.org. Many cloud storage options don't work without API keys and unless those keys are in the source code they can't work in an F-droid.org-built app. Ubuntu One does work in the MobileOrg app so I think that may work . Anyway some kind of ssh option would be nice
Click to expand...
Click to collapse
Thanks for the pointer, I wasn't aware of f-droid.org before, very cool work you guys are doing there!
As you pointed out, Dropbox access requires API keys, and it is not a very good idea to commit the API keys into the repository since anyone can scrape it and use it for their own purposes and then Dropbox blames my app for their mischief. The way I have it now allows anyone to create a build of the application using their own API keys which lets them use the app with up to 5 Dropbox accounts. I've already gotten Dropbox to approve my API keys for unlimited usage, so those keys are what the Google Play store build contains, but they aren't in the repo for the reason I outlined above.
I'm thinking of a way to have f-droid build my app with Dropbox functionality - if all your build infrastructure is open source then it isn't possible for me to give you the API keys to let you do builds without disclosing the API keys to anyone else. Another alternative is for each user to obtain their own API keys and somehow give those keys to f-droid and get a custom built apk, but I'm not sure if that is possible. I could also do some build work to let my app be built without Dropbox support and have f-droid build that version, although that would significantly reduce its usefulness. I'm going to look into supporting Ubuntu One sometime in the future.
Can you elaborate what you meant by ssh option? Do you mean accessing volumes through SFTP or something?
Thanks! I've built the app already and it works fine without keys: when you try to authenticate to dropbox it crashes which isn't a big deal. I'm not sure about ssh: I know some of the f-droid guys like to use dropbear ssh server on their phone which allows their computer to sync via an rsync script. There are some problems building the Dropbear frontend app and I think it needs root so it's not for everyone. I know MobileOrg can sync via ssh: https://github.com/matburt/mobileorg-android using this library http://www.jcraft.com/jsch/
I was looking for something like that. Nice work.
rsync is the usual way you would synchronize directories over ssh. It is included in Cyanogenmod but you wouldn't find it anywhere else. There is a frontend called Rsyncdroid but there is no source code for the rsync binaries. F-droid.org will probably look into building Rsyncdroid with the Cyanogenmod source. Until then you'd have to call it via the terminal or a script manager which would kind of limit its appeal. Very soon, F-droid.org will have the Ubuntu One Files app and that would be a way to (sort of) synchronize a directory.
Version 1.3 released with:
- Add support for volumes on external SD card
- Major performance improvement for volume unlocking
@mrpdaemon, It is great to see an open source file encryption app that does not require rooting one's device! Thank you for your contribution!
I have a few questions, and if these are all answered by the app itself please forgive me as I don't currently have an Android device to test on (I'm going to be getting a tablet soon!):
It sounds like the way Encdroid currently works one has to move a file from it's original location into the Encdroid encrypted volume, correct?
Subsequently, the only way to open a given encrypted file is to open Encdroid and then open the file via whatever app is associated with that file type, correct?
When one opens an encrypted file (via whatever app is associated with that file type) what is the state of that file? Is it unencrypted into a temporary file someplace, and if so, is that unencrypted temp file securely overwritten when the file is closed? Or is there some other method(s) at work to protect the security of the file? (I'm not doubting you--I just want to understand how the app works. )
Do you have plans (if it is even possible without rooting one's device) to enable Encdroid to transparently handle file/folder encryption (eg, similar to the way TrueCrypt for Windows works--software just sees the files like normal inside the TrueCrypt volumn)? It sounds like DroidCrypt might being able to do this, but I'm leery of trusting myself to a closed source unknown piece of software (especially for something security related!).
Does the Dropbox integration just mean that one has the option of storing the encrypted files/containers in their device Dropbox folder?
Thanks!
Just released v2.0 with Google Drive support. Hoping that it's useful to more people now!

[ROM][CM10.1][May27] dt39 UltimateROM v2!

ROM's main highlight is that exchange server security restrictions that are enforced from your exchange server is bypassed ONLY for the lockscreen. So no more entering a password while unlocking your device! Also, you get to use lockscreen widgets, quick camera access, lockscreen targets etc. while you use your company's exchange server account!
Besides, the build has been compiled with the latest CM10.1 fixes (dozens of fixes that happen on a daily basis).
Version 2
- Latest CM10.1 sources (27th May 2013)
- Locktargets crash issues fixed
- Lockscreen with delayed locking - bug fixed (now works as expected!)
- Performance improvements/optimization
- Bluetooth stability fixes
Download Link: http://www.mediafire.com/?0whujps4hzbh4rp
Version 1
- Lockscreen exchange security disabled, always defaults to slide to unlock
- CM10.1 source as on May 14th 2013
Download Link: http://www.mediafire.com/?yyktiubn1lq4x80
-dt39
reserved.
Great !thank you
It would be great if any of you guys can let me know if this is something you find useful. I could try and embed this as a hack-switch somewhere in settings, clean it up from the root level (rather than just disable at lockscreen) and allow the other lock options in settings.
Also, please report if you find any other bugs!
i'd love just a flashable zip aosp or twiz.
Hi
Could you post just the MOD to disable Lockscreen Exchange Security, not the whole ROM, so that we can use it with any 10.1 ROM?
many Thanks
I recall sometime last year there was such a mod for the Exchange apk somewhere in the HTC forums, but I can't recall where exactly. Building a ROM just to enable this is overboard IMHO.
pasil.pt said:
Hi
Could you post just the MOD to disable Lockscreen Exchange Security, not the whole ROM, so that we can use it with any 10.1 ROM?
many Thanks
Click to expand...
Click to collapse
+1
Sent from my GT-N7100 using Tapatalk 2
I am using Revo HD 17.0, can I flash this? I need this badly!
Thanks.
Bert
Unfortunately all the hacks to fix exchange.apk and other email related apks don't completely kill exchange imposed security restrictions system-wide.
The only way to disable these restrictions for specific modules is by doing this -
1. DevicePolicyManager module in Android sources manages all the restrictions across the device. Fixing this directly would ensure perfect removal of these restrictions. The module should still exist to communicate with the exchange servers letting it know that "the device is all fine and secure". The disabling has to be done with all the interfaces exposed which other parts of Android (lockscreen, homescreen widgets, device wipe etc.) accesses. When other parts of the OS queries the DevicePolicyManager module if any restrictions exist - it should return "NO restrictions".
This would take a little longer to implement and test - and is something I will now work on and implement.
2. The second dirty approach is to fix individual modules (such as Lockscreen - like what i've currently patched right now). Only within LockScreen i'm currently overriding querying anything from the DevicePolicyManager.
Version 2 uploaded! Bug fixes, latest CM10.1 sources compiled, performance tweaks.

[ROM][7.1.2][i9305]Unofficial LineageOS 14.1 with modifications

Hi,
I am back with one of my builds. Again this is just result of my hobby, feel free to use it, but do it on your own risk. Also any updates will be probably sporadic.
I wanted to publish my build as quickly as possible, becasuse I promised in another thread. So I simply took, what I have (and I am using right now). As a result there some detail I`d like to change for public release like this for the future (e.g. all the special feature enabled by default, the big dmesg buffer). Be careful. I`ll try to do better version as soon as possible. I don`t recomend this for begginers. Be sure you have backup.
This build is based on the official LineageOS code and contains several of my changes. In some cases it could be considered as fix, improvement, but sometimes a hack or even even security risk, so please read carefully following list. All the changes I did because I wanted the system on my device behave that way (at least time to time). Take it or leave it. Please note, that all the features are enabled by default. Be careful.
- built-in root support
- RIL is based on stock KitKat version (works better for me than the official version)
- the sensors libraries are also from stock KitKat (same reason as above )
- barometer sensor is correctly recognized by the system
- the menu button does, what it always did
- notification led brightness can be configured by user
- entering safe mode by holding specific keys during boot can be disabled by setprop persist.safe_mode_disabled true (this has always only annoyed me, but be sure you know you are doing)
- device wakeup by power button can be disabled when proximity and light sensors are blocked (e.g. in a pocket). Execute setprop persist.pwrbtn_proximity_block true
- external sdcard can be made world writeable by setprop persist.world_writable_sdcard true (be careful with this one, this opens a security risk)
- the notification led can blink when the battery is fully charged - enable by setprop persist.blink_when_charged true
- F2FS support
- the notification icons are also on the lock-screen as they ware in
previous Android versions. The carrier name is moved above the clock
(this cannot be turned off)
- the dmesg buffer size is increased to 16M. I set this for debugging
and remove it in next published build.
- ramdisk LZMA compression support
- sdcardfs support - This is faster replacemnt for the FUSE filesystem. I backported this for higher kernel version. Although I`ve been using this for several months without any problem, please consider this experimental. Enable with setprop persist.sys.sdcardfs
force_on
- mount directories for sdcard are protected against writing while the sdcard is not mounted (this solves a race condition problem which allows some apps to create files in there)
- there some other small changes related to my multiboot envrionment, czech translation, carrier name, etc.
Source code
In the installation zip there is a directory code_info with following content:
roomservice.xml - roomservice.xml for the build
commits - list of git repositories and commits used for the build
patches - directory tree with structure reflecting the source and containing
patches for individual projects. The idea (not always followed) is that one patch is one feature,if possible.
code1.diff - all the patches from patches directory together
code2.diff - changes which are not in patches directory
diff-commits.txt - obsolete, I`ll remove this one in the future or maybe use
it again
The only bug I know about is occasional crash of MTP, but I didn`t notice any negative consequences. There may some problem with battery charging (the display turns on time to time without no obvious reason during charging), but it may be some hardware error (bad cable or charger).
Since this is based on official LineageOS, thanks to everyone who contributed to it.
I am using this build for over a week without any problem, except those mentioned above.
Continue here, for the latest build.
UPDATE:
I totally forget about this yesterday - here are the proprietary files I used for this build proprietary-files-ocm13-skk-ril.tgz It is a mixture from the CM 13 official build and KitKat stock files, with modified ks file (then connect symbol is replaced with xonnect, so it doesn`t crash), maybe some other files and changes. I really don`t remember, I put this together during a long period of time. If you find any of your work inside, please accept my apologies and let me know. From my point of view it just works. If you want to apply the patches, then you will most probably want to change the hardcoded full path to these files in device/samsung/i9305/extract-files.sh.
UPDATE:
If you want to use anything from my patches, feel free to do so, just follow the license of the original project.
I tested it for about 4 hours for modem stability, taking the logs. All SAHARA transfers were ok, with no errors and retries. I should have mentioned your name in some post earlier
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
rodman01 said:
gongrats and many thanks @p.a.n. Your rom runs very well, its awesome. :good:
Do you mind, if I take your sources or parts of it or some files from your rom.zip for my builds? If I do so, I will mention you and what I took and give you credits.
Click to expand...
Click to collapse
Thanks Use whatever you want from it just follow the license of the original project (I updated OP with similar note).
Help??? How to fix gps on this Rom plzz
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
One other thing, the MTP crash is the 'MTP host' app. I just disable this as it's only needed if you need your phone to be an MTP host for something like a digital camera, which I don't. It doesn't affect connections to your PC.
Is there an issue with the automatic execution of init.d scripts? I'm on Boeffla so it may just be that. Luckily you can tell Boeffla app to execute them anyway.
@Glenn2, thanks for testing I am not completely sure about it, but if I remember well, the compass problem is caused by the opensource sensor library (I think that just replacing the/system/lib/hw/sensors.smdk4x12.so with the one from my build should fix that). But the problem is not actually with the compass sensor, that one is ok, but in the opensource version there are missing some "fake" sensors, which provide calculated data based other "real" sensors. One of them provides orientation information, often used in apps as compass. Try some app (e.g. Androsens2) which lists all the sensors and you`ll see the difference - the "fake" ones have iNemo in their name.
I actually don`t care about the MTP crashes. It mostly happens after uninstalling some app, which doesn`t happen too often and otherwise I haven`t noticed any negative related to that. It is just annoying popup for me.
What do you mean by the question about init.d scripts?
p.a.n said:
What do you mean by the question about init.d scripts?
Click to expand...
Click to collapse
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it. I had this happen a couple of times on official LineageOS too. Not the famous mdm_hsic_pm0 which now seems to be cured at long last! I had a period of no signal when I was on the London Underground, maybe that was the cause.
Glenn2 said:
I have a couple of scripts and they were not running on boot. I don't know if Boeffla kernel affects busybox. I remedied this by telling the Boeffla Config app to run init.d scripts when it launches.
Click to expand...
Click to collapse
There is /system/etc/init.d/* scripts, which run OK, or at least /system/etc/init.d/00banner does. There is also /system/etc/init.d/90userinit, which executes /data/local/userinit.sh. I remember that seme previous CM version there was also a user defined init.d somewhere in /data. This may what has changed, but I am not if this is your case.
Glenn2 said:
Also, I had a power manager service wakelock that kept my phone awake for hours, only a reboot cleared it.
Click to expand...
Click to collapse
This on is also often on the top of my kernel wakelock list, but never that bad, always with reasonable times.
Glenn2 said:
Not the famous mdm_hsic_pm0 which now seems to be cured at long last!
Click to expand...
Click to collapse
Yes, the solution has been sitting in the Samsung kernel source for a long time ...
Glenn2 said:
Great work p.a.n.
Using for 24 hours no problems yet and seems very smooth.
Used it for a few hours with the built-in kernel then switched to Boeffla to get Boeffla Sound etc.
Very nice to have the customisable LED again as it was missing from the official LineageOS.
More importantly for me, the magnetic compass seems to work properly. I couldn't get it to work on official, nor on Rodman's RR.
No issues with GPS for me.
I had to install 'The SELinux Toggler' to set permissive so I could get Viper4Android to work (as with official) but I expected that.
Click to expand...
Click to collapse
Do you install the last rom ??? Or not
It is worth pointing out that after backing and restoring between roms, the SELinux attributes for efs files can become not correct. That can lead to something like this :
Code:
06-28 04:17:43.705 3799 3799 W ks : type=1400 audit(0.0:30): avc: denied { read } for name="efs1.bin" dev=mmcblk0p11 ino=8200 scontext=u:r:qcks:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
Code:
06-28 04:17:43.712 3799 3799 E kickstart: Requested ID 16, file "/tombstones/qcks/efs1.bin"
06-28 04:17:43.712 3799 3799 E kickstart: ERROR: function: open_file:80 Unable to open input file /tombstones/qcks/efs1.bin. Error 13: Permission denied
It results in not working RIL because of enforced SELinux. Running restorecon fixes the problem.
moad gastro said:
Do you install the last rom ??? Or not
Click to expand...
Click to collapse
I don't know what your question means, as there is only one ROM. I installed from the link in the OP (dated the same date as the OP).
Still using this ROM, and still very few problems.
The day before yesterday it crashed with the screen off. Had to hold power button in to restart.
And yesterday the damn wakelock. It got stuck at a time when I had no signal, and also I used the camera, so either may be relevant. It didn't seem to cause any drastic battery drain though (see images attached). I suppose when the CPU is awake but only at 200MHz and not doing much it uses little more than when it is sleeping?
Regarding init.d scripts. I added one to /system/etc/init.d that simply writes a file to /data when it runs, to test that it DID run. Script starts #!/system/bin/sh
Results:
1) rom with its own kernel - didn't run
2) rom with Boeffla kernel - didn't run
3) rom with Boeffla kernel and Boeffla Config app set to execute init.d scripts itself - did run
One more, just for fun!
Two days ago I was at the Wimbledon tennis, and the location service and/or weather widget decided I was in Boulogne-Billancourt (Paris) instead! I then opened and closed Maps, refreshed the widget and it changed to the correct location!
..
Hi,
I'm trying to install the current build using TWRP 3.0.2-1, but it gets stuck at the "Patching system image unconditionally..." step with the progressbar at around 40%. It's been sitting there for about 10 minutes. Does anyone know how that'd be fixable?`
Cheers
Latest build is ok for me. I've flashed it using TWRP 3.1.0 build from rgib
https://drive.google.com/drive/folders/0B7pwslEEF0l4Yzk2Nm1jOGRDQVU

Categories

Resources