Develop Bugs

2.3.4 Gingerbread for the Sprint Tab [CDMA][DEV-FILES]

For those of you that want to get in on early GB development but don't have the skill to compile it from source, I compiled the new source code that dropped for the gingerbread build for the Sprint Tab. This is NOT an installable rom. This is a zip containing the compiled AOSP kernel and system, purely for research/development purposes. Download, unzip and play. I doubt this will boot on a CDMA device without the proper bootloaders, but you're welcome to try. You can even develop AOSP roms from it that will probably run on your tab after the update on the 5th. Enjoy.
Download​

Hope someone comes up with a great rom be it asop or other. Im truly looking for great things to come out of this.
Sent from my GT-P1000 using XDA Premium App

im expecting alot from these files!!!
a working 2.3 rom means the following for cdma tabs:
1.working skype video calls!
2.Working hulu!
3. Last but not least, Working Netflix!
it would make the tablet experience so much better for us CDMA owners.
i want to be the first to make a bug list on the first dev to release a rom
it would be a honor
and glad to see you finally posting something space. you have been in hiding so long, you rival osama lol

Argh, I wish I knew how to build roms >:|

kabuk1 said:
Argh, I wish I knew how to build roms >:|
Click to expand...
Click to collapse
im going to start reading this ebook i got.
its called:
learn android application development in 24 hours.
hopefully that would at least wet my feet.

man if I had broadband id have atempted to merge these into my cyanogen repo and make a build
Sent from my SCH-I800 using XDA App

wolfie083188 said:
im going to start reading this ebook i got.
its called:
learn android application development in 24 hours.
hopefully that would at least wet my feet.
Click to expand...
Click to collapse
For real? If so where can I get it.!?!?
EDIT : found it
Sent From My Evo using nanotechnology and incense!

has anyone tried just installing the kernel? anyone tried overwriting the last cdma cm7 build's system with this? anyone tried both? I'm going to see if I can get my hands on some internet soon but I might have me a date
Sent from my SCH-I800 using XDA App

Obama's>god said:
has anyone tried just installing the kernel? anyone tried overwriting the last cdma cm7 build's system with this? anyone tried both? I'm going to see if I can get my hands on some internet soon but I might have me a date
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
I guess I should add: you'll need the driver libs to get this running... you'll have to gank what you can from the gsm GB build. Stuff in /system/lib/hw and /system/lib/egl and so on. Just compare and you will get the idea.

spacemoose1 said:
For those of you that want to get in on early GB development but don't have the skill to compile it from source, I compiled the new source code that dropped for the gingerbread build for the Sprint Tab. This is NOT an installable rom. This is a zip containing the compiled AOSP kernel and system, purely for research/development purposes. Download, unzip and play. I doubt this will boot on a CDMA device without the proper bootloaders, but you're welcome to try. You can even develop AOSP roms from it that will probably run on your tab after the update on the 5th. Enjoy.
Download​
Click to expand...
Click to collapse
Thanks! This is useful. I am merging the CDMA kernel sources with GSM right now and the PowerVR module is updated so it looks like I will have to switch to newer OpenGL driver from this archive.

Technomancer said:
Thanks! This is useful. I am merging the CDMA kernel sources with GSM right now and the PowerVR module is updated so it looks like I will have to switch to newer OpenGL driver from this archive.
Click to expand...
Click to collapse
I hope it's useful. Sadly, the proprietary files weren't included in the source, so of course you'll have to patchwork from other builds or wait until the official release for some of those.
You're welcome though, glad to be of service.

spacemoose1 said:
I hope it's useful. Sadly, the proprietary files weren't included in the source, so of course you'll have to patchwork from other builds or wait until the official release for some of those.
You're welcome though, glad to be of service.
Click to expand...
Click to collapse
Yeah, I just noticed that, no EGL, etc. Maybe they put this stuff in /vendor now?

I just redid my Tab. I'm ready for Gingerbread on this *****.

It seems OTA may be pushed to some users now. Anyone care to rip all the files in /system and post them?
-d

technomancer
as soon as I get my update i'll help you out, just let me know how to rip my system, hell if i could dump my whole g-tab into an installable rom i would... still waiting on the push update, 7:02 PM EST, still no update! might be tomorrow!

