DEAD - Galaxy Tab 4 Android Development

CLOSED

---

reserved

---

reversed
xD

---

moonbutt74 said:
reversed
xD
Click to expand...
Click to collapse
Thanks

---

CM12
Thought you said you was not going to do anything to do with cm12 xD

---

denniso08 said:
Thought you said you was not going to do anything to do with cm12 xD
Click to expand...
Click to collapse
I umm....RUN AWAY !!!
okay, okay i fibbed a little, you got me... :laugh:
@sub77 's build is running quite nicely !
We need a theme package, seperate from having to goto google play.
At least for the browser, it's so [BLEEPING] ugly.
m

---

device ue?
It wont let me flash his rom due to it being a ue device, why is that?
Please help me, i want to Lollipop :3

---

denniso08 said:
It wont let me flash his rom due to it being a ue device, why is that?
Click to expand...
Click to collapse
D,
hi,
because this kernel package is for the milletwifiue sm-t330nu
to address the shortcomings of the kerne in sub77's cm12 rom build for
the sm-t330nu,
Additionally, i make no adjustments for twrp, i use my own recovery build [Philz]
also, i will not remove the updater-script device assert. That is for the individual user to do.
Now that being said, remove the assert from the updater script and give it a try, just , as always, make
a backup first.
This is not, as per OP, not for the sm-t530/nu/31 etc.
m

---

Notacoder.com
I have no clue how I would do that xD

---

neitheramibutitsnothathard.gov/NSA/nicepr0nfolderyagotthereson
denniso08 said:
I have no clue how I would do that xD
Click to expand...
Click to collapse
It's a zip file. Open it on your PC with winrar or 7zip, go to META-INF/com/google/android/ and extract updater-script. Open it with notepad++ and edit out the first few lines, it should be pretty self-evident which lines comprise the assert. Delete those. Put the edited updater-script right back in the same folder in that zip and flash it. Also doable on your tablet, but it's a tad more cumbersome doing it that way, always easier to do on a PC.

---

moonbutt74 said:
D,
hi,
because this kernel package is for the milletwifiue sm-t330nu
to address the shortcomings of the kerne in sub77's cm12 rom build for
the sm-t330nu,
Additionally, i make no adjustments for twrp, i use my own recovery build [Philz]
also, i will not remove the updater-script device assert. That is for the individual user to do.
Now that being said, remove the assert from the updater script and give it a try, just , as always, make
a backup first.
This is not, as per OP, not for the sm-t530/nu/31 etc.
m
Click to expand...
Click to collapse
Ummm, but.... The galaxy tab 4 sm-t330nu Is the milletwifiue..... If it's the same as the cm 12.1 ROM it won't flash because the milletwifi and the milletwifixx are the only two models included in the asserts, which is totally backwards since it explicitly states it's for the milletwifiue. IMO
Edit:
Nope it should flash on his device, the kernel package does include the milletwifiue in its assert
Edit 2:
Totally missed that the original question was about the ROM, not the kernel. If you look in the ROM thread this was covered yesterday

---

Exile1975 said:
Ummm, but.... The galaxy tab 4 sm-t330nu Is the milletwifiue..... If it's the same as the cm 12.1 ROM it won't flash because the milletwifi and the milletwifixx are the only two models included in the asserts, which is totally backwards since it explicitly states it's for the milletwifiue. IMO
Click to expand...
Click to collapse
Yes, however, I am only answering questions about this kernel package. Questions about the rom should be asked on sub77 's thread.
This is the assert for MY updater script
Code:
assert(getprop("ro.product.device") == "milletwifi" ||
getprop("ro.build.product") == "milletwifi" ||
getprop("ro.product.device") == "milletwifiue" ||
getprop("ro.build.product") == "milletwifiue" ||
getprop("ro.product.device") == "milletwifixx" ||
getprop("ro.build.product") == "milletwifixx" ||
abort("This package is for device: milletwifi,milletwifiue,milletwifixx; this device is " + getprop("ro.product.device") + "."););
This is the assert for sub77's updater script
Code:
assert(getthread("ro.sub77's-rom.thread") == " http://forum.xda-developers.com/tab-4/development/rom-cyanogenmod-12-1-t3097152 " ||
abort("This is the wrong thread for your question: http://forum.xda-developers.com/tab-4/development/rom-cyanogenmod-12-1-t3097152; this thread is " + getprop("ro.moonbutt74's-kernel.thread") + "."););
xD
okay seriously though change or update your recovery, there's nothing backwards or conspiratorial about screwy device asserts, it happens.
or remove the assert.
And when all else fails see this video before proceeding https://www.youtube.com/watch?v=JmvCpR45LKA
{
"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"
}
m

