Related
i was thinking on rooting my nexus one phone but i have this question to determine if i should or not.... my question is am if i root my nexus one with cyanogen rom or desire rom... am i able to get ota updates stll if so how...and is there a way to unroot a nexus one yet?????????
This has been ask many times before but to get to the point. Cyanogen and other developers that work on the roms will included any updates that will improve the user experience. Most of the time the updates will happen before the ota comes out. If you want the options to customize the phone beyond the normal apps and performance improvement then root. Rooting is not for everyone so please do your homework if this is your first time.
well reason i ask is because i heard even if u root the phone and then decide to put an official rom then u can then received ota roms is this not true or??
No. This is a general answer. If a update is done the developer will included it in his build. All you do then is flash the updated version of the rom.
I haven't seen an updated thread for CM lately, so I figured I'll start one. I'm keeping this one updated myself with Cyanogen's format.
Developers:
cyanogen - http://twitter.com/cyanogen
codeworkx - http://twitter.com/codeworkx
dumdidum - http://twitter.com/dumdidum
coolya - http://twitter.com/coolya
finghin - http://twitter.com/finghin
eugene - http://twitter.com/eugene_373
and a lot more!
CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Visit the CHANGELOG for a full list of changes and features!
All source code is available at http://github.com/codeworkx! Send pull requests with your changes!
INSTRUCTIONS:
- First time flashing CM6 to your Vibrant (or coming from another ROM)?
1. Unlock/root your device and install Clockwork Recovery via ROM Manager.
2. Do a Nandroid backup!
3. Flash the INITIAL kernel via ODIN.
4. WIPE.
5. Install the ROM.
6. [OPTIONAL] Install the Google add-on.
7. [OPTIONAL] Install Eugene's kernel.
8. [OPTIONAL] Install latest su binary.
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Get me the file "/proc/last_kmsg".
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get me the full output.
- Pastebin links preferred
- Please use the [URL="http://code.google.com/p/samsung-gt-i9000-cyanogenmod/issues/list]issue tracker[/URL] whenever possible!
DOWNLOADS
Initial Kernel: http://www.codeworkx.de/download/cyanogenmod/CM-GalaxyS-Kernel-initial.tar
CyanogenMod Latest Version: http://www.codeworkx.de/download/cyanogenmod/CM6.1-GalaxyS-BETA3.zip
Google Apps Add-on: http://android.d3xt3r01.tk/cyanogen/gapps/gapps-hdpi-20101114-signed.zip
Eugene's Kernel: http://www.multiupload.com/682GAOWJ4B (fixes battery drain, kernel panics, and wake issue. adds OC/UC.)
su binary: goo.gl/Qzi8w (if apps think the phone isn't rooted.)
[NEW] 05012011 Nightly Build: http://www.codeworkx.de/download/cyanogenmod/CM6.1.1-GalaxyS-NIGHTLY.zip (VERY EXPERIMENTAL.)
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
The preferred method of installation is via ROM Manager, or you can head over to the CM Forums for manual downloads.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
Oh dear god... Thank you!
Getting close now. Once this is solid, holy moly.
s15274n said:
Getting close now. Once this is solid, holy moly.
Click to expand...
Click to collapse
Actually, it's pretty good for a daily driver right now. Yeah, there are a few little things that still need to be worked out, but it's getting there.
Woohoo! I hope there will be a non-Odin path soon.
Unfortunately I'm having wake issues with Eugene's kernel, and when I tried to ODIN the original kernel, I can't boot. I would've used logcat to check out what's happening, but for some very very strange reason, adb.exe disappeared from my sdk directory. Also, my JDK is f***ed up for some reason too (though it appears to be caused by Oracle purchasing Sun and changing the company name references in the JDK from Sun to Oracle... I have old Sun version 17 installed and then another later version under the Oracle branding).
Though I was surprised to see my phone running CyanogenMod pretty stable (until it crashes while sleeping), I can't use this anymore... I missed a few important calls. I even tried setting the CPU frequency setting to 200-1000 Mhz like eugene suggested, but that doesn't fix the problem.
I love AOSP Android, especially CyanogenMod. I'm so desperate for a non-Samsung environment that if I could use a plain AOSP build without the improvements of CyanogenMod, I would use it.
I'll wait for TheDudesAndroid to release the official Vibrant version of CM.
TheDudesAndroid on twitter
PSP_Hacker said:
I'll wait for TheDudesAndroid to release the official Vibrant version of CM.
Click to expand...
Click to collapse
Hope you're patient. We might have unofficial / non-CM 2.3 before then.
This is for international i9000 model, not the Vibrant.
What kernel number is that for eugene kernel 3#?
Im sure everyone would love to contribute just to get it out nice and stable since teamdouche only loves HTCs
epakrat75 said:
Hope you're patient. We might have unofficial / non-CM 2.3 before then.
Click to expand...
Click to collapse
Vibrant + sXe V4 (V3.1 Theme) + OCLF + JK2 Modem
diazf09 said:
What kernel number is that for eugene kernel 3#?
Click to expand...
Click to collapse
It's #3. If you could find a link for me, that would be great.
Sent from my SGH-T959 using XDA App
smackdown85146 said:
It's #3. If you could find a link for me, that would be great.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
http://www.multiupload.com/D077HM3K74
diazf09 said:
http://www.multiupload.com/D077HM3K74
Click to expand...
Click to collapse
My bad dude. It's actually #1. Typo on my phone. But it runs CM pretty smoothly, so I'm not complaining.
Yeah that link was for the #3 kernel
Can someone tell me what benefits CyanogenMod brings? I've never used it. JK6 ROM works well, what I lose and what I get after flashing to CM? Thanks.
very nice!!!
kennyp987 said:
Im sure everyone would love to contribute just to get it out nice and stable since teamdouche only loves HTCs
Vibrant + sXe V4 (V3.1 Theme) + OCLF + JK2 Modem
Click to expand...
Click to collapse
It's not that they only love HTC. It's that HTC does a much better job with releasing source and being generally mod-friendly, at least more so than Samsung or Motorola or just about anyone else.
lorendroll said:
Can someone tell me what benefits CyanogenMod brings? I've never used it. JK6 ROM works well, what I lose and what I get after flashing to CM? Thanks.
Click to expand...
Click to collapse
You will lose the codec for HD video, so Avatar and whatever else you have on your phone will not play, thats the a big one for me, as soon as they get that resolved I will be a very happy man. Also the Kernel is bad on the battery, very bad (12 hours) very very minimal use, sync wifi off.
So, I just got this working on my telus fascibrant (Don't ask. )
Any idea why the home +back buttons both function solely as back buttons and how to change said thing around?
0mega1 said:
So, I just got this working on my telus fascibrant (Don't ask. )
Any idea why the home +back buttons both function solely as back buttons and how to change said thing around?
Click to expand...
Click to collapse
Try using Eugene's kernel. It worked for my Vibrant. Not sure what your "Fascibrant" is, so I'm not sure if it might work for you.
I've had my UK Galaxy Tab (GT-P1000) for quite some time and for almost all that time, i've been waiting for the damn 2.3 update. I pretty much check Kies most mornings but as yet, like many, I've never had the notification of update at all.
I've noticed that the 2.3 update file (P1000XXJQ1) is available at the Galaxy Tab forum but if I update using Odin, will it stop me reverting back to 2.2 or getting 'official' updates via Kies after I've reverted back to 2.2?
Finally, does this really matter if I don't get updated by Kies anymore? Realistically, the 2.3 update is likely to be the last update that the Tab is going to see anyway so is there any reason why I should not update using Odin and be damned?!
I'm in the same boat. XEU seems to have been forgotten. Can't help with the ODIN/Root. Instructions seem fragmented to say the least. If an idiot's guide is out there I might try it.
Hi Ravi,
I am in the same boat as you. I am tired of waiting for the upgrade and am considering buying the new Sony Tablet S or even wait for the Sony Tablet P. I would prefer to upgrade because I have the Samsung Keyboard and also the HDMI charging dock.
My firmware version is PDA:JMI /PHONE:JMA / CSC:JM5 (XEU)
The only thing that stops me is that I am not 100% sure which files I should download. I have checked out many sites but guess I am not confident enough yet!
I wish Samsung would get a move on!!
Ofiaich
Guys, forget kies, and forget Samsung. I've been on 2.3 since I got my tab 4 months ago and now I'm on overcomes kratos ROM. Honeycomb builds have been coming and going, you can get stock 2.3 and pretty soon ICS will be developed by some amazing devs on here. Head into the dev section and don't look back!
That's my opinion anyway
Sent from my GT-P1000 using Tapatalk
Thanks Biffroy but what I'm worried about is that if I install a custom ROM and at some point decide to switch back to a stock ROM (maybe to sell the Tab or something) will I be selling something that cant be updated using Kies?
I know it's a bit corny these days but I'd feel bad about passing something on to someone who couldn't update it!!
Also, is there an idiots guide to upgrading to this ROM - i'm pretty useless when it comes to technical stuff so I really would need an idiot's guide..
Ravi said:
Thanks Biffroy but what I'm worried about is that if I install a custom ROM and at some point decide to switch back to a stock ROM (maybe to sell the Tab or something) will I be selling something that cant be updated using Kies?
I know it's a bit corny these days but I'd feel bad about passing something on to someone who couldn't update it!!
Also, is there an idiots guide to upgrading to this ROM - i'm pretty useless when it comes to technical stuff so I really would need an idiot's guide..
Click to expand...
Click to collapse
there is no such thing as an "idiot's guide" when it comes to ROM flashing as it is not recommended for complete newbies.
what I suggested is to read the instruction in here. In my opinion the guide is the most comprehensive of all instructions found anywhere. If reading the guide you still find it too complicated then I suggest you let somebody else do it for you or else be content with froyo.
There is also no big problem if you want to get back to froyo later,I've done it several times, but then you said you don't know how to flash so I guess you are stuck on froyo.
Have you tried bringing your tab to samsung service center in your area?
bongski55 said:
there is no such thing as an "idiot's guide" when it comes to ROM flashing as it is not recommended for complete newbies.
what I suggested is to read the instruction in In my opinion the guide is the most comprehensive of all instructions found anywhere. If reading the guide you still find it too complicated then I suggest you let somebody else do it for you or else be content with froyo.
There is also no big problem if you want to get back to froyo later,I've done it several times, but then you said you don't know how to flash so I guess you are stuck on froyo.
Have you tried bringing your tab to samsung service center in your area?
Click to expand...
Click to collapse
I recently bought a tab in Tesco (got it cheap). Have been in contact with Samsung regarding the update. Seems to be conflicting info, via the online support was told that GB had been released, but I would need to take into service center for them to do the update. Just had a call from a Samsung technician who told me no update has been released for the tab, except for units on Three and from CPW. I am expecting a follow up call to advise when an "official" update will be made available via KIES.
Hi, i have a suggestion for you to update to Gingerbread, have you ever tried the overcome experience? It's awesome....try to update to gingerbread with it, i bet you won't regret
www
teamovercome
net
(plz add "dot" by yourself, becoz this forum don't let newbies to put outside link)
Ravi said:
Thanks Biffroy but what I'm worried about is that if I install a custom ROM and at some point decide to switch back to a stock ROM (maybe to sell the Tab or something) will I be selling something that cant be updated using Kies?
I know it's a bit corny these days but I'd feel bad about passing something on to someone who couldn't update it!!
Also, is there an idiots guide to upgrading to this ROM - i'm pretty useless when it comes to technical stuff so I really would need an idiot's guide..
Click to expand...
Click to collapse
Going back to stock froyo is easy enough and kies won't know the difference if you do it right. We are ALL newbies at one time, I've only been doing this for less than a year, started with my sgs phone as Samsung were taking there time releasing 2,3 and I'm very impatient I've (soft) bricked my phone and tab dozens of times, it's trial and error and very confusing. I am no where near being someone who "knows his stuff" I just love playing around. Go into the dev section and take a look. If you follow the guides from team Overcome and manage to get kratos on your tab, you will be a very happy bunny. There is a bootloader patch in the "stickies" section that you need to read too
This is hard work if your new, but if you follow the overcome guide you should be OK. You're more than welcome to ask me more questions but remember- I'm still a newbie myself and not a dev! I am however glad for messing up and bricking my phone and tab so many times- it's how you learn!
Good luck!
Sent from my GT-P1000 using Tapatalk
Thanks Biffroy,
I've read the instructions a couple of times and watched a couple of 'how to' vids on Youtube and i'm going to give it a go today. I'm a bit nervous but I think i'll be ok!
Guess we all have to dive in at some point!!
Thanks again for the advice.
Hi Ravi,
I am going to try too after the weekend, perhaps Monday! Please can I be selfish and ask you to post here how you got on?
I will post my expereinces too!
I flashed my old Nexus One a long time ago, and am a bit bervous to flash my Tablet!
Ofiaich
Sure! I'll be happy to report back.
Ravi said:
Thanks Biffroy,
I've read the instructions a couple of times and watched a couple of 'how to' vids on Youtube and i'm going to give it a go today. I'm a bit nervous but I think i'll be ok!
Guess we all have to dive in at some point!!
Thanks again for the advice.
Click to expand...
Click to collapse
No worries i'm really interested to know how you both get on so let me know!!!
happy flashing!
I would offer the following:
First, root your device. Get Superuser installed. There is Superoneclick, or I believe Chainfire's CFRoot.
Then back-up your system! Very important, so that you can go back to your specific firmware. (I didn't do this). I believe Rotohammer has a back-up utility ?.
Then install the ROM of your choice.
Overcome instructions are very detailed, and easy to follow.
Good luck!
easy question!
if all went smoothly, how long can this update to an Overcome Rom expect to take?
Ofiaich
ofiaich said:
easy question!
if all went smoothly, how long can this update to an Overcome Rom expect to take?
Ofiaich
Click to expand...
Click to collapse
10 minutes if you've done it a few times!
But for a first time, following the overcome guide step by step, I guess you're looking at 30-60 minutes....
Sent from my GT-P1000 using Tapatalk
Ravi said:
I've had my UK Galaxy Tab (GT-P1000) for quite some time and for almost all that time, i've been waiting for the damn 2.3 update. I pretty much check Kies most mornings but as yet, like many, I've never had the notification of update at all.
I've noticed that the 2.3 update file (P1000XXJQ1) is available at the Galaxy Tab forum but if I update using Odin, will it stop me reverting back to 2.2 or getting 'official' updates via Kies after I've reverted back to 2.2?
Finally, does this really matter if I don't get updated by Kies anymore? Realistically, the 2.3 update is likely to be the last update that the Tab is going to see anyway so is there any reason why I should not update using Odin and be damned?!
Click to expand...
Click to collapse
Had this update for nearly 4 months now... Got it when it first came out.
Stock 2.3 Rom, factory unlocked
Can anyone tell me the benefits of the Overcome ROM to say Stock 2.3.3. I've been to their site and you read stuff in forums but nowhere have I seen a .....
"This ROM is designed to run faster/be more stable/offer this feature/be more customisable.etc....." statement(s).
Also (and no disrespect to the originators) is the source for the ROM available as well?
Regards
pinsb said:
Can anyone tell me the benefits of the Overcome ROM to say Stock 2.3.3. I've been to their site and you read stuff in forums but nowhere have I seen a .....
"This ROM is designed to run faster/be more stable/offer this feature/be more customisable.etc....." statement(s).
Also (and no disrespect to the originators) is the source for the ROM available as well?
Regards
Click to expand...
Click to collapse
Ha? From the Development thread:
ROM FEATURES
JPA Base Rom - ANDROID 2.3.3
Overcome kernel v3.3.1 included
No Modem is included - due to a variety of personal preference I decided to leave that a la carte
Fully Deodexed
Fully Zipaligned
Rooted with busybox installed
Reboot/Recovery/Download options added to the power menu
Accurate battery mod with gingerbread styling
Blur removed across system (i.e. behind power option menu) - significantly improves performance
Power Off confirmation disabled
Screen off animation enabled
Overscroll Glow effect enabled
Added AppWidgetPicker
CSC set to XEU
Ads Blocked
Updated Market to 3.0.26
Updated Maps to 5.8.0
Flash Player removed due to compatibility issue - install from market and you'll be all set.
Updated GMail to 2.3.5
Updated YouTube to 2.1.6
Updated SamsungApps to 2.5.039
Updated StreetView to 1.6.0.6
Updated Thinkfree Office Suite
Removed Startup/Shutdown sounds
Cool boot animation
A2DP Bluetooth Connection Fix Integrated
SIP calling enabled over 3g AND WiFi
Fugutweaks integrated
Browser mods (enabled "Default Zoom" in settings, added "User Agent" in settings, set plugins to "on demand" by default)
KERNEL FEATURES
Support RFS/EXT2/EXT3/EXT4
OC/UV with these steps: 1.6ghz, 1.5ghz, 1.4ghz, 1.3ghz, 1.2ghz, 1ghz, 800mhz, 600mhz, 400mhz, 200mhz, 100mhz
Replaced kernel jhash2 with jhash3
Adjusted kernel HZ value to improve smoothness
Optimized lowmemorykiller values
Optimized compiler flags
Voodoo Sound v10 (courtesy of supercurio)
Voodoo Lagfix (courtesy of supercurio)
Overcome CwM Recovery v4.1.1.4 (Custom built Clockworkmod v4.0.1.4)
Full support of internal/external SD cards in Recovery
V(R) scheduler added and set as Default
Kernel tweaks to VM and Scheduler for better performance
Built in CIFS/TUN/SlowWork support
Touchscreen Undervolted (courtesy Koxudaxi)
RAM Undervolted
Stochastic Fair Blue (SFB) Network Scheduler
Autogroup Scheduler
Asynchronous I/O Enabled (AIO)
Backlight Notifications (Thanks to Neldar for the mod and Koxudaxi for the patch)
Overcome v3.1.0-KRATOS
Overcome Kernel v3.3.1 Included
XWJPA Base
1080p Streaming Flash now smooth as butter
Wifi reconnect bug fixed (thanks to source built wpa_supplicant from disguztipated)
Updated Google Talk client with fully functioning one (identical to 2.3.4)
Updated Gmail to 2.3.5
Overcome Kernel v3.3.1
Overcome CwM Recovery Updated to v4.1.1.4 (Upstream fixes and enhancements)
Numerous Upstream improvements
Updated config_hz and user_hz to improve smoothness
Optimized compiler flags
Set V(R) Scheduler as default
My only issue is the warming of my tab(most probably result of OC). Everything else is as stated....I don't think the stock has these features.
Also unless you are a member of the Overcome team I don't think they will give you the source.....You won't even get the stock firmware JPA
bongski55 said:
Ha? From the Development thread:
ROM FEATURES
JPA Base Rom - ANDROID 2.3.3
Overcome kernel v3.3.1 included
No Modem is included - due to a variety of personal preference I decided to leave that a la carte
Fully Deodexed
Fully Zipaligned
Rooted with busybox installed
Reboot/Recovery/Download options added to the power menu
Accurate battery mod with gingerbread styling
Blur removed across system (i.e. behind power option menu) - significantly improves performance
Power Off confirmation disabled
Screen off animation enabled
Overscroll Glow effect enabled
Added AppWidgetPicker
CSC set to XEU
Ads Blocked
Updated Market to 3.0.26
Updated Maps to 5.8.0
Flash Player removed due to compatibility issue - install from market and you'll be all set.
Updated GMail to 2.3.5
Updated YouTube to 2.1.6
Updated SamsungApps to 2.5.039
Updated StreetView to 1.6.0.6
Updated Thinkfree Office Suite
Removed Startup/Shutdown sounds
Cool boot animation
A2DP Bluetooth Connection Fix Integrated
SIP calling enabled over 3g AND WiFi
Fugutweaks integrated
Browser mods (enabled "Default Zoom" in settings, added "User Agent" in settings, set plugins to "on demand" by default)
KERNEL FEATURES
Support RFS/EXT2/EXT3/EXT4
OC/UV with these steps: 1.6ghz, 1.5ghz, 1.4ghz, 1.3ghz, 1.2ghz, 1ghz, 800mhz, 600mhz, 400mhz, 200mhz, 100mhz
Replaced kernel jhash2 with jhash3
Adjusted kernel HZ value to improve smoothness
Optimized lowmemorykiller values
Optimized compiler flags
Voodoo Sound v10 (courtesy of supercurio)
Voodoo Lagfix (courtesy of supercurio)
Overcome CwM Recovery v4.1.1.4 (Custom built Clockworkmod v4.0.1.4)
Full support of internal/external SD cards in Recovery
V(R) scheduler added and set as Default
Kernel tweaks to VM and Scheduler for better performance
Built in CIFS/TUN/SlowWork support
Touchscreen Undervolted (courtesy Koxudaxi)
RAM Undervolted
Stochastic Fair Blue (SFB) Network Scheduler
Autogroup Scheduler
Asynchronous I/O Enabled (AIO)
Backlight Notifications (Thanks to Neldar for the mod and Koxudaxi for the patch)
Overcome v3.1.0-KRATOS
Overcome Kernel v3.3.1 Included
XWJPA Base
1080p Streaming Flash now smooth as butter
Wifi reconnect bug fixed (thanks to source built wpa_supplicant from disguztipated)
Updated Google Talk client with fully functioning one (identical to 2.3.4)
Updated Gmail to 2.3.5
Overcome Kernel v3.3.1
Overcome CwM Recovery Updated to v4.1.1.4 (Upstream fixes and enhancements)
Numerous Upstream improvements
Updated config_hz and user_hz to improve smoothness
Optimized compiler flags
Set V(R) Scheduler as default
My only issue is the warming of my tab(most probably result of OC). Everything else is as stated....I don't think the stock has these features.
Also unless you are a member of the Overcome team I don't think they will give you the source.....You won't even get the stock firmware JPA
Click to expand...
Click to collapse
Bongski
I'd already read that thanks, unless the reader has a detailed understanding of the numerous references contained within frankly it says nothing......
As I asked in my original post (rephrased) what's the main objective of the ROM? Is it "....increased speed/more stability/better customisation/more sex appeal...."
The above list would make sense if there was an explanatory comment for each item, for example what does "Fully Deodexed" mean and why do I need it?
I just want a 'Top Line' overview comment and then if I want to dig further the options above would be required.......
[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
Hi,
since the official maintainer "solk2" for the GT-I9506 moved on to CM12 before providing a final build incorporating his latest fixes I decided to make my own builds.
According to my personal experience the battery life has vastly improved. In particular the power consumption while the display is off has decreased substantially. Solk2 has apparently fixed some issues with the kernel so the battery issues are gone. So for everyone not yet willing to transition to CM12 (in my case inter alia due to the currently unstable state and the lack of a stable Xposed framework in Android 5) this might be a good alternative.
I will gladly share my unofficial ROMs, however I would need someone to host the files in order to do that. If anyone would be so kind as to host ROMs please let me know.
If any relevant code changes to CM11 will appear I will most certainly compile a new version.
* IMPORTANT *
Please note that these builds are based on nothing else than the unchanged official code from Cyanogenmod, solk2 and others. So every credit goes to them.
I will not and cannot make any changes to the code. The only thing I can do and will do is build a ROM thereof in case some interesting fixes etc. appear. However, since CM11 is becoming outdated there will most probably not be a lot of changes to come.
Also, it should be understood that I take no responsibilities whatsoever if anything goes wrong when you install the ROM. Like the original ROM this is completely at your own risk!
However, you can expect that any ROM I share has been installed on my own GT-I9506 (with Samsung firmware of 4.4.2 nordic countries) and runs without obvious issues. Your mileage may vary.
Here is the current version, including the CM-11.0 code base up to http://review.cyanogenmod.org/#/c/97688/ :
https://www.mediafire.com/folder/j0jynk3en95j5n1,soag9jcmrcajdhq/shared
* Note *
At least some of the issues with solk2's latest official builds were apparently caused by preceding changes to the kernel code. My builds use the latest code base of February 16 incorporating solk2's latest fixes (see https://github.com/CyanogenMod/android_kernel_samsung_ks01lte/commits/cm-11.0).
Unless solk2 will make further changes to the kernel (which I doubt as he has turned his attention to CM-12) the changes in my builds are only related to merged changes in the official Cyanogenmod code for CM-11.0 (see http://review.cyanogenmod.org/#/q/status:merged+branch:+cm-11.0). In other words the kernel will remain the same, even if the build date thereof may change.
Thank You. Perfect rom. in 2015-05-20 mms is working by default I have not find any bugs.
I'm on arter97 CM12.1 and I'd like to try this one. I can imagine a such install procedure:
-flash kk stock firmware (CNJ1 nordic) from odin
-reboot
-flash custom recovery from odin
-reboot
-flash your rom from custom recovery
Is that right?
ilfavi said:
I'm on arter97 CM12.1 and I'd like to try this one. I can imagine a such install procedure:
-flash kk stock firmware (CNJ1 nordic) from odin
-reboot
-flash custom recovery from odin
-reboot
-flash your rom from custom recovery
Is that right?
Click to expand...
Click to collapse
You do not need flash any stock. Just flash TWRP, make full wipe and flash this rom + gapps
Why is this rom so ignored? I flashed it a few days ago and I find it's great. Very very fast and absolutely rock solid. No bugs, no fc, no reboots.
ilfavi said:
Why is this rom so ignored? I flashed it a few days ago and I find it's great. Very very fast and absolutely rock solid. No bugs, no fc, no reboots.
Click to expand...
Click to collapse
I do not know how many have installed this ROM (anyone having done so please leave a reply here).
I see only a very limited number of reasons to transition to a new version of a ROM or Android in general:
1. If the new version provides functionality that I want or need (and material design isn't one of those); or
2. If the new version fixes a bug or security flaw (there is none that I know of).
At the moment CM-12 does not fulfill any of these criteria, instead I would lose the solidly working Xposed framework for an alpha version thereof.
I'm not intending to advertise this ROM, inter alia because the only thing I did was build it, so the credits should still go to solk2. But if anyone hears that someone has issues with the latest "official" version of CM-11, please direct them here.
HI !
This rom is awsome (smooth fast and stable) but is lacking of functionality...
@NeuDLi do you think I can use this rom for patchrom miui v5 or v6 on ? (as base)
And thanks for your work !
3lambda said:
HI !
This rom is awsome (smooth fast and stable) but is lacking of functionality...
@NeuDLi do you think I can use this rom for patchrom miui v5 or v6 on ? (as base)
Click to expand...
Click to collapse
I suppose so... Since it does use the official CM sources, just go ahead and try it.
Thanks for the reply
Do you have some knowledge on building stuff ? (via linux command, problem etc)
What should happen if I update via OTA as it ask me to do?
edit: I realized that the updates suggested are cm12 so can be ignored
I had one strange bug in this rom (maybe reason was in gapps): Go to SMS app, push new and write name in address line from above: phone getting list of contacts to chise. You choisew one and see wrong number (without region code) in address line.
If you push on contacts button and choise contacts here everything will be ok.
NeuDLi said:
I do not know how many have installed this ROM (anyone having done so please leave a reply here).
I see only a very limited number of reasons to transition to a new version of a ROM or Android in general:
1. If the new version provides functionality that I want or need (and material design isn't one of those); or
2. If the new version fixes a bug or security flaw (there is none that I know of).
At the moment CM-12 does not fulfill any of these criteria, instead I would lose the solidly working Xposed framework for an alpha version thereof.
I'm not intending to advertise this ROM, inter alia because the only thing I did was build it, so the credits should still go to solk2. But if anyone hears that someone has issues with the latest "official" version of CM-11, please direct them here.
Click to expand...
Click to collapse
Do you know to make compatible with this ROM, the Arter97 kernel?
Alexyerga said:
Do you know to make compatible with this ROM, the Arter97 kernel?
Click to expand...
Click to collapse
No, as stated I'm not a coder. And also why use Arter97 kernel anyway?
NeuDLi said:
No, as stated I'm not a coder. And also why use Arter97 kernel anyway?
Click to expand...
Click to collapse
Because the Solk2 kernel causes random reboots sometimes
Alexyerga said:
Because the Solk2 kernel causes random reboots sometimes
Click to expand...
Click to collapse
Then maybe you should ask Arter97 what's different in his kernel... Without any hint what difference causes this no-one has a realistic chance to find out. Or ask him to adapt his kernel to CM-based ROMs. I didn't know that his kernel does not work with CM, is that so?
Also, on my S4 I do not have frequent reboots. However, I once activate the advanced option "kernel samepage merging" and then had two reboots in 1-2 days. After resetting to deactivated no more reboots since about 2 weeks... Worth a try to check.
I would like to help, but I simply do not have anywhere near the experience and knowledge to find a kernel bug that apparently solk has not found himself!
NeuDLi said:
Then maybe you should ask Arter97 what's different in his kernel... Without any hint what difference causes this no-one has a realistic chance to find out. Or ask him to adapt his kernel to CM-based ROMs. I didn't know that his kernel does not work with CM, is that so?
Also, on my S4 I do not have frequent reboots. However, I once activate the advanced option "kernel samepage merging" and then had two reboots in 1-2 days. After resetting to deactivated no more reboots since about 2 weeks... Worth a try to check.
I would like to help, but I simply do not have anywhere near the experience and knowledge to find a kernel bug that apparently solk has not found himself!
Click to expand...
Click to collapse
Last time ago arter's kernel was compatible but he removed the support because he didn't have time to maintain two kernels.
Thanks anyway NeuDLi, i will tray the option "kernel samepage merging", it cames activated or deactivated by default? Because when I tried, I didn't change any option
Alexyerga said:
i will tray the option "kernel samepage merging", it cames activated or deactivated by default? Because when I tried, I didn't change any option
Click to expand...
Click to collapse
Well, another problem... I'm not sure if it is a bug in settings.apk or only in connection with our device. However, when you check the option is always ON, and upon leaving the settings.apk it will always return to being ON. So at least I can say that turning if OFF cannot have had an effect because it was never turned OFF.
However, I will try with KSM disabled now. For the time being you can manually disable it and lock this state (well at least until next reboot) by doing the following in an adb session or the terminal:
echo 0 > /sys/kernel/mm/ksm/run
chmod 444 /sys/kernel/mm/ksm/run
Another way would be to recompile the kernel with the option disabled. It would be far better to fix the issue in settings.apk. However, to file a bug report one would have to check if the behaviour is the same in the official nightlies... I read that someone reported this as a bug for the Oneplus One, but it was never resolved.
As an somewhat veteran in other xda-like forums, I advertised link to neudlis reply with his/her first build because it has been rock stable and fast. With my I9506 nordic.
No other customs have been this solid for 3 weeks straight, and I have been trying roms since december !
iBuu said:
As an somewhat veteran in other xda-like forums, I advertised link to neudlis reply with his/her first build because it has been rock stable and fast. With my I9506 nordic.
No other customs have been this solid for 3 weeks straight, and I have been trying roms since december !
Click to expand...
Click to collapse
Although I cannot often enough remind everyone that I did not provide or change any code but just build it that's still not too bad for the first build of a guy not that much into coding .
After a weekend with not much use but some hours of listening to audio books I was left with 21% charge after more than 3 days (see attached screenshot). That's just awesome! So I believe it can safely be said that any power consumption bug was resolved by solk2's latest patches to the kernel.
Also I believe that turning off kernel samepage merging might have helped additionally, so I encourage everyone to try it as well (see above post for manual way to turn it off as bug in settings.apk won't let you otherwise). In my opinion this option should default to off as it is said to be potentially unstable and the I9506 surely has enough RAM not to need it. So I prefer to lessen CPU load for longer battery life in exchange for potentially increased RAM occupation.