Database Develop

[NAND][pre-ALPHA] Kovsky ICS 4.0.3 testbuild0

Based heavily on TeamICS' work on HeroC, here is some very early initial work on ICS for the HTC Kovsky, AKA Sony Xperia X1. Built from AOSP source, with source available.
This is NOT for the faint of heart, and as far as I know nearly everything is broken right now. Instructions for building are coming soon - meanwhile, source is available at https://github.com/Zorlin with bits from https://github.com/CyanogenMod and https://github.com/TeamICS
Credits:
- TeamICS for all their ridiculously awesome work on Hero/HeroC
- CyanogenMod team, on which some TeamICS work is based.
- IceDroidV2 for the installer and current (slightly modded) kernel/boot.img - see IceDroidV2 thread for appropriate credits and source.
Currently working:
- Boots!
Currently not working:
- Everything else
- ADB
Notes:
boot.img is made from applying the ICS porting guide to IceDroidV2's boot.img
Currently there's a "hack" to attempt to get adb working - I threw in a copy of busybox as /system/bin/sh. Need to work out a better way, since it really didn't work...
I've got a bunch of ideas, but it's late, so... here:
DOWNLOAD:
testbuild0 - "The Magic ZIP File"

I can't believe it. OMG !!
BUT
Is it really ICS or just some skin for android 2.3 ?

X1 long live

Garena said:
I can't believe it. OMG !!
BUT
Is it really ICS or just some skin for android 2.3 ?
Click to expand...
Click to collapse
It's really ICS, which is why so little works. Gingerbread kernel for now, though.

woooaaaahhhh.....i love u full to all developers x1 the brilliant smart man ....kovsky never die !!!!

Do you really think you have enough background knowledge to get this off the ground? Or is it more of a "lets see what I can do" thing?

wallaceff said:
Do you really think you have enough background knowledge to get this off the ground? Or is it more of a "lets see what I can do" thing?
Click to expand...
Click to collapse
Yes and no. I think I can bring it to the same state as HeroC, maybe sans camera, and port hardware acceleration if/when they get it working. Kernel isn't my forte, though. At the moment adb is a major and confusing stumbling block... I'm missing something stupidly simple.

can we install it or it's not ready yet
I installed it that we install IceDroid v2 but nothing happened
It was stuck in android boot

mahmoodifar said:
can we install it or it's not ready yet
I installed it that we install IceDroid v2 but nothing happened
It was stuck in android boot
Click to expand...
Click to collapse
You install IceDroid V2 first and then overwrite it... but no, at the moment this is just for developers and tinkerers.

oh damn how nice would that be!!!!
go ahead zorlin an thx a lot for your work

Hi Zorlin how is going ur work ?

Slow... lots of real-life stuff going on. I'll probably publish build instructions on the weekend so others can start contributing.
Haven't forgotten you guys though.

Hello. Any progress or updates of Your work?

Oh my god..
I hope this really happen....
I will do wait your work!

revol5 said:
I hope this really happen....
I will do wait your work!
Click to expand...
Click to collapse
I will try to make something based on @Zorlin sources from #1 post. At all, probably He have own things to do so that is why He not respond.

fergy said:
I will try to make something based on @Zorlin sources from #1 post. At all, probably He have own things to do so that is why He not respond.
Click to expand...
Click to collapse
Your signature shows that you have a own kernel for NAND for X1?
What is working etc? maybe you could share it, when it has benefits to the current published ones
EDIT: maybe you could join zargloub and midnight for kernel dev?

neoofoox said:
Your signature shows that you have a own kernel for NAND for X1?
What is working etc? maybe you could share it, when it has benefits to the current published ones
EDIT: maybe you could join zargloub and midnight for kernel dev?
Click to expand...
Click to collapse
Hello @neoofoox.
Working everything except camera, fm radio and bluetooth (atm working on kernel to see where is problem).
Charging/discharging (at last I think it is ok as phone discharge within 20 hours->3.5 yrs old battery<- using push, wifi, bluetooth and location with 10-15 minutes of talking)
Also, phone wake asap You press power, ok or lock button (also with double security using pattern after normal unlocking)
I also don't think that this is right thread for something other than ICS work conversation.
When I got all things working proper, be sure that will make an new thread with image and patches to kernel.
BR,
Ramon
EDIT: Yeah, I will be happy to talk with @zargloub and @midnight regarding kernel.
EDIT2: Regarding sharing, I use only main system of Cyanogen but My own kernel, so as I say, until kernel completely work, I will not share it because of lot's of questions what users cannot fix until I fix holes inside kernel.