---

moonbutt74 said:
Yes, however, I am only answering questions about this kernel package. Questions about the rom should be asked on sub77 's thread.
m
Click to expand...
Click to collapse
Guess we both misread the original question then since it was about the ROM.
But hey, wanted to say thanks for the kernel. Working beautifully.

---

Exile1975 said:
Guess we both misread the original question then since it was about the ROM.
But hey, wanted to say thanks for the kernel. Working beautifully.
Click to expand...
Click to collapse
E,
hi, are you experiencing the issue with power off charging ?
I think i have it pegged to lpm
after looking through the stock boot.img the lpm service is there
calling to /system/bin/lpm
which relies on [proprietary]
libmaet.so
libsxqk_skia.so
if you would, make a backup of your current rom and reflash sub77's release without flashing my kernel.
after you done getting through setup, make sure the tab is not connected to usb or power,
then shut off your device and plug it in. i am trying to determine if it's in the kernel or ramdisk config/setting is missing.
thanks.
m
to users of my cm11 build, also please let me know if this issue is occuring since it is the same kernel.

---

moonbutt74 said:
E,
hi, are you experiencing the issue with power off charging ?
I think i have it pegged to lpm
after looking through the stock boot.img the lpm service is there
calling to /system/bin/lpm
which relies on [proprietary]
libmaet.so
libsxqk_skia.so
if you would, make a backup of your current rom and reflash sub77's release without flashing my kernel.
after you done getting through setup, make sure the tab is not connected to usb or power,
then shut off your device and plug it in. i am trying to determine if it's in the kernel or ramdisk config/setting is missing.
thanks.
m
to users of my cm11 build, also please let me know if this issue is occuring since it is the same kernel.
Click to expand...
Click to collapse
M,
I did a factory reset and restored a backup from stock. Did anther factory reset and installed the CM package. First boot was fine, restarted, shut down, plugged in, and it charges while remaining shut off. With your kernel I have what is described elsewhere. When the tablet is turned off and I plug in, the charging icon shows briefly, then the tablet boots. Hope this helps.

---

E,
hi, thanks, i am reworking my source.
m

---

[kernel] cm12 sm-t330nu - UPDATED
okay,
after a couple of tests the issue seemed to be with the ramdisk sepolicy/init.
Power off charging issue should be resolved as per my testing
cm12-kernel-carmilla-linaro-milletwifiue-V2.zip
https://www.androidfilehost.com/?fid=23991606952596384
m

---

moonbutt74 said:
okay,
after a couple of tests the issue seemed to be with the ramdisk sepolicy/init.
Power off charging issue should be resolved as per my testing
cm12-kernel-carmilla-linaro-milletwifiue-V2.zip
https://www.androidfilehost.com/?fid=23991606952596384
m
Click to expand...
Click to collapse
M,
I can confirm it charges while off now. As far as stability it seems rock solid, but I'll let you know if I notice anything. Thanks again for all your hard work and super fast response to solve this. If there's ever anything I can do for you just let me know.

---

Exile1975 said:
M,
I can confirm it charges while off now. As far as stability it seems rock solid, but I'll let you know if I notice anything. Thanks again for all your hard work and super fast response to solve this. If there's ever anything I can do for you just let me know.
Click to expand...
Click to collapse
E,
hi, thank you for your reply, by all means update me, it's how i learn.
Keep your posts in the right threads and we're good, no worries. :good:
m

---

moonbutt74 said:
E,
hi, thank you for your reply, by all means update me, it's how i learn.
Keep your posts in the right threads and we're good, no worries. :good:
m
Click to expand...
Click to collapse
Mine charges now to while its turned off. Thanks