[i9500][Resource] Bare-bone kernel with commit-history - Galaxy S 4 i9500 Original Android Development

Repository: https://github.com/AndreiLux/Perseus-UNIVERSAL5410.git
Branch: android-exynos-3.4-SEC
https://github.com/AndreiLux/Perseus-UNIVERSAL5410/tree/android-exynos-3.4-SEC
This is a clean kernel glued together upon Samsung's last public branch of android-exynos-3.4 with sources provided by the OSRC releases. The OSRC release has been stripped clean of all non-i9500 related code and sourced, as much as possible through the original patches.
I made a logical and chronological commit history of all elements and drivers of the UNIVERSAL5410 platform, within reasonable limits of course. Some components are lumped together, mostly things regarding plat-s5p and plat-samsung, and SMP code related to the 5410.
Most core kernel changes have been added with their corresponding upstream commits.
Key functional differences over the OSRC release for a compiled i9500 kernel:
WM5102 ALSA drivers upstreamed to their latest state from WolfsonMicro
Some core SMP changes have been updated to their actual public counterparts (IPI wakeup patch replaced with https://github.com/AndreiLux/Perseus-UNIVERSAL5410/commit/6d6fd0665d951dc9a26b78f3ce77c0cef3323892 for example).
The tree has partial big.LITTLE MCPM support and uses parts of the public IKS release. However Samsung's temporary code is still used as the live driver.
WFI residency down to 5 from 1000.
Wifi filters adjusted to only let through unicast.
Variety of hotfix patches from upstream updated to their final forms.
The tree is stripped of any other variants and only supports the i9500 for the time being. This is done to facilitate the cleaning. I might add the other variants back in the future.
Future: Given the current public upbringing of the 5420 on a 3.8 kernel, we might be able to fetch a lot of things and maybe even rebase on that once it is done. In terms of big.LITTLE, as long as the CCI is dead, there is not further point to update or use MCPM as it bring no new benefits.
For actual "hacky" features, things will be released on the Perseus kernel and branch in the coming weeks.
This thread is meant only as a notice and resource for developers. Discussion should be on the corresponding topic, any other shenanigans don't belong here.

Me and @bala_gamer were watching your this git past week
And what i observed is that you bought everything back to normal
From power management to OC
Now kernel developers can develop with ease
I took this pic just to show @bala_gamer
What awesome thing you brought tous
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyways i stopped deving for I9500
CANT REALLY keep up with my studies
Bye awesome dev
This will be my Last post in S4 Forums
Follow Me on Twiiter @razer1224

Hi,
I noticed I can't PM you, but I assume that is because you get well hassled being a dev here on XDA. Anyway that is why I am posting here, I was curious to know how difficult it would be for me to set up your kernel build for I9305 (Galaxy S3 4G-LTE)?
Basically I am working on a port of the 4.4.2 firmware to my device. As you are probably aware there is not Samsung 4.4.2 release for I9305, so I have narrowed my searches down to a few things 1) Needs to be Exynos sources (only it will be for 4412 - ARM Cortex A9) and that means exclusion of Big.Little functionality as far as I am aware..? 2) It needed to support LTE....now from what I hear the I9500 was initially believed to be a non-LTE device, but Samsung have responded that that is incorrect and that the Exynos release does support all 20 bands of LTE. That has pretty much narrowed it down completely to this device and this device ONLY, the Galaxy Note 2 N7105 as far as I am aware doesn't support LTE? I could be wrong though. (I am going to attempt to try some custom note sorftware in just a moment, although I can be certain it will fail miserably considering I have a major lack kernel support - AOSP kernel sources don't support Samsung RILD so are unable to notify the device when to stop the boot animation sequence....hence those that have tried will soon have eternal boot loop woes.
Anyway, I am fairly well prepared, I also have a spare dedicated test device and most of the right development tools.
If you are available to discuss or share any information with me please feel free to send me a PM or even reply to this post.
Thanks and I look forward to hearing from you
J

Jarmezrocks said:
Hi,
I noticed I can't PM you, but I assume that is because you get well hassled being a dev here on XDA. Anyway that is why I am posting here, I was curious to know how difficult it would be for me to set up your kernel build for I9305 (Galaxy S3 4G-LTE)?
Basically I am working on a port of the 4.4.2 firmware to my device. As you are probably aware there is not Samsung 4.4.2 release for I9305, so I have narrowed my searches down to a few things 1) Needs to be Exynos sources (only it will be for 4412 - ARM Cortex A9) and that means exclusion of Big.Little functionality as far as I am aware..? 2) It needed to support LTE....now from what I hear the I9500 was initially believed to be a non-LTE device, but Samsung have responded that that is incorrect and that the Exynos release does support all 20 bands of LTE. That has pretty much narrowed it down completely to this device and this device ONLY, the Galaxy Note 2 N7105 as far as I am aware doesn't support LTE? I could be wrong though. (I am going to attempt to try some custom note sorftware in just a moment, although I can be certain it will fail miserably considering I have a major lack kernel support - AOSP kernel sources don't support Samsung RILD so are unable to notify the device when to stop the boot animation sequence....hence those that have tried will soon have eternal boot loop woes.
Anyway, I am fairly well prepared, I also have a spare dedicated test device and most of the right development tools.
If you are available to discuss or share any information with me please feel free to send me a PM or even reply to this post.
Thanks and I look forward to hearing from you
J
Click to expand...
Click to collapse
Forget this.
You're better off from the the N7105 sources, it's basically the same hardware as the I9305 minus different screen and wacom digitizer. I build the S3 kernel from same base sources for all those devices.

