yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 8.9 Android Development] L3R0N:
Can you pull the last_kmsg log after a reboot and post here. Seems like its some kernel issue but I have to be sure. I have not had a reboot so I cannot pull the log myself. The other option is to make a modified boot.img from a 4.4 zImage+5.1.1 Ramdisk like I did for the p5 AOSP ROMs. I'll try that option and test if it works and if it does then I'll use that boot.img instead.

Use this to get that log

adb pull proc/last_kmsg

I'm waiting for this weeks Omni build so I can do a port because I didn't want to port last weeks build then port this weeks build again. I'll just wait for the build this week and port.
[Galaxy Tab 8.9 Android Development] L3R0N:
Thanks to [MENTION=2931572]AAccount[/MENTION] we have a new Omni build.

Usual Omni sync and chromium is newly rebuilt in this build.

I've been noticing that some people actually miss the Lollipop nav keys ie circle, triangle and square buttons. So I'm thinking of bringing them back in the next build as well as returning the nav bar to its default size. What are your thoughts on this?

P5 users can flash the P5 wifi build with no issues as I have removed the assert lines from the updater script. Also I've reverted the kernel from v17 down to v16 for better stability. I've never had a problem using the v17 kernel but apparently some people did. The download link has been updated in the OP so find it there.

regards,

L3R0N
[Galaxy Tab 8.9 Android Development] julen163:
HI L3R0N, really thanks for all your hard work, in order to maintain our toy with the last android version.

I really appreciate this...

Thanks to you we still can use it like new one....??.

I want to warn you that in the first post, there is the link to your latest version 20150806, but as your last post... We were waiting for the 20150814 version published at the p4 forum... Did you update correctly the first post?

Thanks a lot

Enviado desde mi LG-D855
[Galaxy Tab 8.9 Android Development] L3R0N:
I'm sorry I uploaded the wrong file.I will upload the correct one as the day progresses. And the build is 20150815 not 20150814. Thanks for pointing that out.
[Galaxy Tab 8.9 Android Development] L3R0N:
Correct build has been uploaded. OP updated with correct link to file.
[Galaxy Tab 8.9 Android Development] AAccount:
If you like the triangle, circle, square that's fine. Bring it back in your rom. I personally really don't like the minimalist thing. Not really into the whole "flat single color icon" trend that's going on either. That's art for you: some people like it, some don't. You'll never end up pleasing everyone :cyclops:

As for the nav bar I also don't like the "new" 2 bar layout as opposed to the single bar ICS layout. I think it's a huge waste to use the bottom bar just for 3 icons. That's why I shrunk it down. I tried not to shrink it down too much that the icons are hard to hit but if you want to expand it back to its original it's your rom. I think there are 2 or 3 commits I made you can undo to get the original 5.X look.
[Galaxy Tab 8.9 Android Development] Rommul:
I have a question. Does this rom work on the GT-P7310MVGR?
[Galaxy Tab 8.9 Android Development] L3R0N:
I don't mind the change but apparently some do. How hard is it to implement RRO? RRO would help users get the changes that they want. There's always xposed but I've tried it and there's always a slight lag every time I install it on either Omni or AOSP so I stopped using it altogether. There's always theming via apk modifications but that's to much work :p .
[Galaxy Tab 8.9 Android Development] drwtsn32x:
Same here. I wiped/formatted all partitions to ensure a clean install.

Keyboard never pops up.

---------- Post added at 06:32 PM ---------- Previous post was at 06:25 PM ----------

