{
"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"
}
[Topic]
I occasionally built RootBox for i9100 myself to include pdroid support.
As i was asked if i could provide a download for them i started this thread.
So far I only sync the official repo, patch the pdroid files from https://github.com/OpenPDroid/ and built the ROM.
For information about the official ROM or the pdroid project see the referenced topics below.
[Files]
I don't provide any sort of warranty, but i use(d) these ROMs myself and would not upload them if i had problems with them.
http://msdigital.de/files/RootBox/
(As i do it myself every new Download - i would recommend to check the file's md5 checksum on your device)
Code:
Changelog
"RootBox-JB-i9100-Unofficial-n00b42-pdroid-20130705"
* No changes (to official) besides pdroid patch
* Tested for two days w/o issues
** If problems with "android.process.acore" then backup your contacts and clear contact storage data
"RootBox-JB-i9100-Unofficial-n00b42-pdroid-20130612"
* No changes (to official) besides pdroid patch
* Testing it right now
[Credits]
All credits go to bajee11 for his awesome ROM and FFU5y and all others who work on OpenPdroid
[Future]
*I'm new to building, so if there are problems originating from me building the ROM contact me.
*Perhaps i will remove some apps or media files i never used, but will point it out if i do so
[References]
RootBox: http://forum.xda-developers.com/showthread.php?t=1806401
OpenPdroid: http://forum.xda-developers.com/showthread.php?t=2098156
n00b
Screenshots ?
Changelogs ?
MPooZD said:
Screenshots ?
Changelogs ?
Click to expand...
Click to collapse
I didn't change anything of the original RootBox ROM besides applying the OpenPdroid patches.
For media / changelogs please look at the referenced official RootBox and OpenPdroid topics.
Regards
n00b
n00b42 said:
I didn't change anything of the original RootBox ROM besides applying the OpenPdroid patches.
For media / changelogs please look at the referenced official RootBox and OpenPdroid topics.
Regards
n00b
Click to expand...
Click to collapse
Thx n00b,
But could you plz build another release over RB stable V4.0?
spreadtux said:
Thx n00b,
But could you plz build another release over RB stable V4.0?
Click to expand...
Click to collapse
I would like to do so, but currently i dont have a clue how to do it, as i only know how to build the lastest commited version and don't know how to "get back" to 4.0.
I already asked some guys and am currently waiting for a response if someone could help me with it.
If i manage to build it somehow, or if the RIL issue in the current nightlies is fixed, i will build it and post it here.
n00b42 said:
I would like to do so, but currently i dont have a clue how to do it, as i only know how to build the lastest commited version and don't know how to "get back" to 4.0.
I already asked some guys and am currently waiting for a response if someone could help me with it.
If i manage to build it somehow, or if the RIL issue in the current nightlies is fixed, i will build it and post it here.
Click to expand...
Click to collapse
I searched on github too but didn't find how to obtain previous version.
github is definetely not a real git or svn repos
Best solution is to ask bajee to give you a link to his v4.0 sources if possible.
Thx to keep us informed.
Whats the difference of this ROM and RootBox with patching OpenPDroid afterwards?
Just curious would love to give v4 a try.
also bump
Greetz
SlimBean-b6|KangBang-v1.1|i9100¬Tapa2
OpenPDroid is a set of modifications to the Android framework and libraries which allows fine-tuning of the data which applications are able to retrieve about your device, your account, your messages, and more. Specifically, it is a Privacy service provider (using the PDroid 1.51 interface) forked from CollegeDev's PDroid 2.0, which is itself an extension of Syvat's PDroid.
Hey,
sorry for confusion - i know what pdroid is/does, just wanted to know whats the difference of thos rom to straight rootbox with pdroid patches (which are flashed after rom flash - generated with autopatcher)
Greetz
SlimBean-b6|KangBang-v1.1|i9100¬Tapa2
leechseed said:
Hey,
sorry for confusion - i know what pdroid is/does, just wanted to know whats the difference of thos rom to straight rootbox with pdroid patches (which are flashed after rom flash - generated with autopatcher)
Greetz
SlimBean-b6|KangBang-v1.1|i9100¬Tapa2
Click to expand...
Click to collapse
Thx Leech,
I completely forgot autopatcher.
I did give it a try but was unsuccessfull to patch RB v4.0 with openpdroid.
Autopatcher fails and gives me this error :
Exception in thread "main" brut.androlib.AndrolibException: Multiple resources: spec=0x010800ce drawable/background_holo_dark, config=-nodpi
at brut.androlib.res.data.ResConfig.addResource(ResConfig.java:65)
at brut.androlib.res.data.ResConfig.addResource(ResConfig.java:58)
at brut.androlib.res.decoder.ARSCDecoder.readEntry(ARSCDecoder.java:201)
at brut.androlib.res.decoder.ARSCDecoder.readConfig(ARSCDecoder.java:170)
at brut.androlib.res.decoder.ARSCDecoder.readType(ARSCDecoder.java:135)
at brut.androlib.res.decoder.ARSCDecoder.readPackage(ARSCDecoder.java:110)
at brut.androlib.res.decoder.ARSCDecoder.readTable(ARSCDecoder.java:83)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:49)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:40)
at brut.androlib.res.AndrolibResources.installFramework(AndrolibResources.java:562)
at brut.androlib.Androlib.installFramework(Androlib.java:473)
at brut.apktool.Main.cmdInstallFramework(Main.java:250)
at brut.apktool.Main.main(Main.java:81)
... decompile Mms.apk ...
### copy patch openpdroid/4.2/aosp/20130213 ###
... copying system/media/PDroid.jpeg ...
... overwriting system/media/PDroid.jpeg from openpdroid ...
### jar patch openpdroid/4.2/aosp/20130213 ###
... apply framework.patch ...
Reversed (or previously applied) patch detected! Skipping patch.
16 out of 16 hunks ignored -- saving rejects to file smali/android/app/BackStackRecord.smali.rej
The next patch would create the file 'smali/android/app/ContextImpl$41.smali',
which already exists! Skipping patch.
1 out of 1 hunk ignored
5 out of 5 hunks FAILED -- saving rejects to file smali/android/app/Fragment.smali.rej
2 out of 2 hunks FAILED -- saving rejects to file smali/android/content/AsyncTaskLoader.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file smali/android/content/ContentProviderOperation.smali.rej
9 out of 9 hunks FAILED -- saving rejects to file smali/android/content/ContentResolver.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file smali/android/content/CursorLoader.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file smali/android/content/pm/VerificationParams.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file smali/android/net/wifi/WifiStateMachine.smali.rej
1 out of 6 hunks FAILED -- saving rejects to file smali/android/os/SystemProperties.smali.rej
1 out of 9 hunks FAILED -- saving rejects to file 'smali/android/provider/Settings$Secure.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
6 out of 6 hunks ignored -- saving rejects to file 'smali/android/service/wallpaper/WallpaperService$Engine.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file 'smali/com/android/internal/os/BatteryStatsImpl$StopwatchTimer.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file 'smali/com/android/internal/os/BatteryStatsImpl$Timer.smali.rej'
... apply preloaded.patch ...
!!! PATCHING FAILED FOR android/app/Fragment.smali android/content/AsyncTaskLoader.smali android/content/ContentResolver.smali android/os/SystemProperties.smali android/provider/Settings$Secure.smali' !!!
File for which patching failed:
---------------------------------------------
Fragment.smali
Click to expand...
Click to collapse
I'll have to move to autopatcher thread.
Stay tuned!
UPDATE :
What mateorod says about RootBox and autopatcher/openpdroid :
I do not know much about ROOTBOX or Xenon, but for now there are no plans to expand the supported rom list with the current patching technique. Once the next update of OpenPDroid goes out, I have somewaht large plans for the patching process which I hope will allow support to be much, much wider. But for now we support straight AOSP, AOKP, PACman, PA, CM, SlimRom and EverVolv in addition to whatever else people have found to work (some, but not all kangs of the above list). Somewhere in there we should have support for multiple roms for most devices...if you need another rom because of some killer feature than you will have to choose that feature over Pdroid, for the moment.
As for that Rootbox logs, whatever they have going on with the Mms.apk is breaking the decompile with apktool, so they likely have something there that is incompatible with the patching process as it no matter the rom type.
Click to expand...
Click to collapse
So we should wait for next openpdroid release or another solution could be to remove the breaking mms.apk from ZIP before patching.
I'll try this tomorrow.
CHEERS
Just followed a link to this thread from RB i9100 Support thread.
I'm actually on i9505 but my i9100 kept on RB v4.0 built from sources.
I only wanted you to know that my repo is still synced with 4.0 sources. I did the last sync just a couple of hours after Bajee released RB v4.0
However I don't know how to patch those Pdroid files. Feel free to contact me if you want me to do something.
GT-I9505 -- Omega v3.1 -- CWM 6.0.3.2.2 -- Sent from Tapatalk
descarao81 said:
Just followed a link to this thread from RB i9100 Support thread.
I'm actually on i9505 but my i9100 kept on RB v4.0 built from sources.
I only wanted you to know that my repo is still synced with 4.0 sources. I did the last sync just a couple of hours after Bajee released RB v4.0
However I don't know how to patch those Pdroid files. Feel free to contact me if you want me to do something.
GT-I9505 -- Omega v3.1 -- CWM 6.0.3.2.2 -- Sent from Tapatalk
Click to expand...
Click to collapse
You guys are doing a fanstastic job! Now if we can just patch the latest 6/11 nightly with HALO that would be incredible! I tried patching with AutoPatcher but it failed. Best to patch while building which I don't know how to do. Cheers.
descarao81 said:
Just followed a link to this thread from RB i9100 Support thread.
I'm actually on i9505 but my i9100 kept on RB v4.0 built from sources.
I only wanted you to know that my repo is still synced with 4.0 sources. I did the last sync just a couple of hours after Bajee released RB v4.0
However I don't know how to patch those Pdroid files. Feel free to contact me if you want me to do something.
GT-I9505 -- Omega v3.1 -- CWM 6.0.3.2.2 -- Sent from Tapatalk
Click to expand...
Click to collapse
thx for the offer. but as the nightlies seem to work again for i9100, i will use the latest code again.
Building it right now. Will upload today.
Just built latest nightly which includes HALO.
RootBox-JB-i9100-Unofficial-n00b42-pdroid-20130611
Testing it right now, so far no issues. Already uploaded it.
So let me get it right....will mm.apk conflict with pdroid?...or is it only when using autopatcher?
Not finished uploading N00b?
RootBOX latest
DorimanX latest
Link to DorimanX Discussion Thread
Sry, my server quota was exceeded but FTP didnt throw any errors, deleted all files but the newest one, will upload them on another server soon.
Dont know if theres problems with mms.apk,
sms etc works fine, never sent/get mms myself.
pSyCh¤_O_O said:
So let me get it right....will mm.apk conflict with pdroid?...or is it only when using autopatcher?
Not finished uploading N00b?
RootBOX latest
DorimanX latest
Link to DorimanX Discussion Thread
Click to expand...
Click to collapse
n00b42 said:
Sry, my server quota was exceeded but FTP didnt throw any errors, deleted all files but the newest one, will upload them on another server soon.
Dont know if theres problems with mms.apk,
sms etc works fine, never sent/get mms myself.
Click to expand...
Click to collapse
Hi Noob.
I just downloaded and flashed your build. It's rebooting rigtt now.
If problems with your FTP server, I'll make your build availaible on my Mega repos soon (See link in my sig)
MMS.apk problem is only when trying to autopatch RB. I tried to remove mms.apk from ROM.zip before autopatching but still unsuccessfull. Problem is fagment.smali or framework.jar related.
So atm auto-patcher + RootBox + openpdroid are not fully compatible.
spreadtux said:
Hi Noob.
I just downloaded and flashed your build. It's rebooting rigtt now.
If problems with your FTP server, I'll make your build availaible on my Mega repos soon (See link in my sig)
[..]
Click to expand...
Click to collapse
Thanks for the offer, but i have another server i can use with much more space than the current one, but no access from here, so will do that later.
n00b42 said:
Thanks for the offer, but i have another server i can use with much more space than the current one, but no access from here, so will do that later.
Click to expand...
Click to collapse
No problem ma8.
I'm uploading your build on my MEGA Mirror anyway.
[UPDATE]
Just found one issue :
When Wifi is activated and connected, Mobile network is disconnected
Can someone else confirm this or is it just me?
If someone is interested, V6supercharger patches for RB v4.0, 11-06 nightly and 11-06-pdroid buidsl are available in [Mods] folder too
Just built and uploaded todays nightly which includes some bugfixes according to bajee11.
RootBox-JB-i9100-Unofficial-n00b42-pdroid-20130612
Testing it right now, so far no issues found.
Related
{
"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"
}
Redirect several internal SD card locations to the external SD card.
This *only* works if the app uses Environment.getExternalStoragePublicDirectory(String), directly or indirectly, to get the location for the download. At present, it won't redirect app data (stuff in /data/data or /sdcard/Android), I may look into that later.
Apps this works with so far:
* /sdcard/Downloads - Chrome, Firefox (@an0n981, @zouhaier1).
* /sdcard/DCIM - Stock JB 4.2 Camera app.
* /sdcard/Pictures - Screenshot (@JamMasterClay).
[size=+3]Requirements[/size]
* [FRAMEWORK ONLY!] Xposed - ROM modding without modifying APKs
[size=+3]Screenshots[/size]
[size=+3]Caveats[/size]
* Due to weird security measures that make no sense, this won't always work on KitKat.
[size=+3]Downloads[/size]
* Source: https://github.com/egingell/Downloads2SD
[size=+2]Version name: 1.0.8[/size]
Download: com.egingell.downloads2sd_v9_acf08f.apk (267.61 KB)
MD5 checksum: acf08f0476e9d1df8997feee1cd12c32
Changes: Using logcat instead of Xposed to log info (logcat | grep "Downloads2SD").
[size=+2]Version name: 1.0.7[/size]
Download: com.egingell.downloads2sd_v8_dcd0c1.apk (267.42 KB)
MD5 checksum: dcd0c152bc1fbf66e14bf3c2422d101e
Changes: Per @rovo89 and @GermainZ in the Xposed Framework thread, I have switched my hook up slightly. It is unlikely that you, the user, will notice a difference.
[size=+2]Version name: 1.0.2[/size]
Download: com.egingell.downloads2sd_v3_77e3e4.apk (264.94 KB)
MD5 checksum: 77e3e49aa80c9ffe968b18141fb19b61
Changes: Added a check to ensure the new destination is viable (e.g. not an unmounted/removed SD card).
[size=+2]Version name: 1.0.1[/size]
Download: com.egingell.downloads2sd_v2_63f388.apk (264.71 KB)
MD5 checksum: 63f3887beb333dd2ea6dff4a4577dd87
Changes: Graphical bug. Reboots may or may not be required for changes, but it never hurts to just reboot anyway.
[size=+2]Version name: 1.0[/size]
Download: com.egingell.downloads2sd_v1_803aac.apk (264.74 KB)
MD5 checksum: 803aac515c56cecc9fc6a39177f1e167
Changes: Initial commit.
Confirmed working with Firefox on Omni 4.4.2
Oy. Seems there's a weird bug on my GS4. Works flawlessly on my GS2.
The bug: Repeated listings on the app UI which are confusing to the mod making it not redirect as it should.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Confirmed working with firefox on SM N9005 running x-note 10.0 leonardo edition. Thnx
sent from my rooted SM-N9005 running x-note 10.0 Leonardo Edition
Just want to report that everything seems to be work here on 4.4.2. So far I tested taking a picture with stock camera and taking a screenshot with the native Android function.
Thanks! :good:
It does not work with downloading a picture in an MMS in Verizon Messages. No surprise there...I absolutely despise that app. Unfortunately since KitKat there's no way to have my messages sync between devices and use a different SMS client. Using the Verizon sync service works better than any 3rd party solution because messages go to Verizon before coming to the phone anyways so often times I'll get a message on my tablet before my phone. 3rd party solutions have to read the SMS database, monitor it for changes, and then forward messages to a separate server. Luckily I hardly ever text people anymore anyways, but I digress.
/rant
JamMasterClay said:
It does not work with downloading a picture in an MMS in Verizon Messages. No surprise there...I absolutely despise that app. Unfortunately since KitKat there's no way to have my messages sync between devices and use a different SMS client. Using the Verizon sync service works better than any 3rd party solution because messages go to Verizon before coming to the phone anyways so often times I'll get a message on my tablet before my phone. 3rd party solutions have to read the SMS database, monitor it for changes, and then forward messages to a separate server. Luckily I hardly ever text people anymore anyways, but I digress.
/rant
Click to expand...
Click to collapse
Does the Xposed log show "DOWNLOADS_PICTURES [OLD] => [NEW]", "DOWNLOADS_PICTURES [OLD] => null", or nothing?
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
egingell said:
Does the Xposed log show "DOWNLOADS_PICTURES [OLD] => [NEW]", "DOWNLOADS_PICTURES [OLD] => null", or nothing?
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Click to expand...
Click to collapse
Not a thing, sir.
Bummer.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
I hope that can be connected to a Bluetooth folder on the external SD card on the next update.
JazzBlueWong said:
I hope that can be connected to a Bluetooth folder on the external SD card on the next update.
Click to expand...
Click to collapse
Eventually. I just need to figure out where Android gets the arbitrary folder name from. Hint: It's not the same place as the ones in this mod.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
@egingell
When I tap 'Direct Download' here: http://forum.xda-developers.com/devdb/project/dl/?id=4318 using Chrome Beta the browser force closes. I've attached a screenshot of the stack trace occurring with no other modules enabled. I did the same test on both my Note 10.1 and S4 both running OmniROM 4.4.2 with the same behavior on both. Downloading other things works fine, for example long-pressing to download a image.
-Sent from My Galaxy Note 10.1 using Tapatalk
JamMasterClay said:
@egingell
When I tap 'Direct Download' here: http://forum.xda-developers.com/devdb/project/dl/?id=4318 using Chrome Beta the browser force closes. I've attached a screenshot of the stack trace occurring with no other modules enabled. I did the same test on both my Note 10.1 and S4 both running OmniROM 4.4.2 with the same behavior on both. Downloading other things works fine, for example long-pressing to download a image.
-Sent from My Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
Works fine for me, but I'm not using Kit Kat. Even when testing and making other apps crash, I still got my file names and Xposed file names with line numbers in the logcat, so I can't even trap the exception let alone fix it since neither are present in that error log.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
egingell said:
Works fine for me, but I'm not using Kit Kat. Even when testing and making other apps crash, I still got my file names and Xposed file names with line numbers in the logcat, so I can't even trap the exception let alone fix it since neither are present in that error log.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Click to expand...
Click to collapse
I hoped it wouldn't be so involved to track down. Xposed log and logcat attached.
EDIT: It's late...forgot to mention Chrome Beta version 33.0.1750.126.
JamMasterClay said:
I hoped it wouldn't be so involved to track down. Xposed log and logcat attached.
EDIT: It's late...forgot to mention Chrome Beta version 33.0.1750.126.
Click to expand...
Click to collapse
I'm afraid I still don't see a viable error message, but I will give it a better look in the morning... and I successfully downloaded the file using Chrome Beta.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
JamMasterClay said:
@egingell
When I tap 'Direct Download' here: http://forum.xda-developers.com/devdb/project/dl/?id=4318 using Chrome Beta the browser force closes. I've attached a screenshot of the stack trace occurring with no other modules enabled. I did the same test on both my Note 10.1 and S4 both running OmniROM 4.4.2 with the same behavior on both. Downloading other things works fine, for example long-pressing to download a image.
Click to expand...
Click to collapse
JamMasterClay said:
I hoped it wouldn't be so involved to track down. Xposed log and logcat attached.
EDIT: It's late...forgot to mention Chrome Beta version 33.0.1750.126.
Click to expand...
Click to collapse
I managed to get Chrome Beta to crash on my GS2, but for a different reason which I fixed and added an untested fix fr your problem. If you'd like to test it:
[size=+1]Version name: 1.0.3[/size]
Branch: beta
Download: com.egingell.downloads2sd_v4_eb5301.apk (265.48 KB)
MD5 checksum: eb5301465e38f0f7df46b2f24d0dec2c
Changes: Removing Security exception ensuring that the file goes to the "external" storage.
egingell said:
I managed to get Chrome Beta to crash on my GS2, but for a different reason which I fixed and added an untested fix fr your problem. If you'd like to test it:
[size=+1]Version name: 1.0.3[/size]
Branch: beta
Download: com.egingell.downloads2sd_v4_eb5301.apk (265.48 KB)
MD5 checksum: eb5301465e38f0f7df46b2f24d0dec2c
Changes: Removing Security exception ensuring that the file goes to the "external" storage.
Click to expand...
Click to collapse
Well, I'm no longer getting a FC. But the download consistently fails before actually starting (i.e. it never gets to showing the download percentage) I've tried multiple times on WiFi (literally sitting next to the router) and on 4G LTE. With the module enabled download fails, without it succeeds. FWIW, in the downloads app where the filename should be is black, and it says unsuccessful below that.
If you feel like continuing to look into this I've attached a new Xposed log and logcat.
JamMasterClay said:
Well, I'm no longer getting a FC. But the download consistently fails before actually starting (i.e. it never gets to showing the download percentage) I've tried multiple times on WiFi (literally sitting next to the router) and on 4G LTE. With the module enabled download fails, without it succeeds. FWIW, in the downloads app where the filename should be is black, and it says unsuccessful below that.
If you feel like continuing to look into this I've attached a new Xposed log and logcat.
Click to expand...
Click to collapse
I had a feeling it would do that. I'm bypassing that particular exception, but whatever is triggering it is still there. Does Chrome Stable have the same problem? Doesn't much matter, though. I don't think I can do anything about it.
Is purposely thrown and it doesn't make much sense why, but I digress.
Edit: Those error messages are even less useful.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
egingell said:
I had a feeling it would do that. I'm bypassing that particular exception, but whatever is triggering it is still there. Does Chrome Stable have the same problem? Doesn't much matter, though. I don't think I can do anything about it.
Is purposely thrown and it doesn't make much sense why, but I digress.
Edit: Those error messages are even less useful.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Click to expand...
Click to collapse
Yup, same behavior with the non-beta version of Chrome.
Just wanted to post that I'm having that same error when trying to download files from Goo.im, Android File Host, and Dev-Host as well. For now I simply changed the Downloads location back to the built-in storage location and everything's working fine. Not a big deal to me, but I just wanted to give you a heads up in case a lot more people on KitKat start using this.
This is a Windows Batch Script/Tool to make any 4.4 based ROM to full F2FS compatibility !! This tool can convert any existing ROM from ext4 to Full F2FS Compatibility in a few clicks !! All tools necessary for conversion included in the batch file itself !!
Basic Info
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
DISCLAIMER
Code:
*I am Not responsible for any bricked devices,SD cards or thermonuclear attacks.
*Please do some research about what you are doing before you use the tool.
*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. Hard. A lot.
Current Device Compatibility
Code:
1. Nexus 4 ( Mako )
2. Nexus 7 2012 Edition ( Grouper)
3.Nexus 5 (HammerHead)
Prerequisites
Code:
1. A Hammerhead
2. Any 4.4 based ROM with [B][U]busybox [/U][/B]installed
3. Proper F2FS Compatible Recovery and Partition Zip from
[url]http://forum.xda-developers.com/google-nexus-5/orig-development/recovery-twrp-2-7-0-0-f2fs-support-t2746030[/url]
4. Any Windows version and my batch script
Features
Code:
1. One Click F2FS Conversion Process
2. All tools included in the Zip file itself
3. Changes only the relevant parts of your updater-script keeping the rest unmodified
4. Compatible boot.img included in the ROM itself
5. Now Scripts are Device Specific
6. Error conditions at many places so a noob cant go wrong
***Special note for CM /CM based ROM users***
Code:
I dont test the script since I dont own an HH !! This is the CM kernel by @kdh2834
If it does not work kindly post the detailed error on the thread . Will try my best to resolve it
***Special note for Stock ROM users***
Code:
The script requires busybox and since stock roms dont have busybox the repacked ROM wont boot up.
In such a case the best option is try out any other AOSP based ROM/or a Stock ROM with busdybox installed
Instructions
Code:
[LIST=1]
[*] Unpack the Zip file you downloaded from Link Below to a folder named F2FSROMConvetor (Dont Mess with the name).
[*] Take Care that the path you extract my Zip for eg in my case "C:\Users\Nabendu\Desktop\F2FSROMConvetor"
does not contain any blank spaces in between or else the script will not work as intended.
[*] Run F2FS Convertor.bat
[*] Select your device
[*] Place the Zip in the Extract /Input directory when prompted
[*] The script will Unpack your ROM
[*] Select option of boot.img based on your rom
[*] Repack your ROM
[*] A black window will open showing the Repacking progress. Dont close my Blue Window anytime during it the repacking process.
After 100% repacking is done the Black Window will close automatically and you can now press any key to Continue
[*] Check NEW F2FS ROM directory for the Repacked ROM
[*] Flash and Enjoy
[*] Cleanup the working directory cleanup.bat (Cleans everything including original input ROM.Only a copy of the Output ROM is maintained)
[/LIST]
***FAQ's***
Q. I get errors compiling the ROM on my XYZ Windows Version?
A. Read through my steps once again especially point 1 & 2. Hopefully u can get it to work.
If you think you are doing everything correctly post it on the thread and Ill try to reply within 24Hrs.
Q. I want to do it on Linux !! Why you no create bash scripts ?
A. Im not good at bash scripting !! Also dont own a Linux Distro so cant help you guys !! But look here @jolinnard has a script for Linux users
https://github.com/figue/f2fs-scripts/blob/master/convert_ROM_to_f2fs.sh and make necessary changes for Hammerhead updater script if any
Q. I can do the same with the Convert to F2FS apk on the Playstore ?
A. Sure you can. Converting on mobile is easier also. But only reservation is that it is paid.Not everyone can afford it.
Also time permitting Ill create a Android Terminal Script based on jolinnards script for Linux.
Q. Do you think I can convert it myself ?
A. Yes its just clicks . Read my steps and do it you wont go wrong.
Download Links
1. V1.1 OLD
2.V1.2 NEW
Changelog
Code:
V1.0 Intial Release
V1.1 : Add Device Support
1) Added Device Compatibility : Nexus 5
2) Scripts now will come seperate for each device.
3) Did some cleaning up on my messy script
V1.1 : Add more Boot.imgs for N5
Credits
Code:
@legolas93 For bringing F2FS to Nexus and also for providing the boot.img for the script
[user=4439521]@mikaole[/user] For the German Translations and extensive testing
[user=2002216]@jolinnard[/user] For the amazing F2FS kernels he is providing
[user=4544860]@osm0sis[/user] For his amazing Android Image Kitchen.The cleanup.bat script is taken from his tool.
[user=3325155]@fishears[/user] For helping out on the kernel side.
[user=5501864]@USBhost[/user] For being the lone tester for the N7 ( 2012 )
[user=4450732]@CallMeAldy[/user] For the CM trick and his compilation thread
[user=4851200]@Rohit02[/user] For being the beta tester
[user=14325584]@kdh2834[/user] For his AOSP Kernel
And all other beta testers !! Sorry if I forgot anyone from the list !!
Screenshots in the Next Post
Hit the Thanks button if you Like My Work
Screenies
Screenies atlast
{
"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"
}
Excellent test on
Big thanks
c-rom v6.4 Network Connectivity fail
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
I dont own a HH so not much I can help you with !! But try flashing a different kernel on top of it , think it should work !! And does c rom used the aosp kernel in the first place !! Look at the thread for modified Kernels , i guess flashing one should solve your problem !!
belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img (AOSP) that NABENDU1 provide inside his tool will not work with your rom.
c-rom is aosp based.
micr0g said:
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img that NABENDU1 provide inside his tool (AOSP) will not work with your rom.
Click to expand...
Click to collapse
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
belictony said:
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
Click to expand...
Click to collapse
Okay you have the com.androidprocess phone fc problem right !! If its only that Ill patch the kernel myself and get you a new one in a few mins and rest assured it will work for sure !!
rabbo3 said:
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
Click to expand...
Click to collapse
Yup what kind of Rom u use !! If it has differential update like Mokee OS or xdelta ( I dont know xdelta/opendelta in detail ) like Omni I can create some kind of allied script for it too !! Put the same question in the N7 2012/N4 but dint get any responses for it mosly due to devs still use the traditional way !! Anyways if anyone wants patching for those im up for the task !!
EDIT: Version 1.2 for HH online ( Bigger Size due to 4 boot.imgs included in the script itself)
Dl Link : https://mega.co.nz/#!dxcVmQRS!5zv6RCqJs82rv5-aW3GqICW5YgCPuZtUhiH0F1vpVP8
Changelog:
Added CM boot.img ( Untested by me ) thx to @kdh2834
Added Purity boot.img ( Untested by me) thx to @kdh2834
Added AOSP com.android process phone fc boot.img ( Untested by me) thx to @me
Kindly post feedback on the thread !!
I will fix the screenies sometime later or tomm
I've used this tool to successfully switch over to f2fs-all with crDroid (a CM based rom). My biggest problem, however, is that I am completely unable to flash elementalx afterward because it freezes on boot. Anybody found a way to fix this?
Edit, I'm an idiot. I found out I have to manually mount /system before flashing ElementalX
fantastic job, works great with cm11-m6,very faster
Great!
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
tavocabe said:
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
Click to expand...
Click to collapse
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
NABENDU1 said:
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
Click to expand...
Click to collapse
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
callidus_ex_de_latebros said:
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
Click to expand...
Click to collapse
Moto G is infact already has /data partition in F2FS file format !! The only thing is making the cache and system full f2fs !! For this firstly your kernel dev should take a initiative to create a fully compatible f2fs kernel and also a f2fs recovery !! Once that is done I would be more than glad to help you guys out !! Anyways till then enjoy f2fs on /data !!
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
Works fine on my crDroid setup. Did it work for you before with Euroskank? Have you tried toggling from MTP to PTP and back? If you have a secure screen lock in place, are you ensuring that you have unlocked the phone after plugging it in? Are you waiting to plug the phone in until after it's booted up? Just trying to rule out the obvious troubleshooting steps
Sent from my Nexus 5 using Tapatalk
work in 4.4.3?
Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
It works for me using omni-elementalx.
danielalonso said:
work in 4.4.3?
Click to expand...
Click to collapse
Yes
To @NABENDU1
Hi, so far everything is good, only complain is that most of the times when I reboot to recovery and flash any update to rom/kernel or when I add a new rom using multirom (tested and working good with omni, slim and paranoid), when finished and reboot the phone I see the boot screen many times. Like a bootloop but eventually it makes it to the rom or the multirom menu to select a rom. Is this because of my configuration of f2fs with multirom or maybe the kernel I use (elementalx shared with all the roms)?
@NABENDU1 thank you very much for this, it's quick and easy as well as educational (to me)
{
"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"
}
***Disclaimer***I am not responsible if you break your stuff. Use at own risk!
I am not a developer and do not pretend to be one. I'm an Android enthusiast.
Why no Aroma?
Because I've made this ROM to my liking for myself, removing apps I'd never use. I have no need for a customized installer. I'm sharing this with you all because I'm sure there's somebody else who wants a simple, optimized ROM with the basic, stable features. If you want more options or customizations, this ROM isn't for you.
No complaints
I do this in my spare time.
Special requests
I'll accept special requests, but that doesn't mean they'll come true.
Bug Reports
Bug reports are welcome! Keep in mind: This is mostly stock and most bugs will be official firmware bugs.
Updates will come along when I have time and when I see something I'd like changed :good:
ROM: Terok Nor
Based on UEU2CNE2 US Official Firmware
DeKnoxed system and kernel
Deodexed
build.prop improvements
Slimmed down
Busybox
AOSP 4.4 KitKat system sounds
Added AOSP 4.4 ringtones, alarms, notifications, and UI sounds
Removed power on sound
Custom, smaller S Pen pointer
Scrolling Wallpaper enabled in SecLauncher3.apk (TouchWiz Launcher)
Android L Keyboard
Galaxy S5 Boot Animation
SELinux: Permissive
Special Feature: @civato SphereKat blazing fast kernel with S Pen fix! For more info on his kernel, please see the SphereKat thread!
*
Samsung Milk Music - Powered by Slacker
- Milk is supposedly available for all Galaxy devices, except it's not available for all Galaxy devices. I've added it here for you all to enjoy
*
Amazon Kindle for Samsung
Special Note:
* Images are copyright to their respective owners
A GT-N5110
One of the latest recoveries that supports Andoird 4.4. I recommend the latest PhilZ recovery: Found here, flash in ODIN
Bootloader upgrade: With Civato's SphereKat kernel, the 4.4 bootloader upgrade is no longer required!
IF YOU DO NOT MEET THESE REQUIREMENTS.. STOP HERE!
A full wipe is only necessary if coming from a different ROM, including Terok Nor v2. All updates to v3 r1+ can be dirty flashed (unless otherwise noted).
1. BACKUP BACKUP BACKUP!
2. Flash
3. Reboot
(click the image ^)
MD5 hash: 25e41bad0695fc543dd75bde681fefb0
Don't forget to hit the thanks button!
XDA:DevDB Information
Terok Nor v3, ROM for the Samsung Galaxy Note 8.0
Contributors
MrHyde03
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: 4.4.2 Bootloader and TZ
Based On: UEU2CNE2 Official 4.4.2
Version Information
Status: Stable
Created 2014-05-26
Last Updated 2014-08-18
2014-06-30
Release 6
Added Android L Keyboard!
Added Galaxy S5 Boot Animation
Updated @civato 's SphereKat to v4.0
2014-06-10
Release 5
Removed S Note 3.1 (If you want, the install this APK S Note 3.1 APK
Rebuild on UEU2CNE2 US Official Firmware (XAR)
Now released with @civato's SphereKat kernel! Make sure you hit THANKS in his SphereKat thread and send him a beer!
Bootloader upgrade: With Civato's SphereKat kernel, the 4.4 bootloader upgrade is no longer required!
2014-05-28
Release 4
Deodexed /system/app, /system/framework, and /system/priv-app
2014-05-27
Release 3
Corrected issues brought on by R2 where the device would not boot after a clean flash.
2014-05-26
Release 2
Enabled Scrolling wallpaper in SecLauncher3.apk (TouchWiz Launcher)
Corrected Text Cursor offset in framework-res.apk, Thanks Civato
2014-05-26
Release 1
Initial release
Civato
All others who've made modding Android possible
Thanks to all who have donated I hope I can continue bringing a stable, smooth experience to the great people here at XDA :good:
Each * represents an additional donation! Much appreciated!!
rfb813 *
There are currently two versions of S Note installed. The orange-red icon is the new version which is available on the GS5 as a "Galaxy ESSENTIAL". The brown icon is the stock Note 8 version. I may remove one of them in future updates.
STOCK KERNEL AND RECOVERY
Download this zip file and extract. The kernel (boot) and recovery are in their own .tar.md5 archives. Flash each in ODIN.
yay!
@MrHyde03
Regarding the S-pen cursor offset (cursor when hovering above a text with the pen), I fixed it in the framework (for the s-pen pointer I'm still waiting for kernel source, I mailed samssung yesterday for the source)
Here is the file for the framework file.
Decompile the framework and drop it in res/drawable-tvdpi.
When compiling the framework again it will throw some errors.
To slove this:
Go to res/drawable-tvdpi and remove the following files
tw_scrubber_control_focused_holo_red.PNG
tw_scrubber_control_holo_red.PNG
Then go to res/values/strings
open that file and on the line 1795 remove the % before the d and before the 2$s
it should look like this
Code:
<string name="wifi_p2p_enter_pin_dialog_message">Enter the PIN and tap Connect within d seconds to connect to 2$s.</string>
now compile and the errors will be gone.
civato said:
@MrHyde03
Regarding the S-pen cursor offset (cursor when hovering above a text with the pen), I fixed it in the framework (for the s-pen pointer I'm still waiting for kernel source, I mailed samssung yesterday for the source)
Here is the file for the framework file.
Decompile the framework and drop it in res/drawable-tvdpi.
When compiling the framework again it will throw some errors.
To slove this:
Go to res/drawable-tvdpi and remove the following files
tw_scrubber_control_focused_holo_red.PNG
tw_scrubber_control_holo_red.PNG
Then go to res/values/strings
open that file and on the line 1795 remove the % before the d and before the 2$s
it should look like this
Code:
<string name="wifi_p2p_enter_pin_dialog_message">Enter the PIN and tap Connect within d seconds to connect to 2$s.</string>
now compile and the errors will be gone.
Click to expand...
Click to collapse
Awesome. You just saved me some time.:highfive: Also, you don't have to delete the two PNGs, just change the extension from PNG to png. I also emailed Samsung on Saturday but have not had as much as a peep from them. Aren't they required under GPL to release the source when their software is released?
Anyways, thanks again Civ.
Updated to Release 2! Check Change Log for details.
Clean flashing to R2 is broken. Only works if dirty flashing. Because of this I've pulled R2 from the download. Go back to R1 if you're having issues with booting. I know what the issues are, I just don't have time tonight. It's late.
I've udpated the download URL to reflect R1.
MrHyde03 said:
Awesome. You just saved me some time.:highfive: Also, you don't have to delete the two PNGs, just change the extension from PNG to png. I also emailed Samsung on Saturday but have not had as much as a peep from them. Aren't they required under GPL to release the source when their software is released?
Anyways, thanks again Civ.
Click to expand...
Click to collapse
Yep they should release it . But some delay is expected.
Fixed the issues from R2. R3 is out and stable.
I could not get R2 to boot at all past the Samsung splash. I'll download R3 tonight. Thank you.
Sent from my GT-N5110 using XDA Premium HD app
glockman4519 said:
I could not get R2 to boot at all past the Samsung splash. I'll download R3 tonight. Thank you.
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
Yep.. that was my fault.. sorry. I didn't properly recompile a few APKs, but we're all good now.
Release three working fine! Thanks and have one on me:4C4716763M934291T.
rfb813 said:
Release three working fine! Thanks and have one on me:4C4716763M934291T.
Click to expand...
Click to collapse
Glad you're enjoying it! Thanks!
2014-05-28
Release 4
Deodexed /system/app, /system/framework, and /system/priv-app
I was beginning to think this ROM wasn't going to install for me. I did an MD5 check - it passed. I flashed the new bootloader firmware and then flashed the PhilZ recovery. Tried to install the ROM and got an Error: Status 7. Tried the newer CivZ recovery and same thing.
Finally got it to install using TWRP 2.6.3 (my favorite, anyway).
Now going to try restoring data from v2.1 and see how that goes.
mletchworth said:
I was beginning to think this ROM wasn't going to install for me. I did an MD5 check - it passed. I flashed the new bootloader firmware and then flashed the PhilZ recovery. Tried to install the ROM and got an Error: Status 7. Tried the newer CivZ recovery and same thing.
Finally got it to install using TWRP 2.6.3 (my favorite, anyway).
Now going to try restoring data from v2.1 and see how that goes.
Click to expand...
Click to collapse
That is odd.. I flashed and reflashed and wiped then reflashed over and over to make sure I didn't have any more duds like R2 was and haven't had any issues with R4. Regardless, I'm glad you got it to flash.
Let me know if you have any other issues.
MrHyde03 said:
Let me know if you have any other issues.
Click to expand...
Click to collapse
Well, don't try restoring data from v2.1, it'll just cause tons of crashes and an error message that the Android UID doesn't match. Guess I'll be TiBU-ing this morning. Just as well, I see that R4 just posted...
mletchworth said:
Well, don't try restoring data from v2.1, it'll just cause tons of crashes and an error message that the Android UID doesn't match. Guess I'll be TiBU-ing this morning. Just as well, I see that R4 just posted...
Click to expand...
Click to collapse
If you're restoring from the same version recovery the backup was created with, then you shouldn't have any issues. That's been my experience. I've always had things break if I restore with a different recovery.
Should you update the firmware to the new Canadian firmware found on samfirmware? It was released after the UK firmware and Canada is closer to the US but there are probably no differences... just asking
Hello guys,
Now we can try Android 5.0 on our LG Optimus G (I'm using it on E970).
Thanks a loooooot to @Kevinjoa for his port.
Thanks to @KevTheGuy for his detailed info about this port.
***CAMERA is working fine, including 'lens blur' feature***
***Don't flash any GAPPS
***Flash the kernel (linked below)
***TWRP is the preferred recovery method
Caution:
NFC not working.
SD Card can not be mounted.
Link to the original posts:
From XDA
From another blog
*Download the latest release from HERE
*Flash this KERNEL
*Flash SuperSU to get root access.
Instructions:
1. Backup your current ROM
2. Wipe 'System', 'Data', 'Dalvik Cache' & 'Cache'
3. Flash the ROM -> Kernel -> SuperSU. One by one.
4. Wipe 'Dalvik Cache' & 'Cache'
5. Reboot & give it atleast 5 minutes for 1st boot.
Google Now Launcher (Andorid 5.0) link:
http://www.dropbox.com/sh/1u17g3me7y308mo/AADNYxVzkfVbsKPnXYjIb5_Ea?dl=0
Other Google Apps (Android 5.0) link: (Just install 'Gmail, Calendar for material design experience. Other apps already installed in the ROM)
https://www.dropbox.com/sh/m8rw7h4rytjbo7d/AAD4TOXeQuCtpoMR9z1jlA27a?dl=0
Thanks
Screenshot:
{
"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"
}
Thank you going to try it.. Need to found some fix to sd its very important
danielad200 said:
Thank you going to try it.. Need to found some fix to sd its very important
Click to expand...
Click to collapse
You are welcome . Yeah, I'm looking for that too.
is the camera working correctly on geeb?
The builds provided in the link you posted are from @Kevinjoa , and he has a thread on the Sprint LG Optimus G forums (http://forum.xda-developers.com/optimus-g-sprint/development/port-android-l-preview-gee-t2818325). There are more posts and active members there, so anyone that wants to know what's up should head there.
Also, Data doesn't work with kernelgeeb.zip on release 17 (just tested it)
You can get Data and camera to work on release 17 (or any Kevinjoa's builds i think) with this kernel (https://mega.co.nz/#!VNcRCCiK!I0cV-A1MgcEsTWsx07zVmxEDGgQIjt7DjP_dEqY_WwU) but then wifi doesnt work. Right now I'm experimenting replacing some wifi files in the rom to see if wifi works with the jollaman's kernel provided above.
I'll report back as soon as I can.
And btw thanks for creating this thread here on e970 forums, I don't think everyone knows about the Spring OG thread
EDIT2: Well turns out making a flashable zip isn't as simple as I thought xD
EDIT1: Ok so I got Wifi, Data, and camera working on release 17 with jollaman's geeb kernel for L, though autorotation gets bugged most of the times i think.
For those interested:
I took all wifi-related files in this rom (https://mega.co.nz/#!xB9xGSpK!kGCJo_GiLqRhPneqbv95xckbSmL2UMQbs7kdn0kZyAU)
from these folders:
\system\etc\wifi
\system\vendor\firmware\wlan\prima
\system\etc\firmware\prima
and copied them to the respective folders in release 17 rom.
Then I flashed the modified rom file and the jollaman kernel.
I can try to make a flashable zip of the wifi files, though i have never done it before.
And also, I read that jollaman999 is working on v12 of his kernel which would be compatible with Lollipop, so in the meantime if you want jollaman's kernel features then this is the way to go
uumeshh said:
is the camera working correctly on geeb?
Click to expand...
Click to collapse
Camera is working, including 'Lens Blur' feature.
KevTheGuy said:
The builds provided in the link you posted are from @Kevinjoa , and he has a thread on the Sprint LG Optimus G forums (http://forum.xda-developers.com/optimus-g-sprint/development/port-android-l-preview-gee-t2818325). There are more posts and active members there, so anyone that wants to know what's up should head there.
Also, Data doesn't work with kernelgeeb.zip on release 17 (just tested it)
You can get Data and camera to work on release 17 (or any Kevinjoa's builds i think) with this kernel (https://mega.co.nz/#!VNcRCCiK!I0cV-A1MgcEsTWsx07zVmxEDGgQIjt7DjP_dEqY_WwU) but then wifi doesnt work. Right now I'm experimenting replacing some wifi files in the rom to see if wifi works with the jollaman's kernel provided above.
I'll report back as soon as I can.
And btw thanks for creating this thread here on e970 forums, I don't think everyone knows about the Spring OG thread
EDIT2: Well turns out making a flashable zip isn't as simple as I thought xD
EDIT1: Ok so I got Wifi, Data, and camera working on release 17 with jollaman's geeb kernel for L, though autorotation gets bugged most of the times i think.
For those interested:
I took all wifi-related files in this rom (https://mega.co.nz/#!xB9xGSpK!kGCJo_GiLqRhPneqbv95xckbSmL2UMQbs7kdn0kZyAU)
from these folders:
\system\etc\wifi
\system\vendor\firmware\wlan\prima
\system\etc\firmware\prima
and copied them to the respective folders in release 17 rom.
Then I flashed the modified rom file and the jollaman kernel.
I can try to make a flashable zip of the wifi files, though i have never done it before.
And also, I read that jollaman999 is working on v12 of his kernel which would be compatible with Lollipop, so in the meantime if you want jollaman's kernel features then this is the way to go
Click to expand...
Click to collapse
I'm on E970 & camera, wifi worked perfectly. But thanks a lot for your detailed post. Is there any patch for SD card & NFC? Except these 2 things, this ROM is not bad!
mtatohin said:
I'm on E970 & camera, wifi worked perfectly. But thanks a lot for your detailed post. Is there any patch for SD card & NFC? Except these 2 things, this ROM is not bad!
Click to expand...
Click to collapse
Not yet. That's what's keeping me from using this rom as a daily driver :c .
I guess Jollaman's kernel v12 will fix those issues, but as far as I know, there is no word on when he's releasing it
KevTheGuy said:
Not yet. That's what's keeping me from using this rom as a daily driver :c .
I guess Jollaman's kernel v12 will fix those issues, but as far as I know, there is no word on when he's releasing it.
Click to expand...
Click to collapse
are you sure? v12 is here for geeb
http://buf.jollaman999.com/jolla-kernel_AIO-gee/
samuel3mn2 said:
are you sure? v12 is here for geeb
http://buf.jollaman999.com/jolla-kernel_AIO-gee/
Click to expand...
Click to collapse
EDIT: Well the v12 does have the option for android L kernel, but then wifi and data dont work, and still no SD card mounting : |
Wou that's new. sorry, I'll edit my post, and try it on android L release 17 to see how it goes.
according to jollaman999 camera is working and he added sd card init lines for geeb (http://forum.xda-developers.com/opt...el-jolla-kernel-cm-based-roms-t2851612/page46).
Sd card still not working with the new kernel
I am was install the kernel camera works perfectly but 3g data is dissaper
How stable is this to use as an everyday?
@mtatohin,
Nice work on the post
I tried the Android L Porting with Kernel "jolla-kernel_AIO_V12_Rev2-geeb,e970" and finding trouble in.....
---------------
1. No reboot option.
2. Camera can't connect error.
3. NFC Not working.
4. Data connection not working. Tried the steps to manually add the APN's but still problem exists.
5. SD not Mounted.
---------------
I did a clean install.
Please help for the above with any fixes.
Thank you.
P.S You are doing a Good Job.:good::good:
Is there no way to enable sad card?
Mikeandrd2292 said:
Is there no way to enable sad card?
Click to expand...
Click to collapse
As been mentioned many times in this thread, no. It might require a framework modification.
Amazing work!
Rockwig said:
As been mentioned many times in this thread, no. It might require a framework modification.
Click to expand...
Click to collapse
Is there no way to enable the happy card?
Sent from my AT&T LG Optimus G
plaster said:
Is there no way to enable the happy card?
Sent from my AT&T LG Optimus G
Click to expand...
Click to collapse
You could try decompiling the framework-res.apk and then modifying the file "storage_list.xml" in "res/xml/" and add the proper values, something like:
"<storage
android:mountPoint="/storage/sdcard1"
android:storageDescription="@string/storage_sd_card"
android:removable="true"
android:maxFileSize="4096" />"
(from https://source.android.com/devices/tech/storage/config-example.html)
after the existing entry in there.
Then you would need to recompile the .apk and add that to the device.
After that, it might show up (with the right Kernel).
Rockwig said:
You could try decompiling the framework-res.apk and then modifying the file "storage_list.xml" in "res/xml/" and add the proper values, something like:
"<storage
android:mountPoint="/storage/sdcard1"
android:storageDescription="@string/storage_sd_card"
android:removable="true"
android:maxFileSize="4096" />"
(from https://source.android.com/devices/tech/storage/config-example.html)
after the existing entry in there.
Then you would need to recompile the .apk and add that to the device.
After that, it might show up (with the right Kernel).
Click to expand...
Click to collapse
thanks for this..
will try soon..
i read that for proper ad card support we neen to mod kernel, framework-res.apk and platform.xml..
will you tell us what we need to do with kernel and platform.xml ?
TEAM ACHERON PRESENTS
{
"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"
}
Stock ROM for SM-T231 Galaxy Tab 4 7in.
This was requested and tested by a private user. This is just a Base Stock SM-T231 Odexed ROM. Nothing flashy just stock and stable.
Thanks to @niviljacob for the request, testing and support so I could build this. I do not have this device.
The CREDITS
TEAM ACHERON - for the love and support
@scarmon25 - Amazing teacher
@lickarock - Amazing teacher and much patients
@bix2010 - Awesome Team member
@bilgerryan - One hell of a Dev & good guy
@ShinySide - root and recovery guide
@safariking - working with him on the SU/Root issues on the tab 4 7in
@AL_IRAQI - for support of this device and the ideas
@moonbutt74 - for the dev knowledge & community attitude of helping when you can
@niviljacob - Testing and requesting
Change log :
Code:
[U][B]Updated : [/B][/U]
Rom Base to XXU0APB1
SuperSU 2.72 stable
hosts file : 2016.05.13 list
[B][U]Added : [/U][/B]
SELinux permissive script
[B][U]Removed : [/U][/B]
Vac and fix FC scripts
dropbox and google drive from /system/app (saved 25MBs)
What's included :
Root - Superuser 2.72
Init.d support w/ scripts - clear browser cache & permissive SELinux
Ad blocking hosts file
Busybox
Removed :
few google apps - can be downloaded from the play store
dropbox - can be downloaded from play store
Install instructions
download ROM to device (internal or external)
VERIFY MD5 SUM BEFORE FLASHING!!!
reboot to recovery (TWRP)
Wipe cache / dalvik cache / data and system
install ROM zip
(not needed but you can wipe cache and dalvik cache after install again)
reboot - boot time will take around 4-5 mins - everything is being set up
set up accounts / preferences / normal set up
$$$profit$$$
DOWNLOAD LINK :
BUILD [APB1] :
link : https://www.androidfilehost.com/?fid=24533100289591280
MD5 SUM : b5536a4489d1a29b936f4f09a91995c7
Mirror (MEGA) update #1 : https://mega.nz/#!ClA22bBC!plFOD_8KhpzzXYk_kJ7-9FLHX-024Vj2btWYXTEpmTY
MD5 SUM : b5536a4489d1a29b936f4f09a91995c7
----
OLD RELEASE :
link update #1 : https://www.androidfilehost.com/?fid=95916177934547691
MD5 SUM : 6aa7e8797f05c653fd1e88d2816d7f2c
Mirror (MEGA) update #1 : https://mega.co.nz/#!rgIGBJTI!Om5FBXkKReuyat9WdSm_ISeACAn_ZRX6b2IV7oaPLzg
MD5 SUM : 6aa7e8797f05c653fd1e88d2816d7f2c
link - inital build : https://www.androidfilehost.com/?fid=95916177934538816
MD5 SUM : ac6e23c032e981f12b6d5ae839c5d710
Mirror (MEGA) - inital build : https://mega.co.nz/#!2sIXgZKD!61fqu14t_NbVxa9FSDGtagjsUBlT5KXkB0hEsOmK4MM
MD5 SUM : ac6e23c032e981f12b6d5ae839c5d710
ROM OS Version: 4.4.2 TW Kitkat
ROM Kernel: Linux 3.10.0
Based On: Samsung Stock Firmware
Version Information
Status: Stable
Created 2015-03-08
Last Updated 2016-5-14
Click to expand...
Click to collapse
-
IS YOUR SUPERSU UP TO DATE? GO HERE TO FIND OUT
-
Stable : http://forum.xda-developers.com/showthread.php?t=1538053
-
Beta : http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
KNOWN ISSUES
HOW TO REPORT A BUG : (BUG REPORT TEMPLATE, IF YOU WANT A RESPONSE FOLLOW THIS!!!)
Device: (device name aka - T230 or T-230NU)
Baseband: (NG2 / NK2 ect...)
ROM Ver: (build number of ROM)
Description: (please state install -full wipe or dirty flash, what's wrong and a way to recreate the issue)
KNOWN ISSUES :
Gallery FC - fixed in update #1
T231 Stock kernel
LINK : https://www.androidfilehost.com/?fid=95916177934547297
MD5 SUM : 5212e0e836ec5de8926bc92093356717
guides/walkthroughs/mods
Basic tips :
http://forum.xda-developers.com/showthread.php?p=58109782
Marshmallow wallpaper
Wow nothing? Guessing this wasn't in high demand.
uploaded DeOdexed version in the OP. Download links available. uploading mirror (MEGA) as we speak.
Not working on my samsung galaxy tab 4 7.0 SM-T231 cx.
And if you wipe system and data you will compeletly lose the os
that is so wrong
bad work!!
emoboy (Official Name!) said:
Not working on my samsung galaxy tab 4 7.0 SM-T231 cx.
Click to expand...
Click to collapse
How did you flash the ROM?
Which version did you flash?
Please be a bit more descriptive. I don't have this device.
emoboy (Official Name!) said:
And if you wipe system and data you will compeletly lose the os
that is so wrong
bad work!!
Click to expand...
Click to collapse
Did you download the deodexed version? Try to odexed version. I need to fix the DeOdexed version. I'm pulling the download links now.
g_ding84 said:
How did you flash the ROM?
Which version did you flash?
Please be a bit more descriptive. I don't have this device.
Did you download the deodexed version? Try to odexed version. I need to fix the DeOdexed version. I'm pulling the download links now.
Click to expand...
Click to collapse
if you dont have this device then dont make work for it thx
and i will try the ODEXED version.
emoboy (Official Name!) said:
if you dont have this device then dont make work for it thx
Click to expand...
Click to collapse
If you read page 3 of this thread especially posts 24 and 25, you will see that g_ding84 was specifically asked to make a rom for this device (since there were no others at the time), and after consideration he did it as a selfless service to the community. It certainly is frustrating when roms do not work as they are supposed to, but this is a development forum, a development community. We should be grateful when an expert member like g_ding84 takes it upon themselves to make more roms. Nobody makes you install roms, and when you choose to do so, it is with the implicit understanding that they are unofficial, custom OS's and that support, whether or not ongoing for the rom itself, also largely depends on the user base too.
Also don't bite the hand that feeds you. If nobody else is developing for this device, are you really going to hold it against the one person trying to help you guys out that he doesn't have the device? That's a lot more common on XDA than you might realize.
Just want to say thanks to the developer, nice try though you don't have a device, you still manage or develop this Rom.
Tried deodexed version but didn't work, shall try odexed version.
Advice to those who want to try, make sure you have a backup just incase.
Edit Odexed version works, shall observe
thisisapoorusernamechoice said:
If you read page 3 of this thread especially posts 24 and 25, you will see that g_ding84 was specifically asked to make a rom for this device (since there were no others at the time), and after consideration he did it as a selfless service to the community. It certainly is frustrating when roms do not work as they are supposed to, but this is a development forum, a development community. We should be grateful when an expert member like g_ding84 takes it upon themselves to make more roms. Nobody makes you install roms, and when you choose to do so, it is with the implicit understanding that they are unofficial, custom OS's and that support, whether or not ongoing for the rom itself, also largely depends on the user base too.
Also don't bite the hand that feeds you. If nobody else is developing for this device, are you really going to hold it against the one person trying to help you guys out that he doesn't have the device? That's a lot more common on XDA than you might realize.
Click to expand...
Click to collapse
okeyy thanx i know xD
i just give him a feedback and now the DeOdex version removed for not work and make stuck at boot (bootloop)
i think i helped him cx
sunrider07 said:
Just want to say thanks to the developer, nice try though you don't have a device, you still manage or develop this Rom.
Tried deodexed version but didn't work, shall try odexed version.
Advice to those who want to try, make sure you have a backup just incase.
Edit Odexed version works, shall observe
Click to expand...
Click to collapse
The private tester reported the deodexed version didn't work. I think I know what went wrong. (Deodex compression setting)
Thank you for testing as well. I'll have a test version going this weekend. Sat or Sun check your PM
Thank you very much for the kind words.
Its hard to Dev for a device you don't own. But I enjoy the challenge. (The partition layout between the SM-T230/NU and the SM-T231 are the same. So that was a huge help.
I'm hoping to get a stable base going so another "potential" Dev can step in and take over.
I updated the 2nd post with the Stock SM-T231 kernel.......doesn't hurt to have a copy. I'm returning to show some love and will work on fixing the known issues.
new update is uploaded. Download links are available.
change log :
fixed gallery FC
added 92sqlite3 data base optimization and 94fixfc fixes permissions on each reboot.
Thanks
Thanks so much for your work.
Downloading and will install soon.
Thanks a lot for your hard work.
Hi
Any chance that you would fully DeBloat the ROM ?
Thanks! <3
Inpain said:
Hi
Any chance that you would fully DeBloat the ROM ?
Thanks! <3
Click to expand...
Click to collapse
Check out post#2 in my other thread. Three debloater scripts. Choose which one you want and flash in recovery.
Remove google apps (except play store and service framework)
Remove Samsung apps
Remove Samsung and google apps
Located here:
http://forum.xda-developers.com/showthread.php?p=58109771
I can make a debloated version but since I don't have the 3G model I'm not sure what's safe to remove. If someone is willing to assist I will.