AndreiLux said:
Forget this.
You're better off from the the N7105 sources, it's basically the same hardware as the I9305 minus different screen and wacom digitizer. I build the S3 kernel from same base sources for all those devices.
Click to expand...
Click to collapse
Yup I know that..and if they release a firmware update for 4.4.x then I will most certainly be using it, as for now they aren't even expected to release 4.3 for our device (official) till end of May....like WTF? I should have never bought an S3 LTE. I chose it because specifically I expected it to have more chances of being updated cause of the potential S4 and S5 devices believed to be all sporting LTE standard....so figured sources would be passed down the line. Far from the truth though...we are probably the worst supported recent Samsung device on the market.
So far there is only a N7100 4.4 release and I seriously don't want to go through the hassle "double" porting because it leaves so much room for error and ultimately failure it was hard enough porting from I9300 to I9305

Sir @AndreiLux I m unable to get phone radio or phone signal with this on pacman and official PA roms. I would appreciate if u may spare some time to fix the issue. It's working well with CM and Aokp based roms. Thx
Sent from my GT-I9500 using Tapatalk

Related

Do you want to help out developers? Got a broken device?

We now have the ability to make all devices with Hummingbird processors into "Super-Dev Phones". I just need a single dead board from each model to locate the proper modification. It can be water-damaged, broken, busted, cracked, smacked, set on fire, chewed on by your dog, dropped, thrown against a wall, or otherwise inoperable. I need a mainboard from each device to make this work.
If you wish to donate a dead device, post here, send a PM, or email me at my username @gmail.com
We can bring this modification to every device with the same processor, we just need to perform analysis before you can set up your device for bootloader development, or resurrect them from a hard-bricked state with nothing but software after a slight hardware mod.
We need to locate the xOM5 pin on following devices before they can be modified into UnBrickable Super-Development devices:
SGH-i896 Samsung Captivate UnBrickable thanks: bulletproof
SGH-i897 Samsung Captivate UnBrickable thanks: bulletproof
GT-i9000 Samsung SGS UnBrickable thanks: Zak Stinson
S8500 Samsung Wave Plans Available thanks: Rebellos
S8530 Samsung Wave II Plans Available thanks: Rebellos
SPH-D700 Samsung Epic 4G Plans Available thanks: James I-----
SGH-i997 Samsung Infuse 4G UnBrickable thanks pdx 528e
SGH-T959 Samsung Vibrant UnBrickable thanks: ChauncyG
SGH-T959V Samsung GalaxyS 4G UnBrickable thanks: bhundven
SGH-T849 Samsung Galaxy Tab 7.0 inch
GT-P1000 Samsung Galaxy Tab UnBrickable Thanks F50+
GT-P100 Samsung Sprint Galaxy Tab UnBrickable
SCH-i800 Samsung Verison/US Cellular Galaxy Tab 7.0 UnBrickable
SHW-M180 Samsung Galaxy Tab
GT-i9010 Samsung Giorgio Armani Galaxy
T839 Samsung Sidekick 4g UnBrickable
SCH-i500 Samsung Fascinate UnBrickable thanks: RootzWiki
SCH-i520 Samsung Droid Charge USB OTG port issue thanks: Clarkkent434
7e ViewSonic ViewPad
R90L200 Pandigital 9" tablet
SGH-i987 Samsung Galaxy Tab 7.0
SGH-T849 T-Mobile Samsung Galaxy Tab 7.0
GT-P1000N Samsung Galaxy Tab 7.0
SGH-i877 Samsung Inspiration
GT-I9020 Google Nexus S GSM - Failed -
GT-I9023 Google Nexus S CDMA - USB OTG port issue - Modification located, but CDMA gets in the way of USB OTG
GT-P1010 Samsung Galaxy Tab 7.0 Wi-Fi 16GB
M9 Meizu
SC-01C NTT DoCoMo Galaxy Tab 7.0
X10 Viliv HSPA 32GB
X7 Viliv HSPA 32GB
SCH-i400 Samsung Continuum
M9300 Kyocera Echo
YP-G1CW Samsung Galaxy S WiFi 4.0 8GB
SGH-T759 Samsung Exhibit 4G
yp-g70 Samsung galaxy s wifi 50 2
YP-G70EW Samsung Galaxy S WiFi 5.0 16GB
YP-GB70NW Samsung Galaxy Player 70 32GB
SCH-I500 Samsung Galaxy S Mesmerize
YP-MB2 Samsung Yepp / Galaxy Touch 32GB
GT-I9088 Samsung Galaxy S
YP-GB1EW Samsung Galaxy Player
16GBH-I909 Samsung Galaxy S Pro Galaxy S
SCH-W899 Samsung phone
SCH-R910 Samsung Galaxy Indulge / Forte\
MID8024-4G Coby Kyros 8"
MID7022-4G Coby Kyros 7"
MID1024-4G Coby Kyros 10.1
Just about anything with a Samsung processor in it.. There's so many
devices. These are the most common ones we are targeting.
Once I have received any of the above boards, I will attempt one of the following tricks to find out where the xOM5 resistor lies. Please understand that there is ALWAYS risk while working on electronics. I have done several of these sucessfully.
Methods for locating modificaton
1. Monitor memory locations in real-time while using the viewmem tool for changes to the OM registers. This only works on a rooted and working device. I can short high from behind a 10kohm pull-up resistor to a low value which is pulled down from a 100kOhm pull-down reistor. This will allow the high to counteract the low and a memory location can be monitored while performing this operation. This leaves the device totally operational and is the best way to perform this type of analysis, but is only accessible on some devices
2. Using overlays and processor pinouts, I can trace out likely locations of the xOM5 resistor, make a modification, and watch the results from the SBL over UART. This leaves the device totally operational.
3. Using relative positioning, I can pick a resistor, make a change and test for proper modifiction. This leaves the device totally operational.
4. Using a multimeter, I can remove the processor from a device and trace out the pins manually. This method is only appropriate for a broken device.
As an additional benefeit, we may be able to port the Nexus S bootloaders to the device, allowing for the latest version of Android to be ported easily to the device... After that, Ubuntu, Apple iOS, WP7, you name it...
Let me get into some of the technical details here... If you're not technical, jump to the end.
----
Pure and simple, this is a hardware exploit which allows direct upload of code to run on the S5PC110/Hummingbird/Cortex A8 platform. Samsung's chain of trust(CoT) model uses hardware to authenticate the Integrated Read-Only Memory (IROM), which authenticates the initial bootloader (IBL), which authenticates the Primitive Bootloader(PBL)... The IROM,IBL, and PBL are all loaded in IRAM, the PBL's job is to initialize Dynamic RAM(DRAM) and authenticate/load the Secondary bootloader(SBL AKA BL3), which loads a kernel, which loads the operating system you see on-screen.
This is a two part hack. We've developed a hardware modification which allows USB download of code. We've also developed the Hummingbird Interceptor bootloader(HIBL) which intercepts the CoT and allows a second, unsigned download. The HIBL uses official code to handle authentication, which jumps to another memory location. It's this memory location where we place our exploit. Our exploit reuses the same code that downloads the HIBL to IRAM, but it initializes DRAM which means you can directly upload a SBL(the final bootloader) to DRAM.
So once again.. really quick... We use a hardware mod to download Rebellos' HIBL, which violates the Chain of Trust, exploits a memory jump and allows unsigned code to run on the processor. All this means you can revive a dead phone easily or try out other operating systems and debug easily, regardless of signature checking on the device.
---------
The first part is the hardware modification so things can be tested without risk. Please help out if you have a dead device. I can make constructive use of it, or you can PM me for instructions. Either way, that old junked device you have can help out millions of people.
Made sticky for the time being
@all
If you don´t have any of the requested stuff please stay away from cluttering the thread, all non related posts such as "great idea!" and so will be deleted and re-incidence could lead to a ban
AdamOutler said:
As an additional benefeit, we may be able to port the Nexus S bootloaders to the device, allowing for the latest version of Android to be ported easily to the device. Apple iOS, WP7, Ubuntu, you name it...
Click to expand...
Click to collapse
So maybe u can run iOS on samsung, or WP7 on iPhone?
Or i misunderstand?
Is my HTC Desire a Cortex-A8 phone or is it not? I didn't know and just NOW found out (after some googleing): "Nope... Some kind of snapdragon cpu".
But I guess not everyone takes the time to look up the cpu of their phone like I did.
I believe if you explicitely list all C-A8 devices (although it seems like a lot of work to do so) you'll receive more bricked phone donations as when you only list the most common ones, because most guys will probably read this post, say "mhh, no my phones not listed here", close their browser tab and forget about that thread, even though they might have a C-A8 phone.
If you want to maximize the donations of bricked phones, list them explicitely in a "searchable" (=search engine friendly) manner.
Just a recommendation, though
akurei said:
Is my HTC Desire a Cortex-A8 phone or is it not? I didn't know and just NOW found out (after some googleing): "Nope... Some kind of snapdragon cpu".
But I guess not everyone takes the time to look up the cpu of their phone like I did.
I believe if you explicitely list all C-A8 devices (although it seems like a lot of work to do so) you'll receive more bricked phone donations as when you only list the most common ones, because most guys will probably read this post, say "mhh, no my phones not listed here", close their browser tab and forget about that thread, even though they might have a C-A8 phone.
If you want to maximize the donations of bricked phones, list them explicitely in a "searchable" (=search engine friendly) manner.
Just a recommendation, though
Click to expand...
Click to collapse
No it's not
Apple A4
Samsung Hummingbird
TI OMAP3
Only phones with the above are from Ol-Sammy, Big Apple, and Google's MOTO . HTC gets their cpu's from Qualcomm which has their own special architecture that's a hybird of Arm v7/v8. But it's closer to v7 so your device can't help them.
Oy, you now have me torn. I picked up a physically broken iphone 4 last weekend and am planning to repair and sell it, but I would love to see this go off the ground.... Decisions, decisions......
AdamiX said:
So maybe u can run iOS on samsung, or WP7 on iPhone?
Or i misunderstand?
Click to expand...
Click to collapse
Let me break this down... This modification means you can NEVER brick your phone. You have to physically destroy it. There's no firmware which can ruin the phone. You simply plug it in and run this tool..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This tool is still a work in progress. It requires a Linux machine (or linux Virtual machine) in order to run. However, it works, and it works well. This tool will work for:
SGH-i897
SGH-i896
SGH-i9000
SGH-i9010
SGH-i997
GT-P1000
T959... We will need to write another tool for other devices.
What this allows is for debugging of entire operating systems without any risk. For example, I installed BADA Bootloaders to my device last night with one of the guys from the BadaDroid project (they're working on porting Android to Bada). My device totally crapped when it saw that firmware, but it gave detailed logging messages about GPIOs. It would be possible to take that firmware and rewrite it to work with our devices, and it basically eliminates that "what if I screw something up" $600 barrier that prevents porting of other operating systems to our devices.
After I flashed Bada bootloaders with the tool above, I simply pulled the battery out, put it back in, connected to USB, used the tool above and it put my phone back into Odin download mode, at which point I reflashed the device.
We need to spread this mod to all the devices. Currently we have SGH-i897 mod done.
Ace42 said:
No it's not
Apple A4
Samsung Hummingbird
TI OMAP3
Only phones with the above are from Ol-Sammy, Big Apple, and Google's MOTO . HTC gets their cpu's from Qualcomm which has their own special architecture that's a hybird of Arm v7/v8. But it's closer to v7 so your device can't help them.
Click to expand...
Click to collapse
That would mean the Samsung GT-I917 (Focus) wouldn't work because it uses a Qualcomm CPU. So why was it included in the list?
StarbuxMcCloud said:
That would mean the Samsung GT-I917 (Focus) wouldn't work because it uses a Qualcomm CPU. So why was it included in the list?
Click to expand...
Click to collapse
I would ask the OP, could be a mistake, unless it still has a xOM5 pin on board. Which could be possible since it's still a Sammy after all. And Sammy makes parts for Apple too. He didn't put any htc phones in the OP, so only Sammy built phones contain the pin he wants.
StarbuxMcCloud said:
That would mean the Samsung GT-I917 (Focus) wouldn't work because it uses a Qualcomm CPU. So why was it included in the list?
Click to expand...
Click to collapse
You're right, removed from the list. I must have received some misinformation somewhere.
Great job! THIS is xda is all about. Hacking the devices until you cant hack them anymore
but no Samsung Epic 4g love?... Its sprints version of the Galaxy S
ugothakd said:
Great job! THIS is what xda is all about. Hacking the devices until you cant hack them anymore
but no Samsung Epic 4g love?... Its sprints version of the Galaxy S
Click to expand...
Click to collapse
That one should work too, it has the Cortex in it, guess he has to add that one next. Unless CDMA causes issues with his tools..
I have a I9020T Nexus S that a shotty kernel made me loose my baseband and pretty much all phone info including IMEI.
It's pretty much a tiny wifi tablet at this point. That being said I'm not sure I want to part ways with it, but I really don't want to send it off to Samsung.
If you guys have and Ideas on how to fix it, I don't mind using it for testing.
Also may be interested in a PM with instructions on what is needed to get the information you'll need to help develop your work.
Either way, thank you all for the hard work, I think this is an awesome development for our community.
AdamOutler said:
We need to locate the xOM5 pin on following devices before they can be modified into Super-Development devices:
Samsung I9000 SGS
Samsung S8500 Wave
Samsung S8530 Wave II
Samsung SGH-i997 Infuse 4G
Samsung T959 Vibrant
Samsung SGH-T849 Galaxy Tab 7.0 inch
Samsung GT-P1000 Galaxy Tab
Samsung GT-i9010 Girogio Armani Galaxy
Samsung GT-i8350 Omnia 7
Google Nexus S
Apple iPhone4
Just about anything with a CORTEX-A8 processor in it.. There's so many devices. These are the most common.
Click to expand...
Click to collapse
I just want to help out your list by adding some more common phones that use the Cortex-A8 Processor:
Samsung i8910 Omnia HD
All First Gen. iPad types
Samsung T839 Sidekick 4g
Palm pre, Palm pre plus
Palm pixi, Palm pixi plus
iPhone 3GS
Samsung SCH-i520, Samsung Inspiration, Samsung Stealth V, Droid Charge
Most All motorola android phones running 1ghz processors
Nokia N900
Thankx Samsunguy, could you add in the model numbers as well?
For instance, Samsung SPH-D700 Epic 4G​ should be added to the list (and I'll be hunting down people with a "broken" Epic for the cause).
=]
nubecoder said:
Thankx Samsunguy, could you add in the model numbers as well?
For instance, Samsung SPH-D700 Epic 4G​ should be added to the list (and I'll be hunting down people with a "broken" Epic for the cause).
=]
Click to expand...
Click to collapse
I updated my list and added common names and model numbers for the devices that had them.
And no problem
Hey Adam,
I've got a motorola droid here (with a broken speaker/microphone cable, so sound etc doesn't work), which uses the OMAP3430 CPU, would you be interested in this?
Might be very handy for debugging the Milestone, which is pretty much the same, but GSM and with a locked down bootloader.
Cheers,
Hobo
s5pc110/s5pv210
Shouldn't the list include s5pc110/s5pv210 based devices only? Cortex A8 is a bit general.
Samsunguy said:
I just want to help out your list by adding some more common phones that use the Cortex-A8 Processor:
Samsung i8910 Omnia HD
All First Gen. iPad types
Samsung T839 Sidekick 4g
Palm pre, Palm pre plus
Palm pixi, Palm pixi plus
iPhone 3GS
Samsung SCH-i520, Samsung Inspiration, Samsung Stealth V, Droid Charge
Most All motorola android phones running 1ghz processors
Nokia N900
Click to expand...
Click to collapse
Thank you. I will review each one for compatibility. They must be based on Hummingbird archetecture... really quickly, I checked the wikipedia on the Droid Charge and it said S5PC110 so that's a go for sure!
Samsunguy said:
I updated my list and added common names and model numbers for the devices that had them.
And no problem
Click to expand...
Click to collapse
I appreciate that, it makes things alot easier
masmalo said:
The Samsung Galaxy Tab 7 Wifi Only GT-P1010 uses the Cortex A-8 too
Click to expand...
Click to collapse
I will add that one. Thanks.
mystichobo said:
Hey Adam,
I've got a motorola droid here (with a broken speaker/microphone cable, so sound etc doesn't work), which uses the OMAP3430 CPU, would you be interested in this?
Might be very handy for debugging the Milestone, which is pretty much the same, but GSM and with a locked down bootloader.
Cheers,
Hobo
Click to expand...
Click to collapse
I'm not sure about Motorola products.. I think they mostly use the Qualcom archetecture... I'll verify to make sure.
Volcacius said:
Shouldn't the list include s5pc110/s5pv210 based devices only? Cortex A8 is a bit general.
Click to expand...
Click to collapse
You may be right, but so far that's all we've found in common with the entire range of processors. don't forget the S5PC100, OMAP and A4.