x4gvnferdy said:
as soon as I get my update i'll help you out, just let me know how to rip my system, hell if i could dump my whole g-tab into an installable rom i would... still waiting on the push update, 7:02 PM EST, still no update! might be tomorrow!
Click to expand...
Click to collapse
Open adb shell and run this:
tar -czvf /mnt/sdcard/system_dump.tar.gz /system/
it will create file system_dump.tar.gz in on your sdcard with the contents of your factoryfs (system) partition.

alright! So when my update comes i will do just that and put it on my dropbox, providing you a download link!

Technomancer said:
Open adb shell and run this:
tar -czvf /mnt/sdcard/system_dump.tar.gz /system/
it will create file system_dump.tar.gz in on your sdcard with the contents of your factoryfs (system) partition.
Click to expand...
Click to collapse
Would the .zip update file help? I've got that posted on mediafire (as i just a little bit ago got the notice for an update. If it'll help, here's the link.
http://www.mediafire.com/?cngx5e67dgbq04y
Otherwise i'll get the update installed and see about running the sys dump as well.

pvtjoker42 said:
Would the .zip update file help? I've got that posted on mediafire (as i just a little bit ago got the notice for an update. If it'll help, here's the link.
http://www.mediafire.com/?cngx5e67dgbq04y
Otherwise i'll get the update installed and see about running the sys dump as well.
Click to expand...
Click to collapse
has anyone tested this? i don't wanna brick my tab!

I've got it up and running on my tab and there's at least 1 other person from this thread http://forum.xda-developers.com/showthread.php?t=1148447 that has it up and running as well.. Odin'd back to stock EA24, did the OTA EB28, and then ran the update.zip from stock recovery. All is happy on my tab. Now I just have to wait till i'm at work tomorrow to get ADB to work, and I'll dump /system.

[NS4G-D720][ROM] Stock 4.0.4/IMM76D DEODEX (Error-Free Decompiling)

Contents:
Android 4.0.4/IMM76D deodexed ROM in flashable ZIP format. Will not produce errors when decompiling APK/JAR files.
Includes Superuser and boot.img root-level access. Does not include radio or recovery.
Changelog:
[R1/02APR2012]: ROM base changed from 4.0.4/IMM26 to 4.0.4/IMM76D. Files updated from stock IMM76D listed below.
Updated File List:
system/app/GoogleEarth.apk (v.6.2.1.6363 :: Earth)
system/app/googlevoice.apk (v.0.4.2.54 :: Voice)
system/app/Maps.apk (v.6.5.0 :: Maps)
system/app/Phonesky.apk (v.3.5.15 :: Play Store)
system/app/Wallet.apk (v.1.1-R57v4 :: Wallet)
system/lib/libearthmobile.so
Notes:
The need to wipe data beforehand is dependent on which ROM you're already using, but is advisable when possible for the sake of simplicity.
[R1] http://www.mediafire.com/file/48w84r8v3qbb8bw/NS4G-4.0.4-IMM76D-DEODEX-R1.zip

So does this mean the SystemUI in this version is able to decompile without errors? If so how exactly did you do this?
Thanks.

ssconceptz said:
So does this mean the SystemUI in this version is able to decompile without errors? If so how exactly did you do this?
Thanks.
Click to expand...
Click to collapse
I used smali and allowed each APK to reference all of the .odex files in the framework, added the classes.dex files to their respective APKs, and zipaligned. I don't know if it matters, but I did those steps through the command line, although I'm sure the process would be a lot faster with a script. If you would like the exact line-by-line process that I used, let me know.

So how is this Rom & all I have to do is download & flash it or is there another step to do?
Sent from my Nexus S 4G using xda premium