@fergy Last question ot jooc Does your phone reboots if you miss a call?

Sorry guys, I might be retiring my Kovsky... I'll publish build instructions and sources etc either way. If you don't hear back from me, assume I retired it
I'm getting fairly hopeful that you'll get decent ICS on the Kovsky soon though.
EDIT: Yup, it's official. I turned in my Xperia X1 in exchange for a free, off-contract Samsung Focus S (which I'm reselling) through the recent Microsoft promotion. I'll still have it for a week - I'm going to try and get ICS on it before then, but I don't really know what chances are like.
After that, I'll turn this over to someone else who can hopefully carry it through.

fergy said:
Hello @neoofoox.
Working everything except camera, fm radio and bluetooth (atm working on kernel to see where is problem).
Charging/discharging (at last I think it is ok as phone discharge within 20 hours->3.5 yrs old battery<- using push, wifi, bluetooth and location with 10-15 minutes of talking)
Also, phone wake asap You press power, ok or lock button (also with double security using pattern after normal unlocking)
I also don't think that this is right thread for something other than ICS work conversation.
When I got all things working proper, be sure that will make an new thread with image and patches to kernel.
BR,
Ramon
EDIT: Yeah, I will be happy to talk with @zargloub and @midnight regarding kernel.
EDIT2: Regarding sharing, I use only main system of Cyanogen but My own kernel, so as I say, until kernel completely work, I will not share it because of lot's of questions what users cannot fix until I fix holes inside kernel.
Click to expand...
Click to collapse
With these things working it is working perfectly, who need wifi if you can use mobile Data to access Internet and who needs bluetooth if you can send files via Email or connect your Phone via headphone port to your soundsystem etc..
I would test that if it becaume available and will report every bug etc. You could choose some people for testing which know something about that / for reporting bugs. So you can fix them and make the kernel 'perfect'.
Zargloub stopped developing and he has his files on gitorious so you could merge the kernels, here is working bluetooth and wifi (but it shows bad signal strenge)
Are you on github or gitorious so other devs can see what you are doing and maybe can help or people see what you are working on now.
I would love to test it, because for me it is allready perfect I hope we read something from you soon. You are our last hope
EDIT: sp3dev was also working on kernel you can get the sources here and here
EDIT2: I asked sp3dev if he would help, but he cannot for 2 reasons, first he has currently no time, the second reason is that he don't want to work on project which are close-source. Maybe you should think about releasing that before it is completely finished or make it open-source. Your device is old and that slow down the process a lot.

[INFO] Android 4.3 JSS15J&JSS15Q vs. JWR66V&JWR66Y, Custom Kernels and Graphic Issues