GT-P6201 = GT-P6200? (Plus N vs. Plus)

Hi all
I have bought a GT-P6201 - a Samsung Galaxy Tab™ 7.0 Plus N (WiFi / 3G) 16GB and I have some questions:
1. Is this device the "same" (as far as I know only the speakers are different, but I´m not sure...) like the normal Samsung Galaxy Tab™ 7.0 Plus (WiFi / 3G), the GT-P6200?
2. If yes, can I use the custom ROM´s and ClockworkMod Recovery for the GT-P6200?
3. Are there any XDA users out there having the same device? So that we can share "our" experience, questions, problems and solutions?
Thanks.
Vario_User said:
Hi all
I have bought a GT-P6201 - a Samsung Galaxy Tab™ 7.0 Plus N (WiFi / 3G) 16GB and I have some questions:
1. Is this device the "same" (as far as I know only the speakers are different, but I´m not sure...) like the normal Samsung Galaxy Tab™ 7.0 Plus (WiFi / 3G), the GT-P6200?
2. If yes, can I use the custom ROM´s and ClockworkMod Recovery for the GT-P6200?
3. Are there any XDA users out there having the same device? So that we can share "our" experience, questions, problems and solutions?
Thanks.
Click to expand...
Click to collapse
1) Should be YES
2) There's not a REAL custom ROM for our P6200 I'm about to realize one as soon as I have enough free time. You should be able to flash CWM and Root your device without any issue
3) As I've seen 'till now you're the only one who own this version of Tab Plus, hope someone else can share your experiences
'Cuz of that, I'd like to ask you if you can share some photos of your device maybe in its differences (speakers)
Let us know
Sent from my Galaxy Note with DarkyROM 3.3
Yesterday i orderd the Galaxy Tab 7.0 Plus N (GT-P6211) German Version.
It should arrive on 04.04.2012. Is the P6211 the same as the P6210? The Hardware is the same.
When it arrive I'll try to root it and flash CWM. I tell you if it works.
Ace9876 said:
Yesterday i orderd the Galaxy Tab 7.0 Plus N (GT-P6211) German Version.
It should arrive on 04.04.2012. Is the P6211 the same as the P6210? The Hardware is the same.
When it arrive I'll try to root it and flash CWM. I tell you if it works.
Click to expand...
Click to collapse
it's the same of P6201 but without 3G right?
Sent from my Xoom on EOS ICS Everest
[David] said:
it's the same of P6201 but without 3G right?
Sent from my Xoom on EOS ICS Everest
Click to expand...
Click to collapse
Exactly. It's the WiFi only version.
Hi David,
thank you for your answer .
Good to know that there is an active dev around here spending his free time for the tab.
BTW: Here is a picture link from Amazon showing the GT-P6201
http://ecx.images-amazon.com/images/I/41PSOFWcHPL._SL500_AA300_.jpg
CU
Vario_User said:
Hi David,
thank you for your answer .
Good to know that there is an active dev around here spending his free time for the tab.
BTW: Here is a picture link from Amazon showing the GT-P6201
http://ecx.images-amazon.com/images/I/41PSOFWcHPL._SL500_AA300_.jpg
CU
Click to expand...
Click to collapse
LoL, I ment a pics of YOUR device maybe in details
For dev, I'm just testing and porting something (today I worked hard) but there's lots to do for libraries ...I'm just trying to optimize everything that can be optimized (not only ZipAlign or Deodex).
Sent from my Xoom on EOS ICS Everest
wifi only
The U.S. wifi only, 16gb, is the gt-p6210. see the samsung us site below. Samsung US site so this is the us version in the link. It is a/b/g/n wifi.
http://m.samsung.com/us/mobile/galaxy-tab/GT-P6210MAAXAR#specs
Afaik:
6200 = 6201
6210 = 6211
It looks different but the hardware should be the same.
BTW: I own a 6211 and am happy with it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[David] said:
...
LoL, I ment a pics of YOUR device maybe in details
...
Click to expand...
Click to collapse
sorry, for the delay - here are some pictures.
Ah, so its nice not to be the only one having a GT-P2601
I was just about to start a Thread with the same questions, good that i found this one
Hope there's gonna be some awesom roms soon for our devices.
GreeZ
Arobase40 said:
There should be a mistake somewhere between the question and the answer...
I don't have an indepth german language knowledge, but when I see UMTS I guess that means 3G and not Wifi only !!!
We can find even cheaper but just to have an idea about the product and the specification (in german that time, but google translate should help) :
http://www.amazon.de/Samsung-Touchs...DA6U/ref=sr_1_1?ie=UTF8&qid=1335349342&sr=8-1
I'm thinking about buying one but I have 2 questions :
1) Is it possible to place a phone call with this Samsung Honeycomb just as with P1000 ??? ^^
2) What custom ROM can we expect to replace this Honeycomb ???
I really love my P1000, but if can have the same formfactor much lighter in the pocket, with dual core and 1 GB RAM with the same quality as with P1000, why not...
Anyone can compare the functionalities between Samsung Gingerbread and Samsung Honeycomb, specially for multimedia and bluetooth support ?
I already saw some missed with galaxy Tab 8.9" and 10.1" as multimedia and bluetooth were not as good as with GT P1000...
Click to expand...
Click to collapse
You are right, i made a mistake.
P6200 = P6201 3G
P6210 = P6211 WiFi
The P6201/P6211 is the German version. Samsung had to change the appearance because Apple complained that it look like the iPad.
To your questions:
1) Yes you can make phone calls on the P6200 3G version!
2) There is only CM9 as custom ROM, but it is in Development, because it has many bugs.
For me Honycomb is very smooth and stable and Samsung has confirmed that ICS will come to our Device soon. About bluetooth I can not say much because I haven't used it yet.
Stock videoplayer on the 6200 has pretty limited codec support - but with mx videoplayer or moboplayer, I haven't found anything it can't play - most using hardware acceleration aswell. I have the hdmi dock and output to a 50" hdtv and it's every bit as good as my archos - and that's saying something as archos are unbeatable for multimedia support.
As far as I can see, there are few differences to justify the massive price difference between the 7.0 and the 7.7 - slighty more powerful cpu and a little more screen real eastate but no IR blaster. I thought long and hard about which one, I reckon for the money the 7.0 plus 3G is the one to get, it's even really good as a phone, I thought I might make the odd call on it but have ended up using it more than my arc s
i`ve searching around but still don`t find where the custom rom link is...can anyone paste me some link of it..
my device is P6200DXKK5 for baseband version
and 2.6.36-P6200DXKL3-CL608366 [email protected] #3 for kernel version
thanks for helping..