same here.... rebooting on its own every few minutes. :(
[Galaxy Tab 8.9 Android Development] L3R0N:
I can't say what is up with the keyboard because I don't have that problem. Never had that problem. Turning on the hardware flag has always given me my keyboard back. However for the reboots please pull the last kmsg log and post it here so I can have a look at what causes it.

adb pull proc/last_kmsg
[Galaxy Tab 8.9 Android Development] L3R0N:
Hey guys, there will not be an update to the Rom here for this week or the next few weeks. Reason being that my island country was hit by Tropical Storm Erika which caused massive damage to the islands infrastructure, loss of property and sadly loss of life. We were hit without watch or warning and this system caught many unprepared. I currently have no internet connection at home as a result and there is no way of telling when it will be back up. Even if I do get my internet connection back up I still won't be able to post here because I've volunteered to assist the Dominica Red Cross and that will keep me busy. Please keep my country in your prayers as we rise slowly from the rubble that Erika left us.
[Galaxy Tab 8.9 Android Development] filipe_m:
[MENTION=5944750]L3R0N[/MENTION]

I'm sorry for the situation in your country.

I hope it improves quickly ...

Concerning this rom:

What are the known issues?

Thank you!!
[Galaxy Tab 8.9 Android Development] L3R0N:
Thanks. I hope so to.

Some users report wifi only connects when a static IP is used however I haven't had that problem. Others report random reboots but I don't have this problem either. Besides these there are no other problems afaik. Try it out and see how it works.
[Galaxy Tab 8.9 Android Development] L3R0N:
Thread is being temporarily marked as Discontinued. See post #2 for reason.
[Galaxy Tab 8.9 Android Development] filipe_m:
I installed the ROM and had both problems of which you speak.

After installation I got 2 gb less of rom free space ...

I would like to erase all the tablet's content and do a fresh installation,

But do not know how to do it ... If in the TWRP i erase everything, including internal memory, how i made the installation of the new rom?

Can anyone give me some tips or direct me to a manual?

Thank you

Enviado do meu ASUS_Z00AD através de Tapatalk
[Galaxy Tab 8.9 Android Development] swaaye:
Format system and then flash the new ROM. Then format data and cache. Boot up and download gapps with the stock browser. Reboot to TWRP and install gapps.
[Galaxy Tab 8.9 Android Development] swaaye:
I gave this ROM a try and I am unable to connect to wifi. Searched the thread and found that it is some kind of problem with DHCP and that a static IP is a "workaround". That's a fairly major problem. :)
[Galaxy Tab 8.9 Android Development] filipe_m:
After a clean installation i still with both problems: Keyborad (easily solved) and Wi Fi connection
[Galaxy Tab 8.9 Android Development] L3R0N:
Omni is back

Hey guys I bought myself a new computer after I gave away those I had to charity. This means that I will resume porting Omni from the p4/p4wifi over to our Tab. I'm currently having some issues with jolinnard's latest kernel and so I won't port until it works on my device. I will not post any untested port here.
[Galaxy Tab 8.9 Android Development] L3R0N:
Hey guys I've got a new build for Omni. It uses [MENTION=2002216]jolinnard[/MENTION]s latest figue kernel and so I've labeled it as experimental. Reason being that some users of his latest kernel have had success using it (....well most users have) but there are a few, me included, who have had problems with it. Now I have tested the ROM and it does boot except with the issues I reported in his thread besides these issues it works ok as far as I could test. I strongly recommend you make a TWRP backup before flashing this build. In case you do not wish to make a complete backup you can simply use a root explorer file manager to copy system/lib/modules to your sdcard then reboot to recovery and backup only the boot partition. In case your device does not boot after flashing this build then simply restore the boot image backup you made earlier and you should be fine. When it boots use a root file manager to copy the modules from your sdcard back to system/lib/modules (overwrite the existing ones in the folder) these are needed for things like WiFi to work.

You may find the new build here or check the OP.

PS. please don't flash and remain silent. Do come back to share your experience be it good or bad. :laugh:
[Galaxy Tab 8.9 Android Development] Huigie:
This is for p4wifi error when installing...
[Galaxy Tab 8.9 Android Development] L3R0N:
Sorry about that I forgot to delete the assert lines in updater script. Will fix tomorrow. Meanwhile you can fix your downloaded copy by opening the updater-script with Notepad++ and deleting the first two lines in the file. Save, close and put the updater-script back into the zip and flash. It should now work fine.
[Galaxy Tab 8.9 Android Development] hewhomustnotbenamed:
Have u changed the build now? or do we need to do it ourselves?

can we use tk gapps with this ROM on tab 8.9?

or are the gapps mentioned in the OP are the only ones compatible with tab 8.9
[Galaxy Tab 8.9 Android Development] L3R0N:
I'm sorry but I haven't changed it yet. I've been very busy with school lately. As you may have seen from some of my previous posts my country was hit by a storm and as a result my school remained closed for a month so now we have to work twice as hard to make up for the lost time. For now you'll need to change it by yourself.
[Galaxy Tab 8.9 Android Development] L3R0N:
Discontinued permanently

Hey guys I've chosen to discontinue this port permanently. I'm very busy with school lately. Besides, we've got a working AOSP ROM from [MENTION=2002216]jolinnard[/MENTION] and I think its best if we all focus what little developer knowledge we have on making his port the best for our tab. So in this light I will not be uploading any more ROMs or updates here. What I'll do is fix the updater script in the last build I posted and that's that. If you run into problems then post them here but there will be no more updates.

Thanks to all who tried this ROM it was great having you. :good:

Regards

L3R0N
[Galaxy Tab 8.9 Android Development] Neyazy:
wifi

I have same problem
[Galaxy Tab 8.9 Android Development] fedtemis:
Link to revised version

I took the liberty of removing the proposed lines from the updater script, as suggested by OP.

Flashed it yesterday with Gapps and supersu, and may I say, it works flawlessly.

Link to file with lines removed:

https://www.sendspace.com/file/dh45ij

Sory for sendspace link. If it dies. Please let me know. I'm keeping a copy.
[Galaxy Tab 8.9 Android Development] karli12:
it dies
[Galaxy S 4 General] bobbythomas:
Hi Devs,

I know we all are busy people and it's not different for you guys. But you guys try to spend some time to work on this wonderful phone development and provide some good ROMS, So why don't all of the Developers unite and be part of a whatsapp group? I am not a Dev, but I would really appreciate if you guys could join my whatsapp group. Please PM me if you are interested or kindly let me know if there are any whatsapp groups?

Thank you,

Regards,

Bobby.
[Galaxy S 4 General] Perseus:
This is Considered as an advertizement. XDA as a forum is intended for the Developers to share Ideas, Brainstorm and collaborate.
[AT&T HTC One (M8)] justine_d:
I got this device from AT&T last year. I went to htc-dev to unlock the bootloader, then I installed CyanogenMod. It hasn't been without problems but I have been relatively happy. However, to upgrade to the latest CM12, I need to update the bootloader. The most reliable way to do that is to return to stock and do the OTA.

I want to return my device to stock temporarily. I've looked through the forums and it seems like it should be possible. There are RUU available, but only for certain CIDs (not mine). The other option is to use a Nandroid backup. Apparently these are touchy. It's best to have your own (I don't), because you have to match the proper versioning or else you might have a brick. I went to check my phone information with

fastboot getvar all

and the result was strange compared to what I have seen elsewhere:

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [[B]redacted[/B]]
(bootloader) imei: [[B]redacted[/B]]
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.006s

The all-important "version-main" is missing, and the baseband-version is marked invalid. I'm not really sure where to go from here. I really want to update the bootloader so that I can get the next CyanogenMod build. (It fails to install with a complaint about the bootloader version. It wants 3.18 or 3.19, while I have 3.16.

I don't really know where to go or what to do now. Advice?

(Finally, I have a custom recovery [Team Win]. My phone is currently S-On)
[AT&T HTC One (M8)] redpoint73:
Not sure where you've been looking, or why you think that. But RUUs are readily available for the AT&T version for every software version since release. And one of the few M8 versions that has consistently had RUUs. AT&T RUUs are listed on my Index tread, sticky at the top of the General AT&T forum section: http://xdaforums.com/showthread.php?t=2751432

Your hboot number corresponds to software 1.xx, but it might be 1.12 (less common) or 1.58 (probably).

Restoring to stock using a nandroid is an option, but IMO more complicated than RUU. You will need to restore the stock nandroid, stock recovery, then OTA twice (to software 3.x then 4.x) in order to make your firmware (including hboot) current. Then flash TWRP and flash CM12.

For the RUU route, you will need to relock the bootloader, RUU, then unlock the bootloader (go through the HTCDev.com process) again. Then flash TWRP and CM12. But the downside to RUU is that it will wipe the phone, but that might not be much of an issue if you are a ROM flasher.
[AT&T HTC One (M8)] justine_d:
Oh, I must have been looking in the wrong place. Somehow I found myself on the other (non-AT&T specific) index.

Wiping the phone is not an issue for me.. So then, I just pick one (I'm leaning toward 1.58 bootable RUU) and flash it, and that's it. I think I can figure it out. Does it matter which one I pick? Anything else I should know?

Thank you!
[AT&T HTC One (M8)] justine_d:
Just checking in to say that everything worked perfectly, I am in the process of taking OTA updates now.
[AT&T HTC One (M8)] redpoint73:
I know you've already got it sorted out. But just for your info:

The only restriction on RUUs (in addition to the fact that they need to match your phone's CID and MID) is that with s-on, you cannot run an RUU that is an

earlier

version than is on the phone (hboot, OS number), meaning you cannot "downgrade". Seeing as you had either version 1.12 or (probably) 1.58; and the only 1.x version RUU released was 1.58, any AT&T RUU would work in your case.

This also means that any

equal or greater

version AT&T RUU will work. Meaning with RUUs you can even have just skipped up to the latest Lollipop RUU (software 4.28) without running any "intermediate" RUUs or OTA updating up to LP. I would have pointed this out earlier, but I wasn't sure which method (RUU versus OTA) you preferred to use.

RUUs are in contrast to OTAs, which normally need to be installed in sequence.
[AT&T HTC One (M8)] justine_d:
Thanks for clearing that up. There was definitely some underlying confusion on my part. In essence, there was no reason to flash the earliest RUU and then install the OTAs, when instead I could have flashed the latest RUU and achieved an equivalent result. Oh well, no harm (and I learned something).

I wish phones were as simple as PCs. Or rather, that phones were as difficult to screw up as PCs.

As an aside, do you have any personal favorite OS to flash to the M8?
[AT&T HTC One (M8)] redpoint73:
Very true. And in regards to doing OTAs

or

RUUs, you now know how to do both! :o

That's always a tough one. Its so personal. Some folks like AOSP or GPE, while some prefer Sense. Folks are looking for different features (customization, performance, etc.).

Personally, I'm not an AOSP/GPE person at all, and actually like Sense. And tend towards pretty stock ROMs, with maybe a few added customizations and performance tweaks, but otherwise pretty clean ROMs. I was on the stock Dev Edition Sense ROM for a while, than more recently SkyDragon Sense (so I could use Sense 7) and then LeeDroid.

That probably doesn't help you much , as it appears you may be more of an AOSP fan. You might check out the GPE ROMs, if you haven't already. IGPE is closer to stock Android than Sense, but should be more stable and bug-free than CM12, since its based on official HTC software.
[AT&T HTC One (M8)] justine_d:
Thanks for your input :) after I thought I was done, I managed to break it, fix it, break it again, and so on. I ran into a problem with receiving calls on CyanogenMod so I flashed back to Sense. I decided to shell $2.5 x 10**1 out for Sunshine S-OFF so that I could restore to any software with the RUUs. Then I just kept chasing the rabbit down the hole: SuperCID and Dev Edition. Then I tried a highly modded ROM (Viper One) to see what it had to offer. Finally I flashed back to CynogenMod because I've used it so long it feels most like home. The incoming call problem is absent in the Dev Edition radio firmware (but I've had to contend with other bugs in the past, only steady use will tell if things have gotten better or worse).

I definitely prefer the more stock feeling. The HTC Dev Edition Sense ROM was by far my favorite over either Viper One or the bloated AT&T stock software. I haven't tried any other AOSP based OS. The first time around I was content to HTCDev unlock and flash CM. I didn't even wait a week; I picked this device because I knew it was unlockable.
[AT&T HTC One (M8)] redpoint73:
Then you really should check out the stock Google Play Edition (GPE) ROM or a custom GPE based ROM. GPE is supposed to be a AOSP type experience, no Sense and basically like a Nexus ROM. But its official HTC software, so should be pretty bug-free in comparison to CM12. Not to knock CM12 (I love it on my Samsung Tab Pro 8.4), but I know its had its share of bugs on the M8 (at least from my understanding).
[Mi 3 Q&A, Help & Troubleshooting] mkp52mkp:
is it possible to get double tap to wake on mi3 n mi4?? any kernel for that??
[Mi 3 Q&A, Help & Troubleshooting] xshinichix:
me too. i was hoping to have this feature on our phones
[Mi 3 Q&A, Help & Troubleshooting] Aka9413:
Its not available for Mi3w now as still the kernel sources are not fully out so devs are unable to add it
[Mi 3 Q&A, Help & Troubleshooting] TiwitAnoid:
I have that thro wsm tools and a xspoed module doubletap2sleep
[Mi 3 Q&A, Help & Troubleshooting] kruga:
That different. Double tap to wake would be a very welcome addition!
[Mi 3 Q&A, Help & Troubleshooting] nuwanmw1988:
I would love to have that in my mi3 too
[Mi 3 Q&A, Help & Troubleshooting] smh.saad:
really any explain ! ? i thought i was all out ?
[Mi 3 Q&A, Help & Troubleshooting] bluethilak:
Kernel sources have been released long back https://github.com/MiCode/Xiaomi_Kernel_OpenSource
[Mi 3 Q&A, Help & Troubleshooting] TheDGITA:
It can be implemented but its very hard do it because the hw is not compatible , the dev speak about it long time ago
[Mi 3 Q&A, Help & Troubleshooting] narugan26:
Try stuntnex kernel or zeurion ;)
[Mi 3 Q&A, Help & Troubleshooting] vivekmishra:
What about tun.ko ?

So we can use data compression apps like opera max?
[Mi 3 Q&A, Help & Troubleshooting] shauyan:
Forget it, it is not supported on Mi3, at least at the moment
[Mi 3 Q&A, Help & Troubleshooting] h4cker90:
WTF guys, flash moshi kernal. It has dt2w. Using it since a month! Works like a charm, but eats battery a bit.
[Mi 3 Q&A, Help & Troubleshooting] lokjianming:
Kernel sources are out but I don't think developers are working on that.
[Galaxy S 5 Q&A, Help & Troubleshooting] adrianoredator:
Hey, all.

I've been reading tons of threads in order to get some fix for this.

Can't downgrade my G900P (bod3) to Kit Kat 4.4.2 NE5.

Odin gives me this error:

<ID:0/004> NAND Write Start!!

<ID:0/004> FAIL! (Auth)

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

As far as I know, the bootloader is blocked.

Does anyone know a way to get it done? Is it possible already?

Thanks in advance.
[Galaxy S 5 Q&A, Help & Troubleshooting] yakiqua:
Starting with BOD3 update u cant downgrade anymore with odin ....

First make a back-up, especially to EFS

Solution :

1 Install custom recovery ...philz in attachement

2. Download Galaxy S5 Rooted Stock ROMs from here http://galaxys5root.com/galaxy-s5-rooted-stock-roms/ and Kernel(ZIP) from here https://www.androidfilehost.com/?w=files&flid=22599 and put the zips on ur SD card

3. Reboot to recovery ...wipe data/cache/dalvik.....install kernel and rom

4. Reboot to system and ur downgrade :)