Killasmoke said:
So how is this Rom & all I have to do is download & flash it or is there another step to do?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
The procedures are the same as for other ZIP-based ROMs: download, transfer to phone, and flash through recovery. You may or may not need to erase your data (depending on which ROM you're coming from), but backing up your data beforehand is advisable and never hurts.
I haven't received any feedback regarding this specific ROM yet (I don't know if that's a good or bad sign). The main difference is that it's deodexed and will decompile without errors. I'm sure there are other threads with more in-depth information on IMM26 changes/improvements/issues.

SuperUser
I was impressed with this rom for the first few minutes I used it. But then I found out that my SuperUser app wasn't working. I tried updating the binaries through the app itself but it couldn't gain root access. I downloaded the file again and flashed it again but SuperUser still didn't work. It was the same problem with not gaining root access. So I flash the SuperUser zip file from zedomax's tutorial on rooting the Nexus S 4G and I was able to gain root access. Just thought I'd tell you.

mvilla, how did you fix the superuser root access problem? i am having the same problem when i try to update binary, and im getting permission error when i try to flash recovery in rom manager, i think is because of superuser not working.

I went to nexusshacks.com and downloaded the nexussrootICS.zip file (I think that's what its called). There's a SuperUser.zip file within that zip file. I moved the file to my phone and flashed it in recovery (wipe cache and dalvik cache of course). And its working well.
Sent from my Nexus S 4G using XDA App

mvilla8 said:
I was impressed with this rom for the first few minutes I used it. But then I found out that my SuperUser app wasn't working. I tried updating the binaries through the app itself but it couldn't gain root access. I downloaded the file again and flashed it again but SuperUser still didn't work. It was the same problem with not gaining root access. So I flash the SuperUser zip file from zedomax's tutorial on rooting the Nexus S 4G and I was able to gain root access. Just thought I'd tell you.
Click to expand...
Click to collapse
Thanks for bringing that to my attention. Uploaded an updated version in the OP that addresses the Superuser issue. Sorry for the inconvenience.
satuday said:
mvilla, how did you fix the superuser root access problem? i am having the same problem when i try to update binary, and im getting permission error when i try to flash recovery in rom manager, i think is because of superuser not working.
Click to expand...
Click to collapse
This update is from ChainsDD's site and has the latest Superuser app and binary. Should accomplish the same thing.

XK72 said:
I used smali and allowed each APK to reference all of the .odex files in the framework, added the classes.dex files to their respective APKs, and zipaligned. I don't know if it matters, but I did those steps through the command line, although I'm sure the process would be a lot faster with a script. If you would like the exact line-by-line process that I used, let me know.
Click to expand...
Click to collapse
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?

sniperkill said:
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
Click to expand...
Click to collapse
Did you ever get that step-by-step process for deodexing ICS from the OP? If so, can you send it to me?

I guess the Google Apps are included?

Will there be any further updates to this in the near future, or has this reached the end of the line so-to-speak? Just curious because I like having the natural AOSP of this.

Been using this since the 9th and I have to say it's very smooth. Very stock too, which obviously is what it's supposed to be. Just saying that for anyone who comes in looking for something customized. This is basically pure vanilla ICS.

Sorry for the delayed replies. I've been hammered by other obligations lately.
sniperkill said:
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
Click to expand...
Click to collapse
mabry said:
Did you ever get that step-by-step process for deodexing ICS from the OP? If so, can you send it to me?
Click to expand...
Click to collapse
I'll try my best to post the steps later today or tomorrow. Sorry to keep you waiting.
akabadnews said:
I guess the Google Apps are included?
Click to expand...
Click to collapse
The stock Google apps are included. There are now two choices: One has the apps that were included in the IMM26 release (R3) and I have also included the latest app updates and related binary files as (R4).
The Batman said:
Will there be any further updates to this in the near future, or has this reached the end of the line so-to-speak? Just curious because I like having the natural AOSP of this.
Click to expand...
Click to collapse
I have replaced the Google apps that have been updated since the IMM26 release. There are rumblings that the official ICS ROM should be released sometime soon. I'm not holding my breath, but I'll offer the same thing to that release once it comes out.
If you're asking about adding functionality or features, I don't think I'd have anything unique to offer since there are so many other ROMs and customizable updates out already. I have considered including FaceLock functionality, but it adds quite a bit of size to the ROM and honestly, it hasn't worked very well for me. If there is enough interest, I'll include it as a separate revision in the future.

I'm getting a error for the media fire links. New link please?
Sent from my Nexus S 4G using xda premium

xamadeix said:
I'm getting a error for the media fire links. New link please?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Sorry about that. I don't know what happened there. Link fixed.

XK72 said:
Sorry about that. I don't know what happened there. Link fixed.
Click to expand...
Click to collapse
Thank you
Sent from my Nexus S 4G using xda premium

Does anyone have problems turning Bluetooth on?
Sent from my Nexus S 4G using Tapatalk

XK72 said:
I have replaced the Google apps that have been updated since the IMM26 release. There are rumblings that the official ICS ROM should be released sometime soon. I'm not holding my breath, but I'll offer the same thing to that release once it comes out.
If you're asking about adding functionality or features, I don't think I'd have anything unique to offer since there are so many other ROMs and customizable updates out already. I have considered including FaceLock functionality, but it adds quite a bit of size to the ROM and honestly, it hasn't worked very well for me. If there is enough interest, I'll include it as a separate revision in the future.
Click to expand...
Click to collapse
I would rather have the straight vanilla experience. Thanks for responding.
Edit: Also, touch to focus would be nice for the camera if at all possible. Thanks.

Hint: AOSP 4.1.1 source and Toro not showing as a target under 'lunch'

In case anyone is having trouble finding toro as a device target when trying to build from the list of targets from the 'lunch' command... Toro didn't show up in the list but I was able to manually specify it rather than selecting a numeric option.
Devs probably know that works, but amateurs like myself might benefit from that tidbit. Jellybean seems to be building OK for me now.
EDIT: I was asked what I did, more specifically, so I'll put that here in op:
Rather than enter a numeric choice, I entered 'full_toro-userdebug'. Apparently this was a valid response and the build proceeded.

Mind explaining how you manually selected it?

keith.mcintyre26 said:
Mind explaining how you manually selected it?
Click to expand...
Click to collapse
Not at all. Rather than selecting say, 11 or another choice, I entered: full_toro-userdebug. Apparently this was a valid response and the build proceeded.

question... not much into actual developing here but i know my way around the inside of a rom or two... once you compile. will it be a fully capable rom? as in (what the OTA will be like without VZ apps)?

spunks3 said:
question... not much into actual developing here but i know my way around the inside of a rom or two... once you compile. will it be a fully capable rom? as in (what the OTA will be like without VZ apps)?
Click to expand...
Click to collapse
It's not as 'polished'. There are no gapps, the dictionary is not complete (need a version from a factory image/rom), there are extra keyboards (Japanese?), maybe a couple other oddities as compared to a stock ROM. It will certainly be more capable that porting a gsm rom to toro, that's for sure .

mmuzzy said:
Not at all. Rather than selecting say, 11 or another choice, I entered: full_toro-userdebug. Apparently this was a valid response and the build proceeded.
Click to expand...
Click to collapse
I did that right after I asked haha. Building now. Thank you.
Sent from my Galaxy Nexus using xda premium

keith.mcintyre26 said:
I did that right after I asked haha. Building now. Thank you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You're very welcome. Happy flashing.

I thought you meant the whole system. I was wondering where you got the jellybean source
Sent from my Galaxy Nexus using Tapatalk 2

phydo said:
I thought you meant the whole system. I was wondering where you got the jellybean source
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Google released it into the wild today:
https://groups.google.com/forum/?fromgroups#!topic/android-building/XBYeD-bhk1o

mmuzzy said:
Google released it into the wild today:
https://groups.google.com/forum/?fromgroups#!topic/android-building/XBYeD-bhk1o
Click to expand...
Click to collapse
Haha uhh.. I did realize that about two minutes ago. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2

phydo said:
Haha uhh.. I did realize that about two minutes ago. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was actually trying to pull it before Google was finished so it hasn't been that long.

Hey can you help me out? Is your android version showing as 4.0.9.99.999.9999.99999? Wth?

anton2009 said:
Hey can you help me out? Is your android version showing as 4.0.9.99.999.9999.99999? Wth?
Click to expand...
Click to collapse
Lol!
Sent from my Galaxy Nexus using Tapatalk 2

phydo said:
Lol!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well... I figured out why it was showing like that; because I was syncing the master branch and not the 4.1.1 branch. But I'm still confused on this

Not to thread jack, but i have my rom building, but to actually personalize the rom, is there any app like eclipse or is it just editing files in the zip?

cdrshm said:
Not to thread jack, but i have my rom building, but to actually personalize the rom, is there any app like eclipse or is it just editing files in the zip?
Click to expand...
Click to collapse
You edit the source files. The goodies you want are in the res folder of most applications. /packages/apps in the source code. Here's my question, when I boot it gets to the Google screen and then a black screen. I suspect this here. When I start the build I see this:
Code:
find: 'src': No such file or directory.
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
... Many more of these Product copy ignored things...
And then it finishes compiling. What's up here, I'm pretty sure it's missing drivers and stuff!

CPCookieMan said:
You edit the source files. The goodies you want are in the res folder of most applications. /packages/apps in the source code. Here's my question, when I boot it gets to the Google screen and then a black screen. I suspect this here. When I start the build I see this:
Code:
find: 'src': No such file or directory.
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
... Many more of these Product copy ignored things...
And then it finishes compiling. What's up here, I'm pretty sure it's missing drivers and stuff!
Click to expand...
Click to collapse
Did you install the binaries for toro? There is also a script that will pull them from your phone (so a stock rom is best), which may be better because Google can't give you everything you need for a functional rom (GPS for example). I ended up copying those files from a stock image to my compiled rom.

i got my binaries from here https://developers.google.com/android/nexus/drivers#torojro03c
mwalt2 said:
Did you install the binaries for toro? There is also a script that will pull them from your phone (so a stock rom is best), which may be better because Google can't give you everything you need for a functional rom (GPS for example). I ended up copying those files from a stock image to my compiled rom.
Click to expand...
Click to collapse

cdrshm said:
i got my binaries from here https://developers.google.com/android/nexus/drivers#torojro03c
Click to expand...
Click to collapse
For future reference, what he's referring to is the extract-files.sh script included in the CM source. If you cannot find the proprietary binaries for a certain device you wanna build for, plug in the phone via usb, cd to the directory with the script and execute the command.

anton2009 said:
Well... I figured out why it was showing like that; because I was syncing the master branch and not the 4.1.1 branch. But I'm still confused on this
Click to expand...
Click to collapse
I also got version 4.0.9.99.999.9999.99999 when I synced to the master branch. Thanks for mentioning the workaround to sync with 4.1.1_r1 .
Did you figure out if it's a problem to sync 4.1.1 into a directory that's already synced with master (4.0.9.99...)?
--------------------------------
Update: I think I can answer this question based on JBQ's response:
https://groups.google.com/d/msg/android-building/rtH5ZbJC7qU/-N1lr9MqexYJ
"You can also switch in place: just run "repo init -b <new_manifest_branch>; repo sync" in your existing client."
Sounds like syncing to a new branch in the same working directory should work just fine.

[CLOSED] Beta Android 4.3 US & CAN | Deodex & Odex | Now Rooted

READ THIS ENTIRE POST PLEASE​
PLEASE PROCEED TO USE THE 4.3 VERSION LOCATED Android 4.3 JWR66V
UPDATED ROM IS MUCH MORE STABLE AND BATTERY LIFE IS GREAT.
Thanks to everyone for testing/using this one until now
This ROM comes from I9505 variant.
Luckily the only thing you will need to do is apply Loki patch if you require it for other ROMS.
If you are a CAN variant you can simply install the ROM with no other issues or steps.
IMPORTANT
User reports suggest that battery life is much better as well as working google wallet in the odex version, root should work for both.
Google Play 4.1.10 : Please manually update Google Play to prevent gps/maps battery drain, download apk and install as usual
There are two FactoryKeystring.apk's included and actively used by Android System, one is hidden and one is in System/app, removing one seems to improve battery life (must have root)
Do NOT change Dpi you will loose root and you will loose wifi. You have been warned.
WARNING
As always, i'm not responsible for your phone blowing up or bricking. Hell this is completely pre-release software that Google hasn't even published yet so you better be sure you're ready to take the plunge and accept that anything can happen and i assume no responsibility. this is all your choice.
System Details
Android version: 4.3
Build ID: JWR66N
PDA: I9505GUEUBMFP
CSC: I9505GXARBMFP
Build Date: 26 June 2013
Changelist: 968842
DOWNLOADS
Odexed & DevHost Mirror
Deodexed & DevHost Mirror
--
LokiDoki Only for U/S variants - CAN variants do not download.
Chainfires Root Guide When doing this please flash full rom and let boot then reboot back to recovery and install this zip
HOW TO FOR CAN VARIANTS
1. Copy ROM (Odex or Deodex) to your internal SD Card
2. Enter Recovery (Power + Volume Up + Home)
3. Do a Wipe/Factory Reset (Necessary due to new Android version)
4. Flash ROM
5. Reboot your device!
HOW TO FOR US VARIANTS
1. Copy ROM (Odex or Deodex) to your internal SD Card
2. Enter Recovery (Power + Volume Up + Home)
3. Do a Wipe/Factory Reset (Necessary due to new Android version)
4. Flash ROM
5. Flash LokiDoki don't rely on a recovery with auto loki
5. Reboot your device!
SCREENSHOTS
SAMmobile page linked here has screen shots. Its stock AOSP not TW
BENCHMARKS
Antutu // Quadrant \\ 3DS Max
Moved to bottom in attachments to reduce OP size
APPS THAT HAVE ISSUES
1. Apex will FC - Solution, use Nova Launcher or various other ones.
2. DashClock will not work at all.
3. CNN App, Live TV - lets you sign in but when attempting to play a video it gives "this video is not available" error.
4. Tapatalk has been reported to have issues, works fine for me. Test yourself.
5. Titanium Backup seems to be having issues restoring.
EXTRAS || PROBLEMS || BUGS
1. Root Chainfires Root Guide
2. IR Works, Install WatchON if you want
3. Charging is SLOW at first, please give ROM about a day to settle and it will be fine.
4. Battery may also drain faster then normal at first, again please give ROM time to settle.
5. Stock Camera - If you start the camera for the first time, you may get a black screen. close it and wait a minute. Reopen and it will work.
6. Wallet works on Odex, have had mixed reports with Deodex
7. Continue to post feed back about apps having issues so I can update here
WHATS DIFFERENT IN 4.3 FROM 4.2.2?
- Roboto font has been cleaned up see here
- "android.hardware.bluetooth_le" listed as a feature in the Android System Info app, suggesting Bluetooth Low Energy support is on-board in Android 4.3. This feature isn't listed on the Google edition GS4 review unit running Android 4.2.2
- Bluetooth tethering is present in the 4.3 ROM, while it's absent (bizarrely) in the 4.2.2-based GS4 GE unit.
- A new checkbox under Advanced Wifi settings allows Google's location service to scan for Wifi networks even when Wifi is turned off and not being used for wireless networking (likely part of Google's new approach to battery-friendly location services)
- Multiple options under "Monitoring > Profile GPU Rendering," as seen in this Google I/O video.
This lets you view a graphical representation of the time taken to generate a frame, and see whether you're hitting the 60 frames per second target or not. This should help devs create more buttery apps.
- New debug options for the new non-rectangular clipping feature. This is a new graphical capability for devs in Android API level 18.
- New option to "Use experimental WebView" (this likely changes the browsing engine used to handle websites within apps, but has yet to be confirmed.
- There is now a button that lets you "Revoke USB debugging authorization." This deletes the RSA key generated for USB debugging authorization from the phone itself, previously you had to do this from the computer side.
- Pressing menu in the phone app, lets you now add two-second pauses in your dialing string (denoted by a comma) or longer waits (denoted by a semicolon.)
- In the Settings of the phone app, you can now enable dial-pad autocomplete and change DTMF (dual-tone, multi-frequency) tone lengths.
- Of course there's the new camera app.
- Long, multi-word SSID names now wrap properly down to a second line in the quick-settings pulldown.
- When you take a screenshot and share it via email, the Subject field is automatically populated with the date and time of the shot.
Thanks to :
SAMmobile for posting Jelly Bean 4.3
A$$h4t for providing the LokiDoki link
mr_blanket fo providing a link to updated Google Play apk to fix some battery drain.
AndroidPolice : their article showing the Roboto font changes/clean up - Found here
AndroidCentral : For their hands on article describing some changes - found here
Chainfire for getting Root!

But you cant root this?

SysAdmNj said:
But you cant root this?
Click to expand...
Click to collapse
Not sure, haven't tried.
Make a NANDROID then download and install and try to root like you would anything, if it doesn't work then reboot in to recovery and restore your NANDROID.

Downloading now......

kylecore said:
Not sure, haven't tried.
Make a NANDROID then download and install and try to root like you would anything, if it doesn't work then reboot in to recovery and restore your NANDROID.
Click to expand...
Click to collapse
I already had the leak but havent tried it yet as I tried GE yesterday and it didnt go too well. Went back to Omega7, will try this as soon as I hear you can root.

Do we need the AOSP kernel or the Touchwiz kernel for the AT&T I-337?

oldblue910 said:
Do we need the AOSP kernel or the Touchwiz kernel for the AT&T I-337?
Click to expand...
Click to collapse
I was wrong.
Sent from my GT-I9505G using xda premium

oldblue910 said:
Do we need the AOSP kernel or the Touchwiz kernel for the AT&T I-337?
Click to expand...
Click to collapse
Please see the op where it says in the second sentence NOT to use a TW kernel, since this is stock AOSP you need an AOSP kernel.
clyon3 said:
TW..... Some say it won't boot and you will lose root.
Click to expand...
Click to collapse
Wrong, completely wrong. It will just need to be a pre-loki'd kernel (i've posted a link to one in the OP)
kylecore said:
Please find the correct kernel for your phone that is NOT a TW kernel in the various threads before attempting to flash.
Click to expand...
Click to collapse

kylecore said:
Please see the op where it says in the second sentence NOT to use a TW kernel, since this is stock AOSP you need an AOSP kernel.
Wrong, completely wrong. It will just need to be a pre-loki'd kernel (i've posted a link to one in the OP)
Click to expand...
Click to collapse
So an aosp att kernel would work?
Sent from my SGH-I337 using Tapatalk 2