Official Lollipop on Galaxy Tab Pro 12.2???

Have you any news about the upgrade?
do we will can see Android 5.0 ?
Still anyone's guess at this point. The Galaxy Tab S line only recently got their updates (and they are still rolling out on the numerous variants of those products) so it may be a while. Personally I'm still trying to be optimistic about it, but I'm not expecting any earth shattering improvements.
It'll take a while. Most of the larger-market Note 3's don't have 5.0, and they have identical hardware. Seems 5.0 has been put on hold for anything without a 6 in the device name, to prevent them impacting the S6 sales.
Even slight differences in hardware require testing though. Larger screen resolution and different cameras in the Note 3 and Note 12.2 are enough to cause 2 testing paths. Note 3 sales were presumably way higher than the 12.2 so that must take priority. My experience with Samsung is to wait a good long while before taking a firmware upgrade from them anyway.
Note 3&4 have it from Verizon of all people and they are some of the slowest to release updates. If they are going to release it it cant be far off
ShadowLea said:
It'll take a while. Most of the larger-market Note 3's don't have 5.0, and they have identical hardware. Seems 5.0 has been put on hold for anything without a 6 in the device name, to prevent them impacting the S6 sales.
Click to expand...
Click to collapse
It's not that...there are problems ( I guess from google or qualqomm) with lollipop. I own also note edge 915FY and despite the fact that has the same hardware as 915F it has not been updated to 5.Even the S6 with 5.0.2.has an update before lounching....
The S5 has 2 or 3 updates after initial release of lolipop...
I just hope that note pro will get anytime an update to lolipop
calinormy said:
It's not that...there are problems ( I guess from google or qualqomm) with lollipop. I own also note edge 915FY and despite the fact that has the same hardware as 915F it has not been updated to 5.Even the S6 with 5.0.2.has an update before lounching....
The S5 has 2 or 3 updates after initial release of lolipop...
I just hope that note pro will get anytime an update to lolipop
Click to expand...
Click to collapse
It has that as well, yes. From Google. Bluetooth connectivity, crashing Contacts, WiFi issues, general instability and memory leaks. But holding off an update to stimulate sales for the new product is a tried and true business method that they've been using since the S2.
The second S5 Lollipop update was required because most users couldn't use their device properly after the first update, which was put on hold after the first week.
at this point I'd appreciate a decent non official Lollipop build...
senectus said:
at this point I'd appreciate a decent non official Lollipop build...
Click to expand...
Click to collapse
First official lollipop firmware is here http://forum.youmobile.org/downloads/?sa=view&down=5357
senectus said:
at this point I'd appreciate a decent non official Lollipop build...
Click to expand...
Click to collapse
I already updated 2 Tab Pros to Lollipop UK version., OH4 I flashed over the Kitkat NK1, all apps and settings still retain.
UK version for Europe, there're more languages than US version.
OH4 = Version 4 Released on August (H) 2015 (O).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Marshmallow update...Xiaomi is playing with us!