[INFO] Android 4.3 JSS15J&JSS15Q vs. JWR66V&JWR66Y, Custom Kernels and Graphic Issues
So, since this issue pops up often in various threads ever since 4.3 was released, I thought I'd make a thread I could point people to instead of repeating the same explanation over and over.
This has been discussed greatly in various Kernel/ROM development threads and I've been even getting PM's about it so I'll try explaining everything here. Most info is taken from discussions made on CyanogenMod-related threads, Franco kernel thread, thracemerin's WiFi-fix thread, and Google-related sources, so thanks also goes to everyone who participated.
On to business...
Background:
When Google released Android 4.3, it came in a few forms. One is the familiar OTA update zip and factory images. This is what people refer to as 'stock'. The build number for that stock release is JWR66V, also known as Android 4.3r1. This was later updated to JWR66Y (Android 4.3r1.1).
As you all know, Android is open source, which leads us to the Android Open Source Project (AOSP). This is where the source for Android located, and one could build the operating system/kernel (with provided drivers) from scratch and make a working flashable operating system. This is also the 'base' for custom ROMs.
AOSP has newer android revisions - Android 4.3r2.1, build number JSS15J, and Android 4.3r2.2, build number JSS15Q. These builds are newer than 'stock' JWR66V/JWR66Y, but they are official, are made by Google, and are available for anyone to build from scratch, just like JWR66V/JWR66Y. The differences are Google Apps, such as Google+, YouTube, Gmail, etc, which will not be included in an AOSP build, but could be downloaded from the store (or available as a flashable zip) anyway. AOSP also has a different browser while 'stock' comes with Google Chrome (which you could manually download if you wanted to). The system itself is still the same Android. If one decides to build Android from the older JWR66V/JWR66Y revisions, they will have the same system as someone else who flashed stock.
Why didn't Google release JSS15J as stock?
A Google employee mistakenly thought that JSS15J only has changes related exclusively to the new Nexus 7 device. He later apologized and acknowledged his mistake. JSS15J has an updated Nexus 4 kernel with dozens of GPU commits/improvements.
Which build is better?
Depending on who you ask. If newer is better, JSS15Q is better. If factory images are better, JWR66Y is better.
Which build should I use?
People who like factory images will stay with factory images. People who like the stock experience but care less about "factory images" could use a clean non-customized JSS15Q build. In a way, JSS15Q could be considered 'stock AOSP' if it's not customized. It's even more minimalistic than what comes with the factory images, because applications such as Google Keep/Earth/Maps and so on are not forced as system apps, and can be optionally installed from the store only if you want them.
Any other differences besides the updated kernel/GPU commits?
Most changes are under-the-hood. There was an updated network setting found in JSS15J/Q that doesn't exist in JWR66V/Y.
I heard something about a Wi-Fi change though?
There is indeed a major difference related to Wi-Fi. I won't get into many details here as there is a dedicated thread with months of discussions, but in short, JWR66V & JWR66Y still have the Wi-Fi notification delay issue that 4.2.2 had. This is because Google turned off ARP offloading for those builds, but later turned it on in JSS15J & JSS15Q. It was also on in JWR66N, the leaked unofficial build that we got prior to the official release.
If Google were to build a new factory images now from JSS15Q, it would have ARP offloading on, and Wi-Fi notification delays fixed. The change is only to an .ini file and the drivers are the same, so while a fix is needed for JWR66V/JWR66Y, it's a simpler fix. If you use JSS15Q you don't have to flash any Wi-Fi fixes at all.
What does this mean for Custom ROMs?
Custom ROMs are usually synced with the latest AOSP revisions and changes. CyanogenMod's Android build is JSS15Q, and the same goes for rasbeanjelly, Carbon, and most custom ROMs. Clean or clean-ish JSS15Q AOSP builds are also available for those who still want both the newest revision and the stock experience, just check the development threads.
HELP! My screen is stuttering and/or has weird green colors and/or doesn't respond properly to touch and/or is yelling at me!
That is mostly why this thread was needed. As mentioned before, JSS15J&JSS15Q have an updated kernel with some GPU fixes. This means that your kernel MUST match your ROM for the issue to go away. There are workarounds, such as disabling hardware overlays, but that is not really a solution. No hardware overlays = reduced performance and possibly other issues.
The basic rule is this:
If you use JWR66V/JWR66Y, either stay with its stock kernel, or MAKE SURE the custom kernel you flash was based on JWR sources.
If you use JSS15J/JSS15Q, either stay with its stock kernel, or MAKE SURE the custom kernel you flash was based on JSS sources.
This is of course a headache for kernel developers, as they need to either drop support for one version, or release two versions each time. Many kernel developers are already offering two version of their kernels - one for JWR-based builds and one for JSS-builds.
This means that if you use the AOSP build or most custom ROMs, you will have the screen issues if you use JWR-based kernels.
So there you have it. Unless some other solution is found, there will have to be 2 kernels - one for each build.

Well done
Wayne Tech Nexus

Anyone have links to a pure AOSP build with literally no alterations?
Sent from my Nexus 4 using Tapatalk 4 Beta

jaju123 said:
Anyone have links to a pure AOSP build with literally no alterations?
Click to expand...
Click to collapse
There are two I know of, they do have some very slight changes you could read about in their threads, I don't know of one with literally zero alterations whatsoever, but again the changes are very minor:
[ROM][JSS15J] aosp 4.3 for Nexus 4
[ROM][28/07/2013] AOSP JSS15J KALO v3.0

Cheers for the clear up, was doing my head in with all the weird builds
Sent from my Nexus 4 using Tapatalk 4 Beta

Is there any way we can (nicely) ask Google to release a factory image from the JSS build? I think that would be the perfect solution, and I don't think it is really too hard for them to push it.

redsmith said:
Is there any way we can (nicely) ask Google to release a factory image from the JSS build? I think that would be the perfect solution, and I don't think it is really too hard for them to push it.
Click to expand...
Click to collapse
They could definitely do it if they wanted to, probably somewhat easily too. The OTA is being pushed slowly for a reason - not just for bandwidth purposes, but so that if some mistake happened, not all devices would be affected. It's probably not a very high priority for them like what happened previously with the December bug, but they could release a JSS15J-from-JDQ39 OTA to devices that haven't been updated yet, and JSS15J-from-JWR6V for those who did update. Posting factory images is easier, and the binaries are already good for both JWR6V and JSS15J. If they chose to release it, we'd forget about this whole thing 1-2 weeks later. But it's hard to say if they'll listen. Might be worth a try as long as it's done in nice/acceptable ways and not by spamming/yelling/threatening and so on.