Gonna attempt to port this to ATT S4
Sent from my SGH-I337 using Tapatalk 2

mrakifa said:
So an aosp att kernel would work?
Click to expand...
Click to collapse
Yes in fact try the one in the OP it links to a thread where the AOSP one is.
Anthony04x said:
Gonna attempt to port this to ATT S4
Click to expand...
Click to collapse
Theres nothing to port, just flash an ATT kernel of choice immediately after the rom and its fine.

kylecore said:
Yes in fact try the one in the OP it links to a thread where the AOSP one is.
Theres nothing to port, just flash an ATT kernel of choice immediately after the rom and its fine.
Click to expand...
Click to collapse
All you need is loki doki the stock kernel works wifi, camera, bluetooth and lte no need to flash any other kernels
Sent from my GT-I9505G using Tapatalk 2

mastergrillo said:
All you need is loki doki the stock kernel works wifi, camera, bluetooth and lte no need to flash any other kernels
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I can also verify this. LokiDoki makes the stock kernel work just fine.

Right then, downloaded ROM and AOSP kernel provided in OP. Wiped, flashed, wifi is a no go for me and same as camera, totally borked (black screen). LTE works...everything else seems to work.

mastergrillo said:
All you need is loki doki the stock kernel works wifi, camera, bluetooth and lte no need to flash any other kernels
Click to expand...
Click to collapse
oldblue910 said:
I can also verify this. LokiDoki makes the stock kernel work just fine.
Click to expand...
Click to collapse
Thanks, anyone have a link to the thread for that? I can update the OP for people.
I'm a CAN variant so i've never touched anything that even mentions Loki
TheSmokingAndroid said:
Right then, downloaded ROM and AOSP kernel provided in OP. Wiped, flashed, wifi is a no go for me and same as camera, totally borked (black screen). LTE works...everything else seems to work.
Click to expand...
Click to collapse
If you're on ATT see the above and use stock kernel