thanks to bto001 here: http://xdaforums.com/sprint-galaxy-s5/general/solution-to-sim-unlock-od3-downgrade-t3128120
[Galaxy S 5 Q&A, Help & Troubleshooting] adrianoredator:
Thank you so much for this!
[Galaxy S 5 Q&A, Help & Troubleshooting] adrianoredator:
I've managed to flash the kernel and rom, then unlock the system.

But my phone wouldn't get phone signal or internet. I've then flash ShoHat rom and now I'm able to get signal and to find my carrier, but can't register on the network.

Any help on this, buddy? Where should I go from here?
[Galaxy S 5 Q&A, Help & Troubleshooting] dork997:
Is this for 900p only or is downgrading banned on 900f aswell?
[Galaxy S 5 Q&A, Help & Troubleshooting] adrianoredator:
I think it depends on your baseband, not on your phone model.

Newer firmwares have locked bootloaders, from what I've seen.
[Galaxy S 5 Q&A, Help & Troubleshooting] yakiqua:
Do i still have an imei?

This happens sometime (quite often) when u unlock a samsung phone...

u need to flash some certificates to get back the signal.....for this it is necessary a box, which u'll find at a service

Another method is to restore EFS from a backup.
[Galaxy S 5 Q&A, Help & Troubleshooting] yakiqua:
I have encountered this problem only on G900P od3 fw so far
[Galaxy S 5 Q&A, Help & Troubleshooting] adrianoredator:
I have my IMEI, still.