They won't release new factory images...
Jean-Baptiste Queru said so...
He said both branchs are the same with the only difference in JSS15J being the new stuff for Nexus 7...
The new GPU commits are from the other branch... So that both matchs and don't give tearing effects or other problems...
Enviado do meu Nexus 4

He had some update statements since. Here they are:
In theory, JSS15J should work just as well as JWR66V for the existing devices. In practice, I expect that there could be minor differences (except for the new Nexus 7 where there are big differences), so if you're targeting a single device you might as well use the source code that matches the retail version the most. Personally, I like to live more on the bleeding edge, so when I carry an AOSP device I'm more likely to be running the master branch.
Click to expand...
Click to collapse
Here's an long-ish explanation of what happened:
-For a number of reasons, the kernel is built separately from the Android tree. We submit binaries of the kernel in the Android tree.
-Those binaries are large. In Google's internal tree, there are 1.5GB of Nexus 4 kernel binaries. With the way our tools work, that's 1.5GB of data that needs to be downloaded and stored by each user in each source tree. At the same time, the binaries don't have any significant value, since the value is in the source history, which is stored separately.
-To avoid making every AOSP user download gigabytes of unnecessary kernel binaries, starting with Nexus 4 (and now also in the new Nexus 7), we've been storing kernel binaries in dedicated projects, and I maintain a parallel history for AOSP that only contains the binaries that are necessary. Right now for Nexus 4, that tree is 31MB (to compare to 1.5GB).
-The retail release process of a new version is actually different for existing devices and for the new Nexus 7. To better reflect that, they each got their release branch, with existing devices in the JW branch (jb-mr2-release) and the new Nexus 7 in the JS branch (jb-mr2.0-release). JW entered final stabilization earlier than JS, which means that the jb-mr2-dev branch and the master branch in AOSP are closer to JS than to JW.
-To save space in the AOSP kernel projects, I try to have as few kernel binaries as possible in there, which means that I prepare those branches at the last minute (in this case I did that on Monday). During testing, I don't stage those projects and I manually use kernels directly from the development branches. For Nexus 4, when I did the final staging on Monday, I only included into the AOSP what ships to end users, i.e. from the JW branch, so I explicitly didn't include the kernel from the JS branch and I used the kernel from JW everywhere instead.
-Since the only changes in JS (compared to JW) were supposed to be related to the new devices, I assumed that the N4 kernel would be the same between the two (without actually checking), and I did all my testing of jb-mr2.0-release, jb-mr2-dev and master with the JS kernel (which was easier as it allowed me to use the same process for Nexus 4 and for the new Nexus 7). One of the changes done for the new devices was in the GPU code, in a way that required a new kernel for Nexus 4.
-The fix was to add the JS kernel to the relevant branches in AOSP.
So, there you have it: I mistakenly assumed there there'd be no kernel changes for N4 between JW and JS, and from there I did all my testing with the wrong kernel.
Sorry about that.
JBQ
Click to expand...
Click to collapse

markd0wn said:
He had some update statements since. Here they are:
Click to expand...
Click to collapse
So peolple who are on stock are outdated and still not enjoying all the gpu optizations?
Correct me if im wrong
typed from my NeXuS 4 tasting some revamped Jellybeans (stock 4.3).

C4SCA said:
So peolple who are on stock are outdated and still not enjoying all the gpu optizations?
Correct me if im wrong
typed from my NeXuS 4 tasting some revamped Jellybeans (stock 4.3).
Click to expand...
Click to collapse
Technically you are not wrong. It's a fact that JSS15J and its kernel has GPU optimizations/commits that are not included in the JWR66V build.

markd0wn said:
Technically you are not wrong. It's a fact that JSS15J and its kernel has GPU optimizations/commits that are not included in the JWR66V build.
Click to expand...
Click to collapse
So this 4.3 update is a huge fail for nexus 4 owners... And i was thinking that i wasnt going root it again...
Google messed up this time
4.3 is almost all about the gpu opt. and now people dont have it all on stock? ? ?
typed from my NeXuS 4 tasting some revamped Jellybeans (stock 4.3).

C4SCA said:
So this 4.3 update is a huge fail for nexus 4 owners... And i was thinking that i wasnt going root it again...
Google messed up this time
4.3 is almost all about the gpu opt. and now people dont have it all on stock? ? ?
typed from my NeXuS 4 tasting some revamped Jellybeans (stock 4.3).
Click to expand...
Click to collapse
I don't know how huge those optimizations are. I'm sure someone will do some GPU-specific benchmark comparison between the builds at some point and see. But yes, a mistake did occur. The average person will be updated to JWR66V (at least at this point) only. Others could install JSS15J manually from one of the threads mentioned in the previous page.