Those that installed it can you confirm that root works?
Sent from my SGH-I337 using xda premium

sabre31 said:
Those that installed it can you confirm that root works?
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
No root for this yet
Sent from my GT-I9505G using Tapatalk 2

sabre31 said:
Those that installed it can you confirm that root works?
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
I don't believe anyone has figured out root yet.
+1 on loki doki for ATT I337
Download loki-doki zip here: http://tau.shadowchild.nl/attn1/?p=483

A$$h4t said:
I don't believe anyone has figured out root yet.
+1 on loki doki for ATT I337
Download here: http://tau.shadowchild.nl/attn1/?p=483
Click to expand...
Click to collapse
does flashing it from the OUDHS Recovery work too? (it auto-lokis kernels)
and another question
for the google edition 4.2 I had to flash the Ktoon TW Kernel. Why AOSP for this one?
thanks!

jhong91 said:
does flashing it from the OUDHS Recovery work too? (it auto-lokis kernels)
and another question
for the google edition 4.2 I had to flash the Ktoon TW Kernel. Why AOSP for this one?
thanks!
Click to expand...
Click to collapse
Thats the recovery im using and it didnt do for me i had to use loki doki
Sent from my GT-I9505G using Tapatalk 2

[P9000 Lite] [ROM] [7.1.2]AOKP Nougat [(un)official]