I bought a Mi4c a few months ago convinced it was a great phone that could replace my Nexus 5 and yes it is a good phone with good specs but I bought it also when Xiaomi announced it would update to Marshmallow. My Nexus 5 was already running under MM so, I thought it would be a matter of a couple of weeks (Xiaomi announced update in Decembre) Today months have passed, many manufacturers like Motorola, Sony and even Samsung have updated some of their models even Moto E...but still nothing for Mi4c. Xiaomi makes good phones and I thought it was better than others cheap Chineses makers. It wants to be compared to Apple but it lacks support and compromise to existing customers. I probably had placed my expectations too high. Am I the only one? Next time I will buy a Nexus again.
Xiaomi uses Miui rom. There is no mutch different between MM based miui and Lollipop based miui.
Miui have most features of MM has already.
Ümit said:
Xiaomi uses Miui rom. There is no mutch different between MM based miui and Lollipop based miui.
Miui have most features of MM has already.
Click to expand...
Click to collapse
thats right! because of that i have no stress to get MM.
sMIUI runs great for me and have many many features!
IMO, they have too many devices to support. Just look at this table:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Many vendors only support their devices for 1 year, some 2, but here you can see Mi2S which is almost 3 years old and is still a supported device. I don't think Xiaomi has big enough development team to maintain all of those devices to match current base Android version. Moreover, they're advertising MIUI, which should have the similar experience between supported devices regardless the base Android version. 3 devices are already out with MM (still beta?), just wait for Mi4c turn. What features do you need from MM anyway?
"What features do you need from MM anyway?" My thoughts exactly.
Looking at the new features of MM, the ones that are interesting are the memory manager, per-app permissions and battery management. These are all things MIUI has built in already. Which probably also makes it that much harder to integrate into a new MIUI version.
Most of the other changes are cosmetic and most likely would not be reflected in MIUI anyway, when the MM update does come out.
or you can install TS CM13 - built by TS team or TS broken OS. They are 6.0 MM and pretty stable now. Great team with great supports and speed.
Sent from my Mi-4c using Tapatalk
The only real feature M offers over L is SD card as internal storage. Since Mi4c has no external storage you aren't missing anything. MIUI already does a Doze feature killing everything in the background.
Doze, per app permission and memory management are thé most wanted feature un MM.
MIUI is good and I don't criticize his developping team very active. I am only mad at Xiaomi marketing team making announcements and not complying.
jipi said:
Doze, per app permission and memory management are thé most wanted feature un MM.
MIUI is good and I don't criticize his developping team very active. I am only mad at Xiaomi marketing team making announcements and not complying.
Click to expand...
Click to collapse
Like a few of us mentioned so far, those features have been built into MIUI for a long time already. So rejoice, you have your most wanted features
On a serious note, it's probably reasonable to assume the MM rollout will follow the release of the new flagship, the Mi 5. Which I think is like a day or two away. You can bet that'll be released with the latest MIUI iteration of android.
jipi said:
Doze, per app permission and memory management are thé most wanted feature un MM.
MIUI is good and I don't criticize his developping team very active. I am only mad at Xiaomi marketing team making announcements and not complying.
Click to expand...
Click to collapse
Please provide at least 1 quote from Xiaomi officials that said Mi4c will get MM soon.
And no.. gizchina "xiaomi mm devices updates schedule" is not official.
i use Broken that is 6.0 and it works perfectly...
if u want 6.0 that bad get it...
Smartlock is there but it is not working at all... That would be nice to have it, dont know if under Android 6 or 7, or actual 5.1...
Enviado desde mi iPad utilizando Tapatalk
i believe it's a matter of time before the mi4c reveives marshmallow... but judging from xiaomi history mm won't come anytime soon... i'd estimate (personally) early autumn the soonest......
Am I the only one that think Xiaomi won't update Mi4c to MM?
Fsu0413 said:
Am I the only one that think Xiaomi won't update Mi4c to MM?
Click to expand...
Click to collapse
I guess so. Since Mi 3/4/5/Note get it, there's no reason to skip Mi 4C/4S/Note Pro/any other still supported devices. However, they seem to be in a discussion now, for supporting newer Android base with locked bootloader or stay with older one with unlocked bootloader.
Why shouldn't it get MM? The Mi4S just got released and should therefore get it, which is very similar to the Mi4C.
Maybe they will update Mi4c straight forward to "N" just like Mi4 which jumped lollipop to MM.
luis83rs said:
Smartlock is there but it is not working at all... That would be nice to have it, dont know if under Android 6 or 7, or actual 5.1...
Enviado desde mi iPad utilizando Tapatalk
Click to expand...
Click to collapse
you can use smartlock after install xposed framework and xMIUI xposed module. You have to be rooted though...