Thanks for the info. I flashed the factory images last night thinking I would much rather go with official images from now on. This thread tempted me to give the AOSP builds another try.
Honestly though, I don't know important the optimizations are. Maybe it's just me. Maybe it's just my own device...... but I find the stock build smoother than the AOSP builds. I get stutters while scrolling through my mms messages, for instance. And transitions on the stock feel smoother so far.
How does one know if we have delays in our wifi notifications though?

markd0wn said:
They could definitely do it if they wanted to, probably somewhat easily too. The OTA is being pushed slowly for a reason - not just for bandwidth purposes, but so that if some mistake happened, not all devices would be affected. It's probably not a very high priority for them like what happened previously with the December bug, but they could release a JSS15J-from-JDQ39 OTA to devices that haven't been updated yet, and JSS15J-from-JWR6V for those who did update. Posting factory images is easier, and the binaries are already good for both JWR6V and JSS15J. If they chose to release it, we'd forget about this whole thing 1-2 weeks later. But it's hard to say if they'll listen. Might be worth a try as long as it's done in nice/acceptable ways and not by spamming/yelling/threatening and so on.
Click to expand...
Click to collapse
Agreed. Any way we can contact them? Maybe in their support pages? I'm kind of lost here =D
We should definitely give it a try, we've got nothing to lose.

Why I can't boot into recovery?
I flashed factory image JWR few days ago, everything was good until today I just realized that I cannot boot into stock recovery. Everytime I enter bootloader and select recovery I only get dead android image with red exclamation mark.
Anybody experience this too?

Wonderful! I've been looking for somerthing since 25/07!
Thanks!!

simorangkir_dcs said:
I flashed factory image JWR few days ago, everything was good until today I just realized that I cannot boot into stock recovery. Everytime I enter bootloader and select recovery I only get dead android image with red exclamation mark.
Anybody experience this too?
Click to expand...
Click to collapse
Hold volume up + down and press the power button (may have to do it a few times). The stock recovery has its options hidden unless you press that combination once you get to the screen you are seeing.
Sent from my Nexus 4 using Tapatalk 4 Beta

mattkroeder said:
Thanks for the info. I flashed the factory images last night thinking I would much rather go with official images from now on. This thread tempted me to give the AOSP builds another try.
Honestly though, I don't know important the optimizations are. Maybe it's just me. Maybe it's just my own device...... but I find the stock build smoother than the AOSP builds. I get stutters while scrolling through my mms messages, for instance. And transitions on the stock feel smoother so far.
How does one know if we have delays in our wifi notifications though?
Click to expand...
Click to collapse
Can someone confirm this?

mattkroeder said:
Thanks for the info. I flashed the factory images last night thinking I would much rather go with official images from now on. This thread tempted me to give the AOSP builds another try.
Honestly though, I don't know important the optimizations are. Maybe it's just me. Maybe it's just my own device...... but I find the stock build smoother than the AOSP builds. I get stutters while scrolling through my mms messages, for instance. And transitions on the stock feel smoother so far.
How does one know if we have delays in our wifi notifications though?
Click to expand...
Click to collapse
Same too ,i feel stock smoother than AOSP .
Sent from my Nexus 4 using Tapatalk 4 Beta

[Q] Network problems (RIL) with latest Beanstalk 4.4

Hi,
I installed 2 weeks ago the latest Beanstalk 4.4.4010 CM-based and I really liked it, it is a very nice ROM and increased the life and performance of my phone by a lot.
At the beginning everything was fine, but now after 2 weeks I am having again the same network problems (losing connectivity, not being able to recover signal, and so on) that I had with my old CM ROM.
After reading a bit around in the forum, I found that there is this RIL change solution http://forum.xda-developers.com/showthread.php?t=2496075
But since this is a bit older, I don't know if it has been already implemented or not in the recent Beanstalk updates or if I still have to do it. And also if this only works with the P880-dev based ROMs or also with the CM based ones. It is difficult to say when one has to read so many threads.
Also an user uploaded a flashable zip fix of the RIL for the AD version. Does this mean that I can flash the P880-dev based ROM with AD and then just flash this zip and would avoid having to do the procedure of the above tutorial?
Is there another flashable alternative for me?
I also read somewhere that NamelessRom wasn't having this issue, so do you recommend to switch?
Thanks,
SC.