Rom based on this: https://forum.xda-developers.com/elephone-p9000/development/rom-aokp-nougat-t3690278
Full credits go to the AOKP team who made the rom for P9000.
To use on P9000 Lite you may need CWM 3.0.2.8 and you have to restore the backup zip provided in the link.
Features:
- Same as P9000 AOKP rom.
- Gapps (Micro) come preinstalled.
Warnings:
- The unpacked rom uses up to 5200MB, so make sure you got free space!
- Put the rom backup on an SD Card, not on internal memory.
- Fingerprint options make the settings app crash (Obviously).
Bugs:
- The rom occupies about 20GB because of a bug.
- Charging seems to be painfully slow. (If someone could fix this, it would be really awesome.)
Installation:
You have to put the folder from the zip in TWRP\BACKUPS.
It should appear and then you should be able to see the rom and install it.
Download Links:
http://aftermath-studio.go.ro/IBOVHQ49DEAML78T.zip
http://aftermath-studio.go.ro:8080/Upload/IBOVHQ49DEAML78T.zip - Edit: I also added a torrent in the attachments.
(Please post to mirrors and post comments with the mirrors, and I'll update the original post)
Good luck!

Update:
For my phone, it charged the battery a bit, or so it seems, and then it kept going down.
Not sure what the bug is, at least for now.
So keep this in mind while downloading.
Any contribution is greatly appreciated.

xnd_bogdan said:
Update:
For my phone, it charged the battery a bit, or so it seems, and then it kept going down.
Not sure what the bug is, at least for now.
So keep this in mind while downloading.
Any contribution is greatly appreciated.
Click to expand...
Click to collapse
ATM I can only point you to CONFIG_MTK_PUMP_EXPRESS_(PLUS_)SUPPORT.
Did you set the following in devconfig?
Code:
CONFIG_MTK_PUMP_EXPRESS_SUPPORT=y
CONFIG_MTK_PUMP_EXPRESS_PLUS_SUPPORT=y

Tarkness said:
ATM I can only point you to CONFIG_MTK_PUMP_EXPRESS_(PLUS_)SUPPORT.
Did you set the following in devconfig?
Click to expand...
Click to collapse
he ported the rom, doesnt seem like he build it

Ruben Craveiro said:
he ported the rom, doesnt seem like he build it
Click to expand...
Click to collapse
Yup.
That's what I did

xnd_bogdan said:
Yup.
That's what I did
Click to expand...
Click to collapse
you need to change more modules and change some stuff on boot.img i think on the file init.rc on boot.img to allow charging

Ruben Craveiro said:
you need to change more modules and change some stuff on boot.img i think on the file init.rc on boot.img to allow charging
Click to expand...
Click to collapse
I'll definitely try doing that but for now I took a break, since finals are coming.
If somebody fixes it before I get to have some free time, that would be even better to be honest.

xnd_bogdan said:
I'll definitely try doing that but for now I took a break, since finals are coming.
If somebody fixes it before I get to have some free time, that would be even better to be honest.
Click to expand...
Click to collapse
i doubt that will happend, i dont think many people use the lite version, me in particular use the normal version, so i cant really fix it.

Do we know if anyone fixed it?
Sent from my Redmi 5 Plus using Tapatalk

Hi!
Anybody fixed the problems?

Hello.
I was going to continue porting this but unfortunately my phone failed so I was forced to buy a new one.
I'm afraid I can't work on this anymore, as I no longer have a p9000 lite