Ulefone Armour X8

I'm looking for information about this phone, as I'm considering buying one to replace an ageing Sony Xperia Z5 Compact.
Specifically I'm trying to find out if this phone will receive the upgrade to Android 11, when it comes out (I can purchase it with Android 10 installed).
I'd also like to know if it will actually receive OS updates at all, eg security updates.
I've tried emailing the company directly several times but either receive no reply at all, a canned response that doesn't answer my questions, or mixed-up answers that don't seem to be related to my questions at all.
I've also noted that the X8 doesn't seem to be on Google's list of Certified devices (https://storage.googleapis.com/play_public/supported_devices.html), and again, a question to Ulefone about this is ignored.
Hopefully someone here knows some information about this phone and company?
Or has anyone got any experience with the Armor X8?
As an alternative - if anyone can recommend an IP68 phone (preferably a rugged phone) that has a smaller than 6" screen (preferably smaller than 5.5"), which is Android 10/11 compatible (ie will receive upgrades), has an SD card slot, and has chip/memory specs significantly better than the Xperia Z5 Compact, I'd appreciate it.
Riceburner said:
I'm looking for information about this phone, as I'm considering buying one to replace an ageing Sony Xperia Z5 Compact.
Specifically I'm trying to find out if this phone will receive the upgrade to Android 11, when it comes out (I can purchase it with Android 10 installed).
I'd also like to know if it will actually receive OS updates at all, eg security updates.
I've tried emailing the company directly several times but either receive no reply at all, a canned response that doesn't answer my questions, or mixed-up answers that don't seem to be related to my questions at all.
I've also noted that the X8 doesn't seem to be on Google's list of Certified devices (https://storage.googleapis.com/play_public/supported_devices.html), and again, a question to Ulefone about this is ignored.
Hopefully someone here knows some information about this phone and company?
Or has anyone got any experience with the Armor X8?
As an alternative - if anyone can recommend an IP68 phone (preferably a rugged phone) that has a smaller than 6" screen (preferably smaller than 5.5"), which is Android 10/11 compatible (ie will receive upgrades), has an SD card slot, and has chip/memory specs significantly better than the Xperia Z5 Compact, I'd appreciate it.
Click to expand...
Click to collapse
I got it for my wife a few days ago.
It is a certified device.
Whether it will support official updates or not, since it comes with Android 10 and having a Mediatek chipset, it shouldn't be too hard to port newer releases to it. There's some thread here about that for the Armor 6 IIRC.
Overall I'd say it's one of the best phones you can get for its price.
ssorgatem said:
I got it for my wife a few days ago.
It is a certified device.
Whether it will support official updates or not, since it comes with Android 10 and having a Mediatek chipset, it shouldn't be too hard to port newer releases to it. There's some thread here about that for the Armor 6 IIRC.
Overall I'd say it's one of the best phones you can get for its price.
Click to expand...
Click to collapse
The Armor 8 is on Google's list - but not the X8. Do we think for certain that they're the same under the skin?
I'm not much of a modder/rooter, generally quite happy with the stock OS, but I do like to receive the security updates, and OS upgrades when they're available. Maybe having a Sony has spoilt me?
They are most definitely not the same under the skin (the X8 is newer and slightly less powerful), but I have had it in my hands and it is certified.
ssorgatem said:
They are most definitely not the same under the skin (the X8 is newer and slightly less powerful), but I have had it in my hands and it is certified.
Click to expand...
Click to collapse
Without wishing to be argumentative ( ) - what's telling you it's certified?
Google Play says it's certified (bottom row, "dispositiu certificat" = "certified device")
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ssorgatem said:
Google Play says it's certified (bottom row, "dispositiu certificat" = "certified device")
View attachment 5221637
Click to expand...
Click to collapse
Good stuff!
Have you received any security updates or OS upgrades?
Considering she's had it for 10 days...
No, no system updates yet.
Just for reference: I received this, rather abrupt email from Ulefone today:
Hello,
Armor X8 will receive the security updates for Android 10, but cannot upgrade to Android 11.
Best regards
Ulefone
website: [www.ulefone.com]www.ulefone.com
email: [email protected]
location: Shenzhen, China
From: Riceburner
Date: 2021-02-04 18:41
To: [email protected]
Subject: Re: Fw: Android updates and upgrades
Hi,
Can you confirm if the Armor X8 will receive security updates for Android 10?
Will other phones from Ulefone receive an upgrade from Android 10 to Android 11?
Is it just the Armor X8 that will not receive any upgrades?
Many thanks
Click to expand...
Click to collapse
I think I'll be looking elsewhere for my next phone.
I know this is an older thread...
but here are the official Android 11 files for the Armor x8, also linked from their support site:
https://drive.google.com/drive/folders/1wh8BOdNX0aMUDdOt66FyiktFyq5BIZ7t
They state you will brick it...I just did mine 10 minutes ago, works like a charm! and no more ADUPS !!
treb42 said:
I know this is an older thread...
but here are the official Android 11 files for the Armor x8, also linked from their support site:
https://drive.google.com/drive/folders/1wh8BOdNX0aMUDdOt66FyiktFyq5BIZ7t
They state you will brick it...I just did mine 10 minutes ago, works like a charm! and no more ADUPS !!
Click to expand...
Click to collapse
ditto .... this being an older thread
treb42 do you know if your updatable phone was a SH1 or SH2 model as disclosed at the bottom of settings/about phone?
Has anyone else tried to update this for SH1 or SH2 models (or is this irrelevant and I am barking up the wrong tree)
Looking at the warning on the upload page my "guess" is its associated with the SH1 (same column) and no such warning sits under SH2.
Great little tough-phone and I'm using adb to manage ADUPS but I'd prefer to banish it to the deepest depths of hell

Categories

Resources