Damn, I've seen some websites about this, but it seems rather difficult to get it done at home.

I'll find somewhere to get this done. Anyway, thank you very much for you help, my friend.
[Galaxy S 5 Q&A, Help & Troubleshooting] yakiqua:
It is on the challenging side to do it at home... Good luck!
[Galaxy S6 Q&A, Help & Troubleshooting] Dunams:
I'm just wondering, is it expected that there will be some root method that supports 5.1.1 without tripping knox in the future?

I mean knox is not something new, do the older devices have something of that sort?

Or "ping-pong root" was just one exploit that only supported 5.0 and that's it?

It pisses me off that I'll lose my warranty if I'll root the phone, I don't understand why does unlocking the software of my device has to do with manufacture hardware defects, mainly because the stock firmware and kernel by Samsung suck as always.
[Galaxy S6 Q&A, Help & Troubleshooting] Dunams:
I meant to post this in the Q&A forum, can a mod please move it?
[Galaxy S6 Q&A, Help & Troubleshooting] cpfeifer:
There was a exploit found in the ping sockets in 5.0 kernel before March 5th. No body has found one for 5.1.1 yet. Without a exploit to get around the SElinux enforcing on our stock kernels you'd have to flash a recovery or custom kernel, both tripping Knox
[Galaxy S6 Q&A, Help & Troubleshooting] Dunams:
So the s5 and the s4 devices which afaik also have KNOX, what you said applies to them as well?

This is annoying.