there are still several versions of RIL; i recommend you try a few of them till you find out the one that works.
the zip that was made for the AD version of rom works only and only with that specific rom, made on that specific date. any rom that was built after (or before) needs to have different flashable zip.
i do recommend you try nameless rom first (take a backup of beanstalk). take it for a spin for a few hours/days and see if you have any network issues. if you do not, you can extract RIL from nameless rom & implement it in beanstalk. good luck

Flying_Bear said:
there are still several versions of RIL; i recommend you try a few of them till you find out the one that works.
i do recommend you try nameless rom first (take a backup of beanstalk). take it for a spin for a few hours/days and see if you have any network issues. if you do not, you can extract RIL from nameless rom & implement it in beanstalk. good luck
Click to expand...
Click to collapse
:good:
Thanks, then I'll try my luck with Nameless. I hope I will not miss it much.
There isn't yet something like dual booting in Android, no?
Cheers,
S

There is for our device, search for twrp multirom. Its a bit of a hassle to set up properly thoguh

[Kernel] Shield Portable Kernel Development [Incl. Guide]

Welcome to the first custom kernel for the KitKat Shield.​
This thread is for the development and building of the Shield Portable kernel.
This is not intended to download a build, post issues, and return when fixed.
Kernel Source:
https://github.com/StarKissed/starkissed-kernel-roth
Kernel Downloads:
https://goo.im/devs/playground/shieldroth
The kernel can be built using the commands below or the included script.
Code:
make tegra11_android_defconfig -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
make tegra114-roth.dtb -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
make -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
App & Donations:
StarKissed [SKU] on Google Play allows you to configure many of the options provided by this kernel. Issues or comments about the app can be posted at the XDA StarKissed app thread
Donations are not being collected through the forum. If you would like to donate, you may do so through StarKissed [SKU] on Google Play by using the donate options located in the top right (the green dollar bill guy).

[Kernel] Shield Kernel Development
The included ramdisk is for update 98. If you are on 72, this will most likely result in a bootloop. Using the 72 ramdisk will not work with this kernel, as the source is specific to "OTA 5" according to the Nvidia gitweb.

I recently updated the source and changed a few commands that may explain why current source resulted in non-working builds. I will be testing builds soon and then begin modifying the kernel once the core build is verified working.

Nice, I hope there will also be an overclocked kernel for 4.4. I know it's silly but I miss the 4.3 overclocked kernel.

rylen said:
Nice, I hope there will also be an overclocked kernel for 4.4. I know it's silly but I miss the 4.3 overclocked kernel.
Click to expand...
Click to collapse
All the code is there, it just loops. I'm not sure what's going on with it. The shield tablet version works.

Quick question. Any chance you could update the usb ethernet drivers in this? Specifically, I'm suffering from this bug on an ASIX 88772 on the official kernel, and it seems their driver is rather out of date. Thanks, and keep up the good work!

bakageta said:
Quick question. Any chance you could update the usb ethernet drivers in this? Specifically, I'm suffering from this bug on an ASIX 88772 on the official kernel, and it seems their driver is rather out of date. Thanks, and keep up the good work!
Click to expand...
Click to collapse
Won't do much good until it boots

True enough, just thought I'd bring it up since it's a fairly easy fix. In the meantime, I threw together a stock kernel with an updated driver to get by. I had one problem after another with the latest official driver, but the good folks at LKML had already put some work in on v4.1.0 several years ago. Using drivers/net/usb/asix.c and usbnet.c from the 3.4.106 source built without problems.

Beginning to think I may have to settle for building against the full source on this one. It boots fine when doing that, but not built alone. The shield tablet builds fine alone, so there's no explanation for it.

you are going to make a new build of your kernel? if you need help with the tests i can help.

YamazakiRobert said:
you are going to make a new build of your kernel? if you need help with the tests i can help.
Click to expand...
Click to collapse
Things are a bit crazy, but once I can get all of the changes fixed up and it'll build clean, I'm going to try to run it over night.

Slightly off-topic, but I'll ask you since you're the only other person I know building a shield kernel. I built nvidia's kernel, changing only the two drivers associated with my ethernet, but for some reason console mode has stopped working now. Have you ran into a similar problem? Plugging HDMI in pops up the selector, but clicking on console mode doesn't do anything - it just stays on the selector screen.

bakageta said:
Slightly off-topic, but I'll ask you since you're the only other person I know building a shield kernel. I built nvidia's kernel, changing only the two drivers associated with my ethernet, but for some reason console mode has stopped working now. Have you ran into a similar problem? Plugging HDMI in pops up the selector, but clicking on console mode doesn't do anything - it just stays on the selector screen.
Click to expand...
Click to collapse
It shouldn't be related. You may need to check the proprietary drivers. I believe HDMI is one.

Didn't bother to find out what the problem was, it just stuck around because I was doing dirty builds as I tested. Once I got a few other tweaks and had some time, I did a clean build and it resolved itself. Did you manage to get your kernel booting when building it by itself? I'm sure I'm doing something wrong there too, but I've been grudgingly building the entire device, since that at least works reliably.

What is so special about this kernel compared to stock ? goodjob already btw, you're one of the few who actually have a kernel
It's really sad how not much development is going on, it's such a good device there is only like 1 release at the original section :/

[Q&A] [INDEX] Samsung Galaxy S3 LTE - ROMs, Kernels, MODs, Recoveries, Themes [09 Ja

[Q&A] [INDEX] Samsung Galaxy S3 LTE - ROMs, Kernels, MODs, Recoveries, Themes [09 Ja
Q&A for [INDEX] Samsung Galaxy S3 LTE - ROMs, Kernels, MODs, Recoveries, Themes [09 Jan 2015]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [INDEX] Samsung Galaxy S3 LTE - ROMs, Kernels, MODs, Recoveries, Themes [09 Jan 2015]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

hi, i am new here! what do you think which is te best rom for i9305?

robi96 said:
hi, i am new here! what do you think which is te best rom for i9305?
Click to expand...
Click to collapse
Best answer I can give: It depends.
Other than that, it's not allowed to start some discussions like best/worst ROM, cause usually they are made for different needs.
Get an oversight of some ROMs (not all available for the i9305).
I can tell you my experience and OmniROM was a rock solid ROM for me with Android 4.4.4, not that feature rich. But you can add features with Xposed framework up to KitKat. On Lollipop you cannot use Xposed yet. Also, the Lollipop ROMs are not stable yet imo. Nevertheless I use the Nameless ROM 2.0, which is working not bad, having some battery issues, but no other probs. However, it's not a reliable daily driver yet, therefore it's beta.

benkxda said:
Best answer I can give: It depends.
Other than that, it's not allowed to start some discussions like best/worst ROM, cause usually they are made for different needs.
Get an oversight of some ROMs (not all available for the i9305).
I can tell you my experience and OmniROM was a rock solid ROM for me with Android 4.4.4, not that feature rich. But you can add features with Xposed framework up to KitKat. On Lollipop you cannot use Xposed yet. Also, the Lollipop ROMs are not stable yet imo. Nevertheless I use the Nameless ROM 2.0, which is working not bad, having some battery issues, but no other probs. However, it's not a reliable daily driver yet, therefore it's beta.
Click to expand...
Click to collapse
thanks a lot and do you have some tips how can make omni smoother? which kernel? settings? or any xposed modules?

robi96 said:
thanks a lot and do you have some tips how can make omni smoother? which kernel? settings? or any xposed modules?
Click to expand...
Click to collapse
Honestly, for me needs Omni ROM was fast and smooth enough for me. I did not use a custom kernel. You can boost some transitions within the launcher app (depends on the app, Apex, Nova Go Launcher Ex should do) or in the developer options (window animation scale, transition animation scale and animator duration scale), disable animations or you can lower the speed, what usually leads to a more fluid experience.
With kernel settings apps like Trickster Mod, Kernel Tuner or Kernel Tweaker you can improve your experience with the standard kernel even more - without overclocking. Check their Q&A or FAQ, helped me. You need root access to your device to change kernel settings. Flash SuperSU if not done already.

Hello, I have been trying to flash for 2 days now but still couldn't get it working.
Initially, my I9305 is running on stock without root. I wanted to root it and then install recovery and ROM.
And so I prepare the necessary files, and start to flash.
I used CF-Auto-Root to root my device first, then got Resurrection ROM and Gapps to flash.
Then I started to get some issue, as it always fail. Error message like no file context and so on. So I read online resources, and found out that I had a older version of TWRP installed which may cause the install.
I then tried to upgrade TWRP but it doesn't allow me to. No choice, I had to flash philz touch, and I did.
I then tried to flash Resurrection again, boot up, and it keep giving me bootloop. After which I downloaded nameless ROM, and CM11 but same issue.
Yesterday night, I downloaded the stock firmware to try. I flashed it, and it is successful based on ODIN, but it still won't boot up.
I just tried it again and it stuck on the Samsung logo screen.
Can anyone tell me what else to do? What I have to do?
This is the stock firmware that I have downloaded and flash - I9305XXUENH1_I9305EVRENH1_EVR.
Let me know what other information I have to provide.
Thanks!

Good work thanks

Volume increase
Hi guys,
I am trying to increase the volume on my phone and spent already hours on the Internet to find out how to do it. I have rooted my phone using CM auto root, installed superSU and ES File Explorer. I was trying to follow instructions to go to system files using this program and edit Snd_Soc_mSm or sound folder but it just doesnt appear on my phone? I was wondering if there is something I can do about or maybe I missed something, I really have no clue.
My phone parameters:
Samsung S3 i9305
Android 4.3
Baseband I9305XUENG1
Kernel 3.0.31-2051278
Build JSS15J.I9305XXUENH1
I would be really gratefull for any help or instructions.
Thanks

@LeoDeos did you check the fb issue?

Japanese S3
Any good news about Japanese variant of S3?
I try to compile but have error at the very beginning.

dear xda members.
I'm moving (as probably many already had) from i9000 to i9305 looking for decent audio experience.
To achieve that I need to find a perfect match between recovery, rom and kernel.
I've gone through the linked index topic as well as tens of other customization-related ones, but still have some basic questions.
Generally it's about the proper Boeffla sound-oriented kernel selection.
I've noted only one or few compilations of Boeffla kernel for i9305 so I give it up on the beginning.
Seems that AGNi is the only resort. But here come the doubts.
how to properly match the kernels from AGNi pureCM and PUREstock list base on information available in MAjor Custom Rom comparison database
If custom ROM is based on AOSP (as the stock rom is - see the table, row 7), does this mean I should go for PUREstock kernel? For example for OMNIrom 4.4.4 should I select pureSTOCK v5.9.3? If my understanding is correct for PACman rom (based on CM) I should go for pureCM kernel.
OR
pureSTOCK kernels are reserved for Samsung roms, and the custom ones should be paired with pureCM kernels?

tomaneq said:
dear xda members.
I'm moving (as probably many already had) from i9000 to i9305 looking for decent audio experience.
To achieve that I need to find a perfect match between recovery, rom and kernel.
I've gone through the linked index topic as well as tens of other customization-related ones, but still have some basic questions.
Generally it's about the proper Boeffla sound-oriented kernel selection.
I've noted only one or few compilations of Boeffla kernel for i9305 so I give it up on the beginning.
Seems that AGNi is the only resort. But here come the doubts.
how to properly match the kernels from AGNi pureCM and PUREstock list base on information available in MAjor Custom Rom comparison database
If custom ROM is based on AOSP (as the stock rom is - see the table, row 7), does this mean I should go for PUREstock kernel? For example for OMNIrom 4.4.4 should I select pureSTOCK v5.9.3? If my understanding is correct for PACman rom (based on CM) I should go for pureCM kernel.
OR
pureSTOCK kernels are reserved for Samsung roms, and the custom ones should be paired with pureCM kernels?
Click to expand...
Click to collapse
I can truely recommend the "combination" you see in my signature block.

Mumtaz77 said:
Now I'm using Bliss Pop some weeks ago. This is a great ROM, but one problem is the USB charging. If i use the radio in my car to charge the phone, its just slow down the discharge. So no up charging.
If I flash the agni kernel, to let me charging rates changeable, the phone is randomly freeze, or not wake up and screen is leave blank.
But this rom is the best for me, just this charging problems make me nervous.
Click to expand...
Click to collapse
Great to hear that you're happy with Bliss Pop. I personally found the right ROM for me and my device, too.
I'm also extremely happy with AGNi v4.5.5, especially as AGNi offers so many and easy to handle settings' possibilities and such a large variety of governors. In the past, I also experienced a few situations with random freezes, black screens etc.
I solved these issues in two ways:
First by playing with different governors, governor and GPU settings, touchboost, touch wake etc. etc. It took me quite a while till I found my current combination of settings, with which my devices now perfectly runs.
It's a pity but I eventually realise that I'd to de-install Xposed and the one and only Xposed module I ran, XPrivacy.
Since I did both above, my SGS3LTE is running so smoothly and really without any problems.
Did you already played a bit with other kernel settings than charging rates?

Looking to find a (preferable) 5.1.1 or 6.0.1 rom to flash to a i9305 (LTE) version
Appreciate any suggestions or guidance - TY
Found the right threads

Hi! can I ask which threads/roms you found most useful/stable? thx
RetiredOldie said:
Looking to find a (preferable) 5.1.1 or 6.0.1 rom to flash to a i9305 (LTE) version
Appreciate any suggestions or guidance - TY
Found the right threads
Click to expand...
Click